21 days ago
ubject: Custom domain config not persisting on backend - certificate issuance never starts
Service ID: 94b935a7-3396-4d27-b3e2-61f4de514c38
Domain: www.frikelanser.co.il
My custom domain shows in the dashboard UI ("Waiting for DNS update") but is not actually saved in the service's backend configuration — the serviceDomains config only contains the default Railway domain, not my custom domain. DNS is fully correct and propagated — verified via multiple resolvers:
CNAME www.frikelanser.co.il → j7v4kv4a.up.railway.app
TXT _railway-verify.www.frikelanser.co.il → matches exactly what's required
I upgraded to the Hobby plan today and have removed/re-added the domain multiple times, each time getting a new CNAME target, but the domain never gets registered on the backend so certificate issuance never starts.
Could you please manually add the domain to my service and trigger certificate issuance?
1 Replies
21 days ago
The domain is registered on your service and the CNAME is propagated correctly, but ownership verification is failing because the TXT record at _railway-verify.www contains a leading newline character before the token value. The published value starts with a line break followed by railway-verify=9d18... instead of the token with no preceding characters. Remove and re-add the TXT record at your DNS provider, making sure the value is pasted as a single line with no leading whitespace or line breaks, and verification and certificate issuance will resume automatically once the corrected record propagates.
Status changed to Awaiting User Response Railway • 21 days ago
14 days 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 • 14 days ago