Cannot access modem settings page

[Marcus_Aseth]

Hi, I have a "Sky Broadband Hub" modem, I'm using Windows 11 and Firefox as browser.

When I input 192.168.0.1 in the address bar, it gets replaced by https://myrouter.io/ and I get a page saying "we weren't able to find the site".

My connection functions normally and I have 4 green lights on the modem, is just that for some reason I have no way to access the modem admin page.
I've also tried from Edge (Microsoft's browser) and got the same result.

Is this a known problem, and there is a solution? 
I really need to access the setting because I'm pretty sure someone is stealing connection...

[JimM1]

@Marcus_Aseth Do the http: //192.168.0.1/ in the browser bar, take out the space between the colon and the backslash, the page get's corrected and turns it into a https that we dont want! See how it goes!

[Marcus_Aseth]

Firefox and most modern browser already do all that for you automatically, you don't need to type https:\\

[Marcus_Aseth]

@JimM1 besides the fact that the ip turns into https://myrouter.io/ already shows it was interpreted correctly

[JimM1]

@Marcus_Aseth Just in case you are not getting the s for secure is NOT wanted at all!!!!

[Marcus_Aseth]

s or no s, same result - is not a matter of http.

I've asked chatGpt, here what it has to say:

---

Direct answer: Yes, this is a known issue with Sky Broadband Hubs. The router’s admin page no longer works through 192.168.0.1 or myrouter.io. Sky has moved management of the hub to the Sky WiFi app (available on iOS and Android). You cannot access settings through a browser anymore

---

Can someone on this forum confirm?

[jtonline]

See this thread: https://helpforum.sky.com/t5/Broadband/myrouter-io-This-site-can-t-be-reached-but-the-internet-is-ac...

[JimM1]

@Marcus_Aseth No point in dragging it out any further, was on the SR203 web browser about 4 hours ago both wireless and wired.

Attached picture when cleared for viewing.

[Marcus_Aseth · Accepted solution]

@jtonline Thank you, that link solved my problem.

For people encountering this same problem in the future, the solution is simply to assign 192.168.0.1 as preferred DNS.

The steps to achieve that on Windows 11 are as follow (courtesy of AI)

---

Step-by-step: Add your router IP (192.168.0.1) as DNS

1. Open Network Settings

     * Right-click the network/Wi-Fi icon in the taskbar.
     * Select Network & Internet settings.

2. Choose your active connection

     * If you're on Wi-Fi: click Wi-Fi → your connected network → Properties.
     * If you're on Ethernet: click Ethernet → Properties.

3. Edit DNS settings

     * Scroll down to DNS server assignment.
     * Click Edit.

4. Switch to Manual

     * In the pop-up, change from Automatic (DHCP) to Manual.
     * Turn on IPv4.

5. Enter DNS addresses

     * Preferred DNS: 192.168.0.1
     * Alternate DNS: you can add a public DNS such as 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).

6. Save changes

     * Click Save.
     * Close settings.

---

[Marcus_Aseth]

Follow up, explanation for why it fixed the problem.

I had my preferred DNS 8.8.8.8

---

### 🔎 What happened
- When your **Preferred DNS** was set to `8.8.8.8` (Google), your PC sent all domain lookups directly to Google’s DNS servers.
- The Sky Hub’s admin page (`192.168.0.1`) doesn’t actually resolve through external DNS. Instead, the hub firmware redirects browsers to `myrouter.io`.
- `myrouter.io` is a **local hostname** that only resolves correctly if your PC asks the router itself (via `192.168.0.1` as DNS).
- With only `8.8.8.8` configured, your PC asked Google for `myrouter.io`. Google doesn’t know that name, so the lookup failed → “can’t find server.”

### ✅ Why it works now
- By adding `192.168.0.1` as the first DNS entry, Windows queries the router first.
- The router knows how to resolve `myrouter.io` (it maps it back to itself).
- Result: the browser can reach the admin page.
- If the router DNS doesn’t answer, Windows falls back to the secondary DNS (`8.8.8.8`), so external sites still resolve normally.

---

(this is what they AI says... take it with a grain of salt, but given it solved the problem, looks convincing enough)

[Chrisee]

@Marcus_Aseth as with many answers from AI it was partially correct as the newer white Sky hubs dont use the web interface to change settings instead you access them via the My Sky app. Actually your issue is not to do with DNS as the browser had the internal IP4 address you typed and would not have sent a DNS call but instead, like many modern browsers, was set to only load secure sites using https: so displayed a default error page.

This is a common issue these days which is why Sky have started using an app on newer hubs.