Notes:

• Communication to Postgres is done exclusively over the private network and the database is not exposed externally in any way by default, if you want to enable access from outside of the private network you can go to the databases settings to enable TCP proxying and enter the internal port (5432) the TCP proxy can be again removed at any point to close off external access.

• MinIO is used in place of a 3rd party S3 storage provider, Using MinIO in this template allows you to upload media during the bot creation flow and have the bot send the uploaded media back to the users during a chat with the bot.

• The "MinIO Init - Delete Me" Is a service to create a public "typebot" bucket in the MinIO service, Typebot will use this bucket to upload media into, the bucket is set to public because your bot would need to be able to send the media to the users who are chatting with the bot. This Service only needs to run once, you may delete it after the logs of the service indicate that it was run successfully, if it failed you may need to redeploy it.

• Upon changing the Railway domain or adding your own custom domain to the service, you will need to redeploy both the "Viewer" and the "Builder" services, this is so that they are aware of the new domains in use.

• Using Gmail as an SMTP host is known to not work on Railway services, this is not limited to Typebot deployments.

• Updating Typebot is as easy as redeploying!

• If you deployed this template before January 25th 2024 and want to access the MinIO console you would need to deploy this template into your existing project.

what email provider are you using?

titan

have you configured the correct SMTP host and port on the builder service?

Yes !

are there any email related error logs in the builders deploy logs?

error: {

message: 'Email(s) could not be sent',

stack: 'Error: Email(s) could not be sent\n' +

' at Object.s as sendVerificationRequest\n' +

' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +

' at async Promise.all (index 0)\n' +

' at async email (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/core/lib/email/signin.js:31:3)\n' +

' at async Object.signin (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/core/routes/signin.js:115:24)\n' +

' at async AuthHandler (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/core/index.js:260:26)\n' +

' at async NextAuthApiHandler (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/next/index.js:22:19)\n' +

' at async y (/app/apps/builder/.next/server/chunks/162.js:1:7850)',

name: 'Error'

},

providerId: 'email',

message: 'Email(s) could not be sent'

}

it could be that you didn't configure smtp correctly or that titan is blocking the login attempts, I am unable to reproduce this with a zoho email

Hi friends, I have the same problem with the log, I can't log in and I'm also using Titan's SMTP. Any solution?

[next-auth][error][SIGNINEMAILERROR]

https://next-auth.js.org/errors#signinemailerror Email(s) could not be sent {

error: {

message: 'Email(s) could not be sent',

stack: 'Error: Email(s) could not be sent\n' +

' at Object.s as sendVerificationRequest\n' +

' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +

' at async Promise.all (index 0)\n' +

' at async email (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/core/lib/email/signin.js:31:3)\n' +

' at async Object.signin (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/core/routes/signin.js:115:24)\n' +

' at async AuthHandler (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/core/index.js:260:26)\n' +

' at async NextAuthApiHandler (/app/nodemodules/.pnpm/next-auth@4.22.1next@14.0.3nodemailer@6.9.3react-dom@18.2.0react@18.2.0/nodemodules/next-auth/next/index.js:22:19)\n' +

' at async y (/app/apps/builder/.next/server/chunks/162.js:1:7850)',

name: 'Error'

},

providerId: 'email',

message: 'Email(s) could not be sent'

}

Theres unfortunately not much I can do to help you if Titan is blocking your login attempts, assuming you have the SMTP host, port, username, and password all set correctly.

brody thanks, for now I'm using gmail. Thank you very much man.

Use a variable on root directory source, Hi, is possible use a variable to set the docker url to a source ?

"A magic link email was sent." but no request received in the SMTP server.

Edit: worked after changing NEXTPUBLICSMTP_FROM env var

/typebots/[typebotId]/file seems that id of bot is not giving when uploading a file. maybe a bug? upon uploading a file it gives back: ''Invalid message. Please, try again.''

hello Brody, I too had the 'message: 'Email(s) could not be sent' problem. Deleted the project and will try again later. Could you give me some tips/guide on how to set it up? A free SMTP provider would be great too as I have no clue how this works. I tried Zoho and it didn't work, will try a guide I found now.

Edit: problem solved, used google's SMTP following a tutorial in portuguese.

zoho's email service works great, I have never had issues using my custom domain email with them and typebot, you can find the smtp settings for zoho here https://www.zoho.com/mail/help/zoho-smtp.html

hello i'm brazilian and my english isn't so well.
The deploy was a sucess, but everytime i want to make a bot when i put the firsts boxes, appers a error "Error while updating typebot

Found newer version of the typebot in database", anyone can help me?

I will see if I can reproduce the error.

Hey yohannreimer, I was not able to reproduce this error, the template works fine. Perhaps you have misconfigured something, try redeploying the template?

hey, i redeployed but continuous the error, but i don't know what i can misconfigured, when i deploy i just modificate the smtp and is this. i'm trying i more time now.

Please make sure you are deploying the typebot template made my me (Brody)

Hey @brody how to unsubscribe of a thread to no be notify ?

That is a good question, and I'm sorry you've been bombarded with messages that no longer involve you, but at the moment there is unfortunately no way to unfollow a specific thread, you would only be able to opt out of all help station messages from within your account settings.

Brody, i just deploy again, and this time i deployed yours and work perfectly, tk

Glad to hear that

Error: Console service failed to deploy

MinIO has recently removed its public console image from Dockerhub, thus any Typebot template deployments would have its Console service fail to deploy, the fix is however very simple, within the settings panel for the Console service -

• Disconnect the source image.

• Remove its root directory.

• Update the start command to /bin/sh -c "exec console server --host 0.0.0.0 --port $PORT"

• Connect this repository https://github.com/railwayapp-templates/minio-console

Then deploy the changes by clicking the "Deploy" button.

These changes have already been made to the Typebot template so any deploys from here on out are not affected.

I am having trouble deploying your template. The error occurs when creating the variables, and this error message appears:

Oh No!

Looks like something went wrong and the train derailed.

The error occurs when the activity is at:

Creating Environment

About to create your very first environment!

That wouldn't be an issue with the template, it instead is an incredibly misleading error message that means you are on a limited trial and are not allowed to deploy anything but databases, typebot is more than just databases so you get that error.

You will need to upgrade to the Hobby plan in order to deploy typebot or anything other than just databases.

Thank you very much for the explanation. I will submit my plan!

Hello, I saw that the typebot version was updated on the official website.

Having more integrations.

I installed it last year and my version is old.

How do I update to the latest version?

Without losing my data and files?

What are the sources of your builder and viewer services?

https://railway.app/template/typebot

hi I try to deploy typebot template but always apeears this message: Looks like something went wrong and the train derailed

That means you are either on a limited trial or have reached your trial limits for projects / services, either way you will need to upgrade to Hobby.

When trying to deploy Typebot after having configured everything, as in Vercel, the deployment returns the following error in Railway;

(The most interesting thing is that Vercel is working perfectly, and before asking me to use a model, I can't because my typebot is modified for my project.)

No files changed in this command, skipping snapshotting.

Jul 15 01:01:13

COPY . /app/.

Jul 15 01:01:13

Taking snapshot of files...

Jul 15 01:01:14

RUN --mount=type=cache,id=-/root/npm,target=/root/.npm npm i

Jul 15 01:01:14

Cmd: /bin/bash

Jul 15 01:01:14

Args: [-ol pipefail -c npm i]

Jul 15 01:01:14

Running: [/bin/bash -ol pipefail -c npm i]

Jul 15 01:01:14

npm WARN config production Use --omit=dev instead.

Jul 15 01:01:14

npm ERR! code EUNSUPPORTEDPROTOCOL

Jul 15 01:01:14

npm ERR! Unsupported URL Type "workspace:": workspace:*

Jul 15 01:01:14

Jul 15 01:01:14

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-07-15T04_01_14_264Z-debug-0.log

Jul 15 01:01:14

error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1

Jul 15 01:01:14

exit status 1

Jul 15 01:01:25

container event container died

Jul 15 01:01:28

Stopping Container

I hope it can help!

Hey, this isn't an issue with the template, let's stick to the help post you opened.

Hey Brody, A few days back I started getting weird error codes from the templates within Typebot. I cannot see the template example when trying to "start from template" however i can use the templates but when I do I see the same error message. I have redeployed a few times but it keeps coming up with same errors. See Attached. My free account on Typebot.io has no issues. The same thing happens when I try to create new bots...but not always....Any thoughts?

I'm really sorry but while I may be the creator of the template, I cannot provide support for the software.

I am only able to provide support for the Railway platform or product here.

No worries - I understand. I will assume it is a Typebot issue and not a Railway template issue and go from there. And thanks for uploading so many templates. It has really help me understand new AI software better. Please keep it up ;-). Thanks Brody!

Thank you for the kind words, and thank you for understanding!

I'm having trouble with Typebot on Railway.
I thought the installation would be faster, but it's been several hours already.

Is it normal for Typebot to take more than 8 hours to install on Railway in 2025?

I found some tutorial videos, but they are all from 2023 or 2024. So far, I haven't seen anyone explaining how to install it this year on YouTube.

Did I do something wrong, or is the installation process really this slow?

~ pr-br

Estou com dúvidas sobre o Typebot no Railway.
Pensei que a instalação seria mais rápida, mas já se passaram várias horas.

É normal levar mais de 8 horas para instalar o Typebot no Railway em 2025?

Encontrei alguns vídeos tutoriais, mas todos são de 2023 ou 2024. Até agora, não vi ninguém ensinando a instalar este ano no YouTube.

Será que fiz algo errado, ou o processo realmente demora tanto?