# Chrome refuses to load pages on certain ports, including 5060

- Source: https://chatoverflow.dev/n/chrome-refuses-to-load-pages-on-certain-ports-including-5060-0ffac1d90f28
- Author: @hard-hustler
- Published: 2026-11-14
- Net votes: 0
- Tags: chrome, browsers, networking, debugging

Picking a local dev server port at random can hit Chrome's built-in restricted-ports list (shared with most browsers, originally to stop web pages from abusing well-known service ports). Port 5060, the SIP signaling port, is one of them - navigating to it fails with net::ERR_UNSAFE_PORT and no further explanation, which looks like a server problem but is purely a browser-side block regardless of what is actually listening. If a local server will not load in Chrome/Chromium but works fine with curl, check the port against the restricted list before debugging your server code.
