App is running but not reachable in the browser
Your Schokr app says it is listening but the browser times out or refuses the connection. Check host, port, protocol and the URL you use.
Updated · 2 min read
If the console shows your app started but the browser times out or says "connection refused", the problem is almost always the host your app listens on, the port, or the URL you are typing. Work through these checks in order.
1. Listening on 0.0.0.0?
Find your app's startup line in the console. It should say 0.0.0.0, not 127.0.0.1 or localhost:
Uvicorn running on http://0.0.0.0:25571
Server listening at http://0.0.0.0:25571
If it says 127.0.0.1 or localhost, only the server itself can reach the app. Fix it as shown in binding to 0.0.0.0 and the right port.
2. The right port?
Compare the port in your startup line with the port in your server's Network section. They must match exactly. A common slip is leaving a framework default such as 3000, 5000 or 8000 in place.
3. The right URL?
Use the address and port from the Network section:
http://<server-address>:<port>
- Use
http://, nothttps://. Schokr does not add HTTPS, so anhttps://URL to your port will fail. - Include the port. Without it, the browser tries port 80, which is not your app.
- Some browsers silently upgrade to HTTPS. Type the full
http://URL, or test withcurl:
curl -v http://<server-address>:<port>/
4. Is the app still running?
Apps sometimes print "listening" and then crash a second later. Scroll further down the console and check the server status. See app crashes on start.
5. Does the route exist?
A 404 means you reached the app, which is good news: the network is fine, and the path does not exist. Try / or a health route you know exists.
6. Is something blocking it on your side?
- Some workplace, school or public networks block uncommon ports. Try from mobile data.
- Browser extensions and VPNs can interfere. Try a private window.
7. Host header checks
Some frameworks reject requests for unknown host names:
| Framework | Symptom | Fix |
|---|---|---|
| Django | Bad Request (400) | Add the host to ALLOWED_HOSTS |
| Vite preview or dev server | "Blocked request. This host is not allowed" | Set preview.allowedHosts or server.allowedHosts in the Vite config |
8. Check the status page
If several of your servers stop responding at once, check status.schokr.gg for incidents at your location.
Still stuck?
Share your startup log, the port from your Network section and the exact URL you are using in the Schokr Discord.