Issues with backend
matoxx01
HOBBYOP

a year ago

Before when I started my frontend I could not access my APIs because of an ‘Internal Server Error’ and I had to restart my backend to get it working again and everything was fine, but in another 4 hours it did not work, I tried to fix it with Cron, but it was still the same. Now it's something different, the Build is running fine, but I don't have a log in the Deploy, and when I go to the Railway URL I get ‘502 Bad Gateway’. So my question is, do I have to pay for it to work properly? If not, how can I fix this problem, I am attentive.

$10 Bounty

1 Replies

a year ago

502 bad gateway would mean your service or some other service that your service is connecting to isn't giving a response, what do you see in the service logs when this happens and what kind of code or template are you running on the service?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...