7 months ago
This site can’t be reached
jobstir-env.up.railway.app’s DNS address could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE
4 Replies
7 months 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 brody • 7 months ago
7 months ago
Have you checked your container port and logs? Is everything fine, or are there any errors?
7 months ago
Divyansh, this is a well-known issue, which has risen in the past couple of weeks. Some Internet Service Providers (ISPs) are blocking the railway domain requests. Even I tried your website, which loaded for the Airtel network, while it was ERR_NOT_CONNECTED 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
But the thing is I tried to open your server/endpoint with different networks. The DNS issue is because of the ISP limitations, but even when I switch to an ISP which does not block the request (Airtel), the URL gives 404 (not found error). So, that means even if you add custom-domain to yoru server, it is less likely to be active/accessible because there are some issues in how you are configuting the PUBLIC NETWORKING setting of your deployment
Go to the Railway dashboard, select the desired service -> Settings -> Public Networking
Make sure that you have copied the correct endpoint, and check the PORT your server is using is the same listed in the settings. If not, then do change it to the correct one. Also, you can try checking the HTTP/BUILD logs to check for any errors.
I hope that would help, if so, do mark my reply as the solution 
Attachments
clashing
Divyansh, this is a well-known issue, which has risen in the past couple of weeks. Some Internet Service Providers (ISPs) are blocking the railway domain requests. Even I tried your website, which loaded for the Airtel network, while it was ERR_NOT_CONNECTED 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#s1ahBut the thing is I tried to open your server/endpoint with different networks. The DNS issue is because of the ISP limitations, but even when I switch to an ISP which does not block the request (Airtel), the URL gives 404 (not found error). So, that means even if you add custom-domain to yoru server, it is less likely to be active/accessible because there are some issues in how you are configuting the PUBLIC NETWORKING setting of your deploymentGo to the Railway dashboard, select the desired service -> Settings -> Public NetworkingMake sure that you have copied the correct endpoint, and check the PORT your server is using is the same listed in the settings. If not, then do change it to the correct one. Also, you can try checking the HTTP/BUILD logs to check for any errors.I hope that would help, if so, do mark my reply as the solution
7 months ago
divyanshgawri, any update.
clashing
Divyansh, this is a well-known issue, which has risen in the past couple of weeks. Some Internet Service Providers (ISPs) are blocking the railway domain requests. Even I tried your website, which loaded for the Airtel network, while it was ERR_NOT_CONNECTED 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#s1ahBut the thing is I tried to open your server/endpoint with different networks. The DNS issue is because of the ISP limitations, but even when I switch to an ISP which does not block the request (Airtel), the URL gives 404 (not found error). So, that means even if you add custom-domain to yoru server, it is less likely to be active/accessible because there are some issues in how you are configuting the PUBLIC NETWORKING setting of your deploymentGo to the Railway dashboard, select the desired service -> Settings -> Public NetworkingMake sure that you have copied the correct endpoint, and check the PORT your server is using is the same listed in the settings. If not, then do change it to the correct one. Also, you can try checking the HTTP/BUILD logs to check for any errors.I hope that would help, if so, do mark my reply as the solution
7 months ago
Did my initial reply helped you!
If yes,then mark that post the solution 