a month ago
Hello Railway team.
I'm experiencing an issue with the routing of a custom domain that returns HTTP 502 with x-railway-fallback: true, even though the service is healthy. I need help reconfiguring the edge.
Technical details
Domain: barberslim.com.br (apex)
Railway project: barberslim (id 1aeae3e6-f515-4725-9f6b-a628d2b9bbb5)
Service: barberslim (id 671944d1-a2fc-4d36-9c93-718b9c649551)
Service instance: 5845d6cd-864c-414f-adee-b1d39b38bfc5
Custom domain ID: 3fd05045-894b-49c2-9dcc-e0d6f6e0bf5c
Edge ID: edge-6705e5cc5ae5e82ae931d2b1f900f08f
Symptom (reproduced on 29/08/2026, ~23:50 UTC)
Accessing https://barberslim.com.br/:
HTTP 502 "Application failed to respond"
server: railway-hikari
x-railway-fallback: true
x-railway-request-id: RrnC4a_CR1Gfrc3kN8N_Fg
x-railway-edge: sjc1
x-hikari-trace: sjc1.hqvw
The same error occurs when forcing the edge IP (69.46.46.86) with the Host header set to barberslim.com.br.
Checks I have already confirmed (not code, not DNS)
Item Status
DNS A record barberslim.com.br ✅ 69.46.46.86 (Railway edge)
Custom domain registered ✅ (edge ID above)
SSL certificate (Let's Encrypt) ✅ CN=barberslim.com.br, valid until 27/11/2026
Latest deployment ✅ status SUCCESS (id 57112c5f-cf02-40a4-b0ba-eb9503e30168)
Instance active ✅ sleepApplication: false
Healthcheck path empty (no custom healthcheck)
Proof that the service is healthy
The instance's direct URL responds HTTP 200 normally:
https://barberslim-production.up.railway.app/ → 200 (title "BarberSlim — Barbearia | Agendamento Online")
In other words, the problem lies exclusively in edge routing (x-railway-fallback: true + server: railway-hikari indicates the edge is serving the fallback instead of the active instance). This is not misconfiguration on my side nor a code issue.
Request
Please reconfigure/clear the routing for the custom domain barberslim.com.br on the edge to point to the active instance 5845d6cd-..., or let me know if there is anything pending on your end. If you need another x-railway-request-id, let me know and I'll provide new ones.
Thank you in advance.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your DNS, certificate, and domain verification are all correct, and your service is responding on its railway.app domain. The edge routes for your custom domain were not installed, which is why it was serving the fallback page. We have started a routing repair for the domain, and it should begin serving traffic within a few minutes.
Status changed to Awaiting User Response sam-a • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 30 days ago