Ubiquiti Dashboard Issue

Follow up: I put Firefox into Troubleshooting Mode and told it to Reset. I then went through and set my customizations, closed Firefox, and reopened it. Everything then worked.... for a while. The next morning it wasn't working again.

This is really a question for Unifi/Ubiquiti help channels as it needs some architectural knowledge around the solution used, but this sounds interesting:

Everything works if I'm not trying to connect via the web portal from the local network. (i.e. If I'm elsewhere or use my cellphone's hot spot, I can connect to my gateway via the web portal without any issues.)

I'll try to reiterate, if these are correct:

1. being on the home/local network accessing the device on 192.*/10.* IP from the same network works
2. using unifi.ui.com on that same local network renders broken UI
3. connecting the same machine via a different/unrelated network opens unifi.ui.com without any issue and you can manage the device?

One thing to enable/disable/change provider would be DNS–over–HTTPS in browser settings.

The other possibility however is that the unifi CDN is hosted by a cloud provider that doesn't like your ISP's traffic, e.g. the IP address of your original connection triggers some bot protections over at their side and fails some async loads of components.

(Or, your system holds some networking prefs per connection interface, so these change e.g. between your home wifi and your mobile hotspot; like e.g. filtering DNS, maybe even some VPN tunnel etc. — things that can impact the reliability of some connections, if e.g. IPv6 or HTTP/3 support comes into play, esp. in case the unifi management uses some loopback DNS tricks and similar…)

jbr, I would tend to agree with you and have posted there also. However, after doing a Reset in Firefox, it worked. The next morning, it didn't work again. Also, since it works in Edge on the same computer on the same connection, there does appear to be a Firefox component to this. So, I think it's a combination of things. Of course, this makes it even harder to track down.

Definitely. Firefox uses its own DNS, TLS or H/3 stack so it differs from others — and equally has a distinct connection signature for bot protection scoring and measures so it's also scored differently even on the same machine.

(Notably, unverified search assistant result claims Unifi portal uses Cloudflare as it's delivery/security solution… which… in general has mixed results for individual Firefox users, starting from anti–fingerprint measures to custom or synced prefs like tweaking audio or disabling webRTC etc. etc. having impact — and if ISP/IP scoring comes in the mix the results might be… pretty wild.)

Would you be able to check the Network pane of console (F12) and refresh the unifi page to see if anything on the waterfall of assets turns red with error codes and potential reasons for blocking or failing?

They might have a bug somewhere in the local access from the outside. Luckily they appear to reasonably fall back to the "online" mode and talk to the device via their cloud once you remove this permission — probably good to share with them or their user forums in case more people run into the same.

This permission is called "LNA" and it was added recently: Control personal device and local network permissions in Firefox (if you want to know more as to why: localmess.github.io is basically the reason without having to read between the lines…)

Already shared it with them. I'll add your description in the last paragraph to my post there.