a year ago
I'm experiencing a delay in custom domain propagation on Railway, even though the changes have already been propagated from Cloudflare.
š¹What I did:
Updated DNS records on Cloudflare (A/CNAME pointing correctly).
Confirmed propagation via DNS lookup tools (records are updated).
Flushed DNS cache on my local machine.
š¹Issue:
- Despite these updates, my custom domain isnāt resolving to my Railway-deployed site.
- Iāve waited for a while, but the domain still redirects incorrectly or fails to load.
- Railway panel still shows āPendingā for domain verification.
š¹Questions:
1ā£ Is there an additional Railway-side caching delay?
2ā£ Should I manually re-trigger verification or re-add the domain?
3ā£ Any troubleshooting steps specific to Railway + Cloudflare setup?
Would appreciate any insights! Thanks in advance. š
1 Replies
Status changed to Awaiting User Response Railway ā¢ over 1 year ago
a year 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 ā¢ 11 months ago