a month ago
Custom domain SSL provisioning appears stuck.
Project ID:
4b489855-500c-422c-9fdf-4d7350b0409c
Service ID:
39d5aaf6-7e59-47f2-b838-7b8e487fcfec
Environment ID:
766766f0-df71-4c0c-8045-26123924533b
Custom Domain:
orders.prodigytees22.com
Current Status:
CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
Time Stuck:
Approximately 2+ hours after DNS propagation and verification.
Verified:
- CNAME resolves correctly to Railway target
- Railway ownership TXT present and matches
- Additional ownership TXT present and verified
- No CAA records present
- Service healthy and accessible
- targetPort configured correctly (3000)
- Five other custom domains on the same Railway service have VALID SSL certificates
Observed Behavior:
Railway continues serving the default *.up.railway.app certificate for this domain rather than issuing the custom-domain certificate.
Can someone investigate this specific custom-domain registration and re-trigger or repair certificate provisioning if necessary?
6 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Hey justinb470,
Your DNS setup is solid, since your CNAME, TXT verification, and 5 other domains on the same service all check out, this is almost certainly a stuck cert issuance job on Railway's backend, not anything you can fix yourself.
A few things to try first:
- Remove and re-add the custom domain in your Railway service settings. This re-triggers the cert provisioning pipeline from scratch and often unsticks it. Your DNS records stay the same, just delete orders.prodigytees22.com from Railway and add it again.
- Check for Cloudflare proxy interference. if your domain is behind Cloudflare (orange cloud), SSL validation via ACME HTTP-01 or TLS-ALPN-01 can fail silently. Try setting the DNS record to DNS-only (grey cloud) temporarily until the cert provisions, then re-enable proxy if needed.
- If removing/re-adding doesn't work within 30 minutes, this needs a Railway staff escalation since you've provided your Project ID, Service ID, and Environment ID, a team member can directly re-trigger cert issuance on the backend.
Your IDs are already in the thread so staff can action it immediately. Tag @railway staff or open a ticket referencing this thread.
zx1234r
Hey justinb470, Your DNS setup is solid, since your CNAME, TXT verification, and 5 other domains on the same service all check out, this is almost certainly a stuck cert issuance job on Railway's backend, not anything you can fix yourself. A few things to try first: 1. Remove and re-add the custom domain in your Railway service settings. This re-triggers the cert provisioning pipeline from scratch and often unsticks it. Your DNS records stay the same, just delete orders.prodigytees22.com from Railway and add it again. 2. Check for Cloudflare proxy interference. if your domain is behind Cloudflare (orange cloud), SSL validation via ACME HTTP-01 or TLS-ALPN-01 can fail silently. Try setting the DNS record to DNS-only (grey cloud) temporarily until the cert provisions, then re-enable proxy if needed. 3. If removing/re-adding doesn't work within 30 minutes, this needs a Railway staff escalation since you've provided your Project ID, Service ID, and Environment ID, a team member can directly re-trigger cert issuance on the backend. Your IDs are already in the thread so staff can action it immediately. Tag @railway staff or open a ticket referencing this thread.
a month ago
This happens to all of my clients who connect their domain. The SSL provisioning spins for up to 24hrs but why does it get stuck every time? @railway
a month ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
a month ago
That's the point though, this is happening all the time and it's not a code issue. Railway keeps getting stuck. I don't want to have to remove and reattach and keep telling clients to update their DNS records again and again until railway decides to finally work properly. This should be working and is setup correctly but I'm putting in support tickets because it's clearly an issue and I'm just getting....well try again or just let it sit longer. There should be a solution not and I feel like the support is lacking on this issue. What options do we have besides try reattaching for each customer each time this happens and hope it actually works?
a month ago
It has been 2 days and still not response on this. This is clearly a railway issue that is going unresolved and the only solution I get is just keep trying again and again and hope it works this time. I have 2 SSL's still spinning waiting on railway. Can someone please look into this? @railway
16 days ago
You need to add a TXT record to _railway-verify.orders.prodigytees22.com. You can access the TXT record from the verificationToken property under status.