Your custom domains (lingopeek.com, serplet.com, photostark.com) all show as verified with valid certificates and propagated DNS on our side, so there is no issue on the Railway end. Since you're using Cloudflare with proxying enabled, please ensure your Cloudflare SSL/TLS mode is set to "Full" (not "Flexible" and not "Full (Strict)") as described in our Cloudflare configuration docs.

https://cleanshot.com/share/RBWdbK1JX6c1lM3lq3B6

Same by me, I have two services with cloudflare domains, one is a proxy, I had to use a railway generated domain for the upstream, to avoid this error, I thought this might be related to the fix that is mentioned here so I left a comment there too: https://station.railway.com/questions/503-error-2fa95090#36dn

Everything looks correct on our end. You'll need to reach out to Cloudflare as we have no control over their side of things.

No, it's not a Cloudflare issue — it's how your automatic domain configuration wizard sets things up.

Here's the situation: your wizard creates a "proxied" (orange cloud) DNS record in Cloudflare. For one of my websites (serplet.com), this works perfectly. For another website (lingopeek.com), with the exact same Cloudflare proxy configuration, it throws Error 1000. Even after switching off cloudflare proxy mode to DNS only - website still don't work (getting infinite redirect).

Same Cloudflare setup, same proxy mode, different results — the only variable is how Railway handles the routing on your side.

Could you please investigate whether your domain wizard is correctly configuring the upstream for both services? This doesn't seem like something Cloudflare support would be able to help with.

If your record is pointing to a .up.railway.app domain using a CNAME, it'll be routed correctly on our end. The error you see is from the Cloudflare platform. Can I see your DNS configuration on Cloudflare for the broken domain?