25 days ago
All 3 of my services in my "staging" environment that require inbound addressability have external domains setup in Cloudflare:
- actions-web
- rocket-web
- api-server
All of them match:
- CNAME record routing to the provided Railway proxy address
- TXT verification records indicated
The ONLY difference is that I do NOT have these setup for cloudflare proxy since the initial LetsEncrypt process requires access via http (not https) and Cloudflare ends up blocking the HTTP request otherwise.
I have waited over 36 hours for this to "resolve itself" but these domains are still showing up in the Service with the "DNS" lit up. When I click on that link for each of these three services, the ONLY difference that shows up (re: the automatic setup in Cloudflare between the existing records and the ones Railway proposes to create is the fact that the Cloudflare proxy is turned off. Everything else matches exactly (it doesn't even include the verification records in the confirmation because those are already identicatl).
Please advise.
4 Replies
25 days ago
All three custom domains (api-staging.revatto.com, staging.revatto.com, rocket-staging.revatto.com) are showing DNS propagated, verification confirmed, and valid SSL certificates on our end. If the dashboard still shows a stale indicator, a page refresh or briefly removing and re-adding the domain should update it, but your domains are fully working with HTTPS right now.
25 days ago
This thread has been marked as private. Any further activity in this thread will only be visible to you and Railway employees.
Status changed to Awaiting User Response Railway • 25 days ago
25 days 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 • 25 days ago
25 days ago
I can access your domains just fine. As the bot mentioned, try removing and readding the domains from your dashboard if a stale indicator is shown.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Awaiting Railway Response Railway • 25 days ago
0x5b62656e5d
I can access your domains just fine. As the bot mentioned, try removing and readding the domains from your dashboard if a stale indicator is shown.
25 days ago
Removing and REAdding the domains completely resets/refires the whole process (new railway proxies, etc) and runs the risk of running into LetsEncrypt rate limits.
Attachments
25 days ago
k. This might not be a Railway issue? Still do not understand whether or not I'm seeing the correct status in the UI or not, but I do see valid certificates provisioned for the domains.