a month ago
Custom domain verified in UI but missing from backend service config — edge not routing
Service: Truefy_APP
Project: celebrated-serenity (production)
Domain: truefy.ru (apex)
Symptom: Domain shows as verified in the UI (CNAME @ → tmjogdi6.up.railway.app, TXT _railway-verify — both green). However getServiceConfig returns only truefy.up.railway.app — the custom domain is missing from the backend config. TLS handshake closes (ERR_CONNECTION_CLOSED), plain HTTP returns 503.
Ruled out on my side:
CAA records: none (Let's Encrypt not blocked)
DNSSEC: disabled (no DS/DNSKEY)
Apex CNAME flattening: working (Cloudflare, truefy.ru → A 69.46.46.81)
Service itself healthy: truefy.up.railway.app returns HTTP 200
Identical pattern previously on www.truefy.ru (cert issued, CN=www.truefy.ru, but domain not routed on edge).
This is a platform-side backend/edge config sync issue and needs your team's direct intervention. Please attach the domain to the service edge and confirm.
6 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
I'm able to access truefy.ru just fine. However, you need a TXT record on _railway-verify.www.truefy.ru.
a month ago
There have been other users in/around Russia who have reported not being able to access sites hosted on Railway. Unfortunately, if that's the case for you as well, your only option would be to use a VPN.
Railway isn't able to do anything about a regional/ISP block.
0x5b62656e5d
There have been other users in/around Russia who have reported not being able to access sites hosted on Railway. Unfortunately, if that's the case for you as well, your only option would be to use a VPN. Railway isn't able to do anything about a regional/ISP block.
a month ago
I already have a VPN, it's turned on 24/7.
0x5b62656e5d
I'm able to access `truefy.ru` just fine. However, you need a TXT record on `_railway-verify.www.truefy.ru`.
a month ago
Thanks! A couple of clarifications, because there may be a mismatch on the backend:
The active custom domain on this service is now the apex truefy.ru (I removed www.truefy.ru earlier — the free plan only allows one custom domain). Per Railway's own "Configure DNS records" dialog for truefy.ru, the required records are:
CNAME @ → tmjogdi6.up.railway.app ✅ (green in UI)
TXT _railway-verify → railway-verify=e64205ccfba339902a1f9f3f47c7a22c443f841c6df00db73e4ed0bcd706927d ✅ (green in UI)
Both are set and verified in the dashboard. The dialog did not ask for a www record.
You mentioned _railway-verify.www.truefy.ru — does the backend still have www.truefy.ru attached instead of the apex? If so:
Which verify token should the www record use? The dashboard only shows a token for the apex _railway-verify.
Or should I fully remove and re-add the domain to force a clean backend sync?
Also, re: access — from outside Russia (US-based server) the TLS handshake to https://truefy.ru still closes (ERR_CONNECTION_CLOSED) and plain HTTP returns 503, so it doesn't appear to be serving globally. Could you confirm which exact URL/protocol worked for you (https://truefy.ru)? That would help pinpoint whether it's an edge-routing issue on the platform side.
a month ago
If you're using your apex domain, then your current configuration is fine. I'm able to access it just fine from Taiwan.
Attachments