3 months ago
This is the app:
You will see that I haven't deployed a new version in a while and everything looks okay.
But when you go to the URL you see:
===
Not Found
The train has not arrived at the station.
Please check your network settings to confirm that your domain has provisioned.
If you are a visitor, please let the owner know you're stuck at the station.
Request ID:
GuBRqZA_TjqjAf2y0-QtfA
===
Please help or let me know if I need to provide more information.
12 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
I restarted the container and it seemed to work temporarily but now it’s intermittent and mostly not working.
Mostly you get the error screen, or you get a half loaded page without styles or if you are lucky the real thing properly loads.
3 months ago
I have the same happen for one of my sites/services.
It is extremely simple - and have not deployed it for weeks.
kokholm
I have the same happen for one of my sites/services. It is extremely simple - and have not deployed it for weeks. <https://railway.com/project/5f4f2e4e-5c18-4737-8334-87a38e9cabc0/service/f463526e-0471-4c8f-a468-cacdda80777f?environmentId=3d9bdbf8-d17c-4348-993c-e3a21acd98be>
3 months ago
As you have a pro account you should be able to get official support - perhaps you can tell me what they say? Many thanks
adamsilver
As you have a pro account you should be able to get official support - perhaps you can tell me what they say? Many thanks
3 months ago
Yeah. I can make a ticket myself and hope that is bumped up
kokholm
Yeah. I can make a ticket myself and hope that is bumped up
3 months ago
Thank you appreciate it - perhaps you can point them to this thread too!
3 months ago
3 months ago
This was related to a known issue with our proxy during a period of elevated traffic. Your service and domain configurations were fine the whole time. A container restart can re-establish routing if you're still seeing the error. Let us know if it persists.
Status changed to Awaiting User Response Railway • 3 months ago
sam-a
This was related to a known issue with our proxy during a period of elevated traffic. Your service and domain configurations were fine the whole time. A container restart can re-establish routing if you're still seeing the error. Let us know if it persists.
3 months ago
Everything is still down today. any ideas?
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Awaiting User Response Railway • 3 months ago
brody
You need to enable private networking in your service settings.
3 months ago
I have done that and redeployed (just in case) and it seems to be working (thank you!) but are you able to explain to me why I needed to do that given I have never had to do that before?
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
A recent platform change now requires private networking to be enabled on all services. Older services that predated this weren't automatically migrated, which is why your domain stopped resolving.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved brody • 2 months ago

