typebot internal server error
typebot is experiencing internal server error. What is the solution?
42 Replies
Could you please send your deploy logs?
@t3ch_w1z4rd I'm seeing this a lot, please get to the bottom of it, as this is for a bounty
@Brody I see @cadimbh has open a thread in templates channel and noreply and here now he didn't describe what is the issue.
run typebot yourself, play around with it and see if this error can be reproduced
we had issues with the typebot template when typebot updated the codebase to next version and I have fixed it . we already have a solution but I need to confirm whether its same issue or different issue. but no logs or no information is provided I can't help
@Brody you can check the date and time I just deployed my template it works flawlessly.
and the site works fine?
yes I have tested login and registration and well works as expected
@cadimbh if you still using old codebase please pull the latest and rebuild the service.
@Brody I guess this should the same issue which we had last week. I am not sure if I can push notification to users to update the image
I wish you could do that
when you are deploying your own template, what smtp server are you using?
I have tested with sendgrid, mailjet, mailgun and ethreal.mail(for testing and debugging)
we have seen zoho mail also working
gmail
test with gmail
google should also work til they configure it properly
will test it later today.
I've seen lots of issues with using gmail on railway, and it's one of the most likely smtp servers the users will use
Probably. but that shouldn't throw 500 error unless they have written code like that
why not? typebot tries to connect to the mail server, it can't, and ends up throwing a 500, seems perfectly plausible to me
no smtp comes into play in authentication like signup or signin.
it can connect to smtp server when server start but if it was handled properly with try catch then server should normally and authentication will fail by which we can confirm its smtp issue and not server issue
okay, please test when you have the time
Sure will keep you posted.
@cadimbh please let us know whether are you using latest code and its still failing
it would be helpful if you share the logs
can you show us any of the non sensitive environment variables?
project id 1cca5529-8cc9-4604-a97c-f2db41ad6792
It was working normally. Yesterday was not me. But several users are having the same problem.
^
mind just telling us what smtp server you are using?
what do you mean several users ?
is it possible to restart the service and get first instance when this error shows up ?
I installed a new Typebot and the problem was presented here... I changed the latest version to 2.16 in my repository and now it works, it seems that the problem is being generated in 2.17 that brings the integration with WhatsApp
Yes apparently it was in this new version.
Several users who are on version 2.17 are reporting the same problem. "Internal Server Error"
yes, as I published a video on YouTube showing how to install Typebot on Railway using template, some users reported the problem to me, so I installed a new Typebot in my account on that date and the problem was presented.
In version 2.17 the url of the viewer appears localhost, where it should show the url of the Railway, changing the version latest to 2.16 Typebot works
In version 2.17 the url of the viewer appears localhost, where it should show the url of the Railway, changing the version latest to 2.16 Typebot works
so is it missing variables that pertain to WhatsApp and is freaking out?
It's not because of variables. The Typebot template is on Railway. And both the Viewer and the builder have an error in the domain link.
WhatsApp variables are not added during installation, but apparently it seems that the new version broke something during installation with the template, because in 2.16 it is working.
WhatsApp variables are informed if you want to share the flow with WhatsApp
gotcha
pin the version to 2.16 and call it a day until the devs release a fix
@cadimbh change the latest version to 2.16 in your repository to be able to use it until the problem is solved
Yes, I'm going to upload it to test. Thank Claudio
I'm facing the same problem, how can I put in the previous version? @claudiobalbino
Hello friend, did you manage to set it to the previous version of typebot and did you succeed?
it has already been confirmed that 2.16 works