Internal server error when accessing Typebot

I noticed that since yesterday the new installations with the Typebot template present the error Internal server error when trying to access the url of the builder. Problem also reported by several users who used my referral link.

Using Detected Dockerfile

context: bf048ee8b6da4f93788806cc790756d5

ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

4d977139-3a8b-4a74-8dd8-44f9e989efbc
https://github.com/Aravindha1234u/typebot-railway/issues/2
@T3cH_W1z4rD

I will try to reproduce this issue but can you give me more insight what is the issue?
you are saying many user has issues using your referral link? did you try to replicate my template and that is causing issue? I didn't understand the actual problem

today this message is highlighted in the log

dockerfilePath is only compatible with the Dockerfile constructor
no that said people who used my Railway referral link reported the same problem to me, because I recently made the video showing how to install Typebot on Railway using the template

yes I just saw the video but you didn't the issue if that's not the case here? were you getting the same issue
if its something related to Docker daemon I guess it should platform issue @Angelo @Brody can you help here?

this is the log of my installation

previously it was ok, yesterday after they reported to me i created a new install and learned the error for me as well

the docker deamon error was an incident with railway, but that's since been resolved

I installed a new Typebot, following your message, but the problem remains when trying to access the builder url it shows Internal Server Error

yeah the internal server error has nothing to do with the docker error you received earlier and this would be an issue with the template
@T3cH_W1z4rD - you're up! 🙂

okay, I'll let tech wizard take it from here

There is no error in this log. is it running now properly ?

the problem remains >>> Internal Server Error


TypeError [ERR_INVALID_URL]: Invalid URL

at new NodeError (node:internal/errors:405:5)

at new URL (node:internal/url:611:13)

at parseUrl (/app/node_modules/.pnpm/next-auth@4.22.1_next@13.4.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/utils/parse-url.js:17:16)

at Object.<anonymous> (/app/node_modules/.pnpm/next-auth@4.22.1_next@13.4.3_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/react/index.js:72:34)

at Module._compile (node:internal/modules/cjs/loader:1256:14)

at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)

at Module.load (node:internal/modules/cjs/loader:1119:32)

at Module._load (node:internal/modules/cjs/loader:960:12)

at Module.require (node:internal/modules/cjs/loader:1143:19)

at require (node:internal/modules/cjs/helpers:110:18) {

input: 'https://';,

code: 'ERR_INVALID_URL'

}
@T3cH_W1z4rD I believe that if you install a new Typebot you will observe this problem
builder-production-ddf4.up.railway.app

please show us a screenshot of the service variables please

now the log is complete

'''ADMIN_EMAIL=claudioXXXXXX@XXXXXXXX.com
DATABASE_URL=${{Postgres.DATABASE_URL}}
ENCRYPTION_SECRET=9tdv-8z19o5n1e_1yox6@cmnaqhyj96n
NEXTAUTH_URL=https://${{RAILWAY_SERVICE_BUILDER_URL}}
NEXT_PUBLIC_SMTP_FROM=${{SMTP_USERNAME}}
NEXT_PUBLIC_VIEWER_URL=https://${{RAILWAY_SERVICE_VIEWER_URL}}
PGDATABASE=${{Postgres.PGDATABASE}}
PGHOST=${{Postgres.PGHOST}}
PGPASSWORD=${{Postgres.PGPASSWORD}}
PGPORT=${{Postgres.PGPORT}}
PGUSER=${{Postgres.PGUSER}}
PORT=8080
SMTP_AUTH_DISABLED=false
SMTP_HOST=smtp.sendgrid.net
SMTP_PASSWORD=SG.4dOZC3eaS6G7G40Rv54KEXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SMTP_PORT=587
SMTP_SECURE=false
SMTP_USERNAME=apikey'''

please enclose all code type text in triple backticks

sorry but i didn't understand

is the issuer in builder or viewer ?

builder

Project ID

422ffb9b-1326-4f64-a3f0-a9ae5b2cc79b

I am looking into this issue. give me few minutes

Great thank you

@Brody I have question
did service discovery environment variable stopped working ?

Builder and Viewers are service with domain linked but there variable aren't working

DATABASE_URL=${{Postgres.DATABASE_URL}}
ENCRYPTION_SECRET=${{builder.ENCRYPTION_SECRET}}
NEXTAUTH_URL=${{RAILWAY_SERVICE_BUILDER_URL}}
NEXT_PUBLIC_VIEWER_URL=${{RAILWAY_SERVICE_VIEWER_URL}}
PGDATABASE=${{Postgres.PGDATABASE}}
PGHOST=${{Postgres.PGHOST}}
PGPASSWORD=${{Postgres.PGPASSWORD}}
PGPORT=${{Postgres.PGPORT}}
PGUSER=${{Postgres.PGUSER}}
PORT=8081

Inside service I get

NEXT_PUBLIC_VIEWER_URL=
NEXT_PUBLIC_VIEWER_URL=
NEXT_PUBLIC_E2E_TEST=
NEXT_PUBLIC_VIEWER_URL=

go raw edit the viewers raw env, save it, and let it rebuild

Yes now variables has value. so need time to get domain assigned and populate the value ?

this is a known issue and will be tackled within the next few weeks
or so im told

@T3cH_W1z4rD @Brody my dear, I'm not a developer, so if you can explain to me what I should do to solve it here, I'll be grateful

I did find the root cause but didn't find the solution
7days before typebot has updated their docker image to pull environment variables from specific file and before this release it wasn't like this. so I am trying to fix it

correct @T3cH_W1z4rD ... yes before it was working perfectly

please chill with the pings #🛂｜readme #5
if you are going to ping prefix it with @silent like i did when i pinged tech wizard

@Claudio Balbino can you try to sync the repo to latest or delete the project and deploy it again

created a new Typebot... it worked perfectly 👏👏👏

that what's template fault it was with the code change that they released. I can we can close this thread as well.
@Brody
I taught @slient was some kind of feature of discord nevermind it didn't work as expected

it is, don't know what went wrong, no worries though
locking thread now!
thanks for getting this fixed 🙂