2 months ago
Hello, dear readers. Can anyone tell me why the site doesn't work over Wi-Fi but works fine on a mobile network? What could be the issue?
10 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
Your Wifi may blocked railway network, You can try change your DNS to 1.1.1.1
mayori
Your Wifi may blocked railway network, You can try change your DNS to `1.1.1.1`
2 months ago
I tried changing it, but the problem persists for some reason. Anyway, thanks for the help, friend.
danil371d
I tried changing it, but the problem persists for some reason. Anyway, thanks for the help, friend.
2 months ago
What do you see when you access it with your WiFi network?
mayori
What do you see when you access it with your WiFi network?
2 months ago
I have an infinitely black screen that tries to load the site
danil371d
I have an infinitely black screen that tries to load the site
2 months ago
Can you try clear the DNS cache and open the deployment URL again?
2 months ago
It works through one provider, but doesn't work through other provider. Is this a DNS problem?
vstavskyi
It works through one provider, but doesn't work through other provider. Is this a DNS problem?
2 months ago
I don't even know, I have a dynamic Ip and the dns is assigned by itself
2 months ago
I have the same problem in Ukraine.
2 months ago
Assuming you're accessing the site via url *.up.railway.app?
Try one of these
Temporarily lower the router MTU to 1400. If the black screen resolves, it was never censorship at all.
Or Attach a custom domain
If a custom domain doesn't fix it, put a CDN in front of that domain. This moves the client-facing IP off Railway's new prefix entirely.
Can also try to access other sites you can find in this thread https://station.railway.com/community/what-are-you-building-on-railway-c3fff450 search for up.railway.app domains
2 months ago
I'll tell you what the reason was. I wrote to my provider and they said that the problem was with the higher-level provider, which caused a failure due to which my site wouldn't load. As they explained, there were problems and a failure on the server of the higher-level provider.