Hi team, I have a railway node.js app that doesn't have a domain configured as it just runs background tasks. One of the background tasks involves making a request to a third party service that requires the domain origin of any requesting service to be added to a whitelist in order for their API to accept incoming requests. One exeption to this rule is if the request is coming from a localhost. Up until today things were working fine and then suddenly all requests started getting rejected by this third party service with a 403 Forbidden error. I believe thisis because the domain is not in the whitelist.

I'm not sure if the third party changed something or railway changed something that caused my app to no longer be recognized as a localhost, but now it seems that I need to add the domain of my app to They do not allow adding IP addresses to the whitelist. I tried generating a railway domain adding railway.app, up.railway.app, and my-service.update.railway.app to the whitelist, but requests are still being rejected with a forbidden error code

Are there any recent changes that could be causing this issue on the railway side? Also if a node.js app doesn't serve an api, what's the right domain that I need to whitelest to make things work again?