8 days ago
Service: 53d9001d-d3ea-4c9c-bb0e-ab4b8a5001b9
Some other services are unable to access it via private networking - error getaddrinfo ENOTFOUND postgres3.railway.internal.
May be the same situation as https://discord.com/channels/713503345364697088/1509760353204961451 - but I can't work around with Public Networking because that's still broken for me (per https://discord.com/channels/713503345364697088/1491862601662205982/1491862601662205982 from ~2 months ago)
7 Replies
Seems to be back to connectable after a re-deploy. Didn't feel confident enough to do a re-deploy after previous problems with that, especially when the volume was showing as 0GB (presumably metrics are broken on this service) --- but after managing to finally take a backup (took a long time to delete enough backups to have enough space), re-deploying did get it connectable again.
Interestingly, this has finally fixed my ability to connect via Public Networking too --- although I have actually started to appreciate having it not accessible to the public a bit.
im having the exact same issue! although, redeploying hasnt fixed it for me 🙁
8 days ago
Redeploying didn't fix mine so far. Tried 3 times
8 days ago
fixed by redeploying the postgres database
7 days ago
Always redeploy. The way Railway seems to work is based on proxies that will eventually fail when infrastructure runs into a hiccup. Consider remaking the service if metrics stay broken or you continue having issues - this suggests that the service itself may be misgenerated and their own cleanup services are working hard to fix it, but can't unless you give them a new artifact (by redeploying for instance). This does not guarantee that headers, attributions etc. will be completely remade.
The fact that the public proxy works backs this up, I believe it is routed through another proxy service - which seems to work fine.
Consider it like a key for a door. The key is slightly malformed so sometimes it works, sometimes it keeps you out in the rain and sometimes it jams the door. You either change the door or the lock, but really, it might not even be a lock problem, it could be the door itself that's bent and need replacing.