5 days ago
My service is returning host_not_allowed (403) for all requests on both my old domain fairway-production-0742.up.railway.app and new domain fairway-production-f260.up.railway.app. Billing is active, Hobby plan, $4.49 credits available, deployment shows green/active. The x-deny-reason: host_not_allowed header suggests my account's public networking is blocked at the proxy level. Can you investigate?
1 Replies
Status changed to Awaiting Railway Response Railway • 5 days ago
3 days ago
Good news, this has cleared. host_not_allowed shows up when a freshly generated up.railway.app domain hasn't finished syncing its route to your container at our edge yet. fairway-production-f260.up.railway.app is now serving your app directly — it returns your app's own 404 on the root path rather than a 403, so the block is gone.
Your account was never restricted at the proxy level, billing is active, and the deployment is green. The old fairway-production-0742 domain will keep returning 404 since you've switched off it.
Try hitting one of your real routes and you should be all set. Let me know if anything still looks off.
Noah
Status changed to Awaiting User Response Railway • 3 days ago