3 months ago
Hi everyone, I really need help.
My Railway payment was declined and my account got temporarily restricted.
After I fixed the payment, I had to redeploy all my services.
Since then, Typebot won’t let me log in anymore.
When I try to sign in with my email, it keeps loading forever and eventually shows an error telling me to check the logs.
The Railway logs show:
AccessDenied
no-token-requests
I even tried creating brand-new Typebots, but I still can’t log in — the same issue happens every time.
Before the payment issue, everything worked normally.
After the redeploy, nothing related to authentication works anymore.
Does anyone know what might be causing this or how I can fix it?
I can share screenshots of my environment variables, logs, or auth configuration if needed.
Thanks in advance!
4 Replies
3 months ago
Hello,
Outbound SMTP is only available on the Pro plan and above, while Free, Trial, and Hobby plans have SMTP disabled.
For sending emails from your application, please use a dedicated email service that provides HTTPS APIs. More information can be found in our documentation:
https://docs.railway.com/reference/outbound-networking
Best regards,
The Railway Team
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
brody
Hello,Outbound SMTP is only available on the Pro plan and above, while Free, Trial, and Hobby plans have SMTP disabled.For sending emails from your application, please use a dedicated email service that provides HTTPS APIs. More information can be found in our documentation:https://docs.railway.com/reference/outbound-networkingBest regards,The Railway Team
3 months ago
Hi, thanks for your reply.
I’ve just upgraded my subscription, but SMTP is still not working.
Even after upgrading, my application keeps trying to send the login email indefinitely and never completes the request.
Can you confirm whether the plan I upgraded to actually enables outbound SMTP?
Or is there an additional activation step needed before SMTP starts working?
Thanks!
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Please perform a re-deploy of your application after you upgrade to Pro for us to apply the new configuration and refer to Debugging SMTP issues for additional troubleshooting steps.
Thank you!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago