Hey there! We've found the following might help you get unblocked faster:

• 🧵 Streamlit 502 Bad Gateway Error

• 🧵 App deploys successfully but returns 502 Bad Gateway

• 🧵 502 Bad Gateway

• 🧵 502 Bad Gateway Error

If you find the answer from one of these, please let us know by solving the thread!

These do not really help. I have changed the domain. I just want to confirm that it is just to do with waiting and not with my configurations or something.
CNAME
@

gzcjgqyp.up.railway.app

I had a quick look at your application. You recently changed your REACT_APP_API_URL variable, and the current value of that variable is a list of two different URLs. You may want to set it to just a single value.

Furthermore, consider using the built-in private network for better performance and security (and reduced networking costs). Read about Private Networking in the Docs: https://docs.railway.com/guides/private-networking

Thanks for the link, but my issue isn't with private networking.

Problem: My frontend loads fine at ticketvault.net, but I get 502 Bad Gateway errors when making API calls to the backend endpoints (like my-tix.net/api/auth/login, /api/admin/users, etc.).

Current setup:
screenshot attached

Specific symptoms:

• Static site/frontend works

• Any fetch() calls to /api/* endpoints return 502

• Same API calls work fine on the Railway-provided domain

This seems like a public networking configuration issue where static content serves but API routes aren't being properly proxied through Cloudflare to the Railway backend.

Could you help with the correct configuration for API routing through custom domains with Cloudflare proxy enabled?

My Railway-provided domain works perfectly, but my custom domain returns 502 Bad Gateway errors for all requests.

Working:

• https://ticketvault.up.railway.app/api/auth/login → works fine

Not working:

• https://my-tix.net/api/auth/login → 502 Bad Gateway (returns HTML instead of JSON)

Configuration:

• Custom domain: my-tix.net

• Railway service: gzcjgqyp.up.railway.app

• Cloudflare: CNAME my-tix.net → gzcjgqyp.up.railway.app (proxied)

• SSL/TLS: Full

Question: Since the Railway domain works but the custom domain doesn't, this seems like a domain routing issue. Is there something specific about how my-tix.net should be configured differently than the working Railway domain?

The fact that I get HTML error pages suggests requests aren't reaching my FastAPI backend through the custom domain.

Thanks!

Both the Railway domain and the custom domain work for me. I'm going to move this thread to the community, as the issue would be outside of Railway's control.

https://station.railway.com/questions/dns-configuration-issue-for-custom-domai-10696e8a#fcrf

jaliljzarifa, you can check my post on how to configure custom domain. BTW, is your custom domain setup in Railway showing Setup Complete (like shown in the image)?