6 days ago
- Status 525 is being returned from Railway on existing custom domains
- Trying to set a new custom domain and it's stuck on a warning sign status
Help ASAP! Production apps aren't loading.
3 Replies
Status changed to Open Railway • 6 days ago
6 days ago
Already tried that (and I'm well familiar with AI responses), this didn't help. Issue isn't with CF.
6 days ago
HTTP 525 probably means Cloudflare can't complete an SSL handshake with Railway's origin.
Check your Cloudflare SSL/TLS setting (SSL/TLS -> Overview). If it's set to Full (Strict), Cloudflare expects a valid cert from Railway's origin - if Railway's cert for your domain expired or got invalidated, you'll get 525 across all domains simultaneously.
Quick fixes in order:
- Temporarily set Cloudflare SSL mode to "Full" (not Strict) - this often restores service immediately while the underlying cert issue resolves.
- For the new domain stuck on warning: that's a separate provisioning issue, i would propose to deal with the existing domains first.
- If Cloudflare is not involved and you're hitting Railway directly - share which domains are affected and Railway staff can check cert validity on the backend.
Immediate mitigation: Cloudflare SSL -> Full (non-strict) buys you time. What's your current Cloudflare SSL mode set to?
6 days ago
Tried that as well, same issue.