4 months ago
Hello, our production code started receiving 502 nginx bad gateway errors for no apparent reason when our router attempts to connect our web frontend to the associated Railway service; we looked into it, and the config for our production code now has RAILWAY_BETA_ENABLE_RUNTIME_V2 set, even though we did not set this on at all. We would like to turn this off because we think it is the cause of the outage. If anyone else has encountered this issue, please let us know; our prod service is down until this get resolved. Thanks
4 Replies
We have an internal private network called “production” which is stuck on initializing; this is causing all internal private network resolutions to fail. We would like to delete it, however we can’t find any way to delete it on the API, CLI, or Railway web UI
We only want the Railway default private network, as this is what works in our staging network and what has worked in prod for months