net::ERR_CONNECTION_REFUSED (This site can't be reached — refused to connect)
The browser reached the host but nothing was listening on that port.
Exact message you may see
refused to connect
Seen on:
JavaScript
Meaning
Locally it usually means the dev server isn’t running or is on another port; in production the web server or load balancer is down or the port is firewalled.
Common causes
- Dev server not running / wrong port
- Web server stopped
- Using http:// to an https-only port or vice versa
- Firewall rejecting the port
⚡ Quick fix
- Start the server and check its port
- Use the right scheme and port
- Check the server process and firewall
Detailed fix by platform
Linux
ss -ltnp | grep :3000
How to diagnose
- Server — Is it listening on that port?
- Scheme — http vs https?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in JavaScript
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 9 Oct 2026