Thinking back on it, I think I actually noticed this behavior while I was running the release candidate that was being offered although I brushed it off at the time due to other priorities and the fact it wasn’t causing any problems per se.
But I suppose that underscores the potential usefulness of community beta program or early adopter ring to help catch behavior like this before broad deployment.
Can we not mark this as solved? It’s not solved–it’s a workaround for a serious regression, and the fix is a file that might cause other problems later when it’s actually fixed.
I was hitting my head against the wall why I was getting block page from Cisco (from my ISP) and just ignored it and tried another browser to avoid any weird plugin problems (Firefox, which is equipped to do DNS over HTTPS; only now do I realize why it accidentally sidestepped the issue).
Confirmed stopping the proxy fixes it temporarily.
Tbh I’ve given up, this Router has far too many problems, most recent ive discovered intermittent disconnection of LAN devices were caused by it, i was initially blaming my APs, it has been removed from my network, at least until someone is able to port OpenWRT / Luci to it
I can’t even sell it, as the buyer will almost definitely return it immediately or file a chargeback
I sold my UCG Fibre thinking i was getting a more stable setup, how wrong was I…
Okay, well, you’re entitled to bail on this, but again as the OP I’d not mark this as solved.
I love my Alta equipment, and have had a generally excellent experience. Regressions happen, but the speed at which a DNS leak isn’t being fixed is concerning, given that I’ve seen things fixed much faster in the past. I wouldn’t touch anyhing from UniFi ever again, even if you paid me.