Support

This is almost always the browser silently upgrading the connection from http:// to https:// on its own. Most modern browsers — Edge in particular — automatically switch to more secure connections by default. Since the dMix 128's built-in web server only speaks plain HTTP (no TLS), the browser waits indefinitely for a secure handshake that will never arrive, which looks exactly like a stuck loading page.

Fix:

1. Type the address with the http:// prefix explicitly, e.g. http://169.254.x.x/.
2. If that doesn't help, turn off the browser's auto-upgrade setting:
   • Edge: Settings → Privacy, search, and services → turn off "Automatically switch to more secure connections whenever possible."
   • Chrome: Settings → Privacy and security → Security → turn off "Always use secure connections."
3. As a quick test, try a different browser (Chrome or Firefox) — if it loads there but not in Edge, that confirms the auto-upgrade setting is the cause.

Before touching the browser, confirm basic network connectivity first: the console uses a link-local IP (169.254.x.x, no DHCP server involved), so your computer needs an adapter address in that same range to reach it at all.

1. Press Win + R, type ncpa.cpl, press Enter.
2. Right-click the Ethernet adapter connected to the console → Properties.
3. Select "Internet Protocol Version 4 (TCP/IPv4)" → Properties.
4. Leave it on "Obtain an IP address automatically" (Windows will pick a 169.254.x.x address the same way macOS does), or set a static IP manually — e.g. 169.254.x.x, subnet 255.255.0.0.
5. Run ipconfig — the adapter should show a 169.254.x.x address — then ping the console's IP before touching the browser.

If ping succeeds but the page still won't load, it's the browser HTTPS auto-upgrade issue above, not a network problem.