a month ago
Custom domain is stuck and cannot be re-attached to my proxy service. Every attempt fails with "Failed to create custom domain, please try again" with no further detail. Even generating a fallback *.up.railway.app domain on the same service fails identically. Confirmed not a DNS issue (clean single CNAME, resolves correctly), no platform incident, no maintenance notice.
Domain was successfully attached, then a service redeploy was triggered right after (before DNS had even propagated), and it's been stuck since — over 24 hours now, well past the window where similar cases self-resolved.
Project: Plane-Workflow
Environment: production
Service: proxy
Note: the proxy service doesn't even appear in this form's Service dropdown, despite being a real, currently-deployed service in this project (visible in the Railway dashboard) — every other service in the project shows up correctly. That's likely related to the same stuck state causing the domain issue.
1 Replies
a month ago
The custom domain is already registered on the proxy service and the CNAME is propagating correctly, so attempting to re-add it will fail because it already exists. The domain is not verifying because the TXT ownership-verification record is missing from your DNS. Custom domains require both the CNAME (which you have) and a TXT record at the verification hostname shown in the service's Settings, as documented here. Add that TXT record at your DNS provider with the value shown in the Railway dashboard for that domain, and once it propagates, verification and certificate issuance will proceed.
Status changed to Awaiting User Response Railway • 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 • about 1 month ago