a month ago
My custom domain www.s3pmp.com is showing "Cloudflare proxy detected" in Railway's networking panel, but there is no Cloudflare involved at all.
Full DNS chain:
www.s3pmp.com → CNAME → wq5c4e7q.up.railway.app → 66.33.22.101
IP 66.33.22.101 is owned by AS400940 Railway (Railway's own ASN)
DNS provider is Names.co.uk (nameservers: phase8.net) — no proxy, no CDN
Railway is incorrectly flagging its own IP range as Cloudflare, which is blocking SSL certificate issuance. The domain resolves directly to Railway with no intermediary.
Please manually trigger SSL certificate issuance for:
Domain: www.s3pmp.com
Service ID: 70f0c972-d20d-4ffd-ab0b-32012deaf516
Project: inspiring-light / capital-markets-platform
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 • 28 days ago
a month ago
Delete the domain from your Railway dashboard, wait 10 minutes, and re-add it.
This is a known bug where Railway’s Fastly edge proxy incorrectly flags its own IP range as Cloudflare. Deleting and re-adding forces a fresh edge sync, clears the cache, and triggers the automated SSL issuance process.
dev-charles254
Delete the domain from your Railway dashboard, wait 10 minutes, and re-add it. This is a known bug where Railway’s Fastly edge proxy incorrectly flags its own IP range as Cloudflare. Deleting and re-adding forces a fresh edge sync, clears the cache, and triggers the automated SSL issuance process.
a month ago
have tried that and it doesnt work
capmarkets
have tried that and it doesnt work
a month ago
I think what you'll have to do here is you must force delete the domain using the Railway API directly instead of using the regular Dashboard, Use Railway's GraphQL API to force-purge the broken domain metadata. you can see more here: https://docs.railway.com/integrations/api/manage-domains
dev-charles254
I think what you'll have to do here is you must force delete the domain using the Railway API directly instead of using the regular Dashboard, Use Railway's GraphQL API to force-purge the broken domain metadata. you can see more here: https://docs.railway.com/integrations/api/manage-domains
a month ago
tell me if it works
dev-charles254
tell me if it works
a month ago
no unfortunately didnt work
a month ago
It may take up to a few hours (maybe even a day, but rarely) for Railway to validate the DNS and issue a certificate.
Also, it seems like you have set up a routing rule to redirect traffic going to www to @. Make sure that's not being set in your DNS provider.
If you don't have that sort of rule set up, I'd recommend migrating to Cloudflare's DNS service to avoid these issues.