a month ago
After the automatic metal upgrade deployment, the service can’t connect to other services in the project. Redeploying temporarily fixes the issue, but after about 30 minutes the error occurs again. When I try to redeploy once more, the new deployment gets stuck at the container creation stage.
6 Replies
a month ago
Hmmm that is definitely not ideal. Could you send a link to the service having this issue? The one failing to connect and the service its failing to connect to?
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
could this be in connection to docker being broken? https://www.dockerstatus.com/
Status changed to Awaiting Railway Response Railway • about 2 months ago
a month ago
The connection is working now and the deployment is no longer stuck. Here is the link to the affected service:
https://railway.com/project/cd30ec90-f3c9-4a9b-837a-adf66d7599e7/service/42d8607f-5fa0-4e31-a888-f61d59f9644d?environmentId=5166440e-c6b2-4076-884a-0b42d265b870&id=ddc1e0d3-b79a-4ea6-9420-4520612aab50
This service is unable to connect to any internal services. External connectivity has not been tested.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
I’ll try, but for now everything is working, and I don’t really want to touch it. If it breaks again, I’ll test this option.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved noahd • about 2 months ago