10 months ago
I'm hosting a Python FastAPI backend application on Railway and have enabled public networking to expose my service. However, when attempting to access the application through the domain provided by Railway (getassist.up.railway.app), the site fails to connect. I have ensured that the application is deployed successfully, but it remains inaccessible from the provided URL. Please assist me in identifying potential issues causing this connectivity problem and advise on necessary steps to resolve it.
FYI : its been about 2-3 hours
5 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Getting both public and private networks to work
- 🧵 DNS Configuration Issue for Custom Domain popolnenie.kz
- 🧵 Deepgram WebSocket Streaming Connectivity Issue on Production (Trial Plan)
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
It's accessible, gen5ai
Are you still facing that issue? If yes, then please paste the screenshot of the browser window & network tab of the dev console which should be showing the errors ✌
Attachments
10 months ago
Gen5ai, this is a well-known issue that has arisen in the past couple of weeks. Some Internet Service Providers (ISPs) are blocking requests to the railway domain. Even I tried your website, which loaded for the Airtel network, while it was DNS_PROBE_FINISHED_NXDOMAIN for other networks.
You can refer to this post, in which I have told the ways to rectify this ISP restriction (to use custom domains): https://station.railway.com/questions/requests-to-backend-url-return-404-with-0ccf9b05#s1ah I am sure that would help. If so, then mark this as the solution once you are done with the rectification ✌
clashing
**Gen5ai**, this is a well-known issue that has arisen in the past couple of weeks. Some Internet Service Providers (ISPs) are blocking requests to the railway domain. Even I tried your website, which loaded for the Airtel network, while it was DNS\_PROBE\_FINISHED\_NXDOMAIN for other networks. You can refer to this post, in which I have told the ways to rectify this ISP restriction (to use custom domains): [https://station.railway.com/questions/requests-to-backend-url-return-404-with-0ccf9b05#s1ah I](https://station.railway.com/questions/requests-to-backend-url-return-404-with-0ccf9b05#s1ahI) am sure that would help. If so, then mark this as the solution once you are done with the rectification ✌
10 months ago
gen5ai, any update!
If it helped, then do close this thread by marking the helpful post as the solution
9 months ago
Any progress, gen5ai