Nothing strange at all. The original post seemed to be all about accessing HA from a mobile device.
Mobile devices are exceptionally strict about dns names matching the certificate. An IP address will never be listed on a cert, not even as a SAN. Attempting to access HA internally by ip will generate a certificate error, which will cause a mobile device to refuse to connect to it.
As for a browser on a pc, if he only used http:// instead of https:// in the browser url (you kept only giving an IP and port, never specifying a protocol), this would also fail. Ha cannot respond to both http and https simultaneously. If you configure a certificate, you can no longer access it via http. The most likely course of events is that he accessed the system via http during initial config, and then configured a certificate. Then, subsequent connection attempts were likely made using the browserās autocomplete function from the browser history, which would have been http since thatās how previous connections were made.
I can access my router using either a host name or a local IP address using a mobile device or my desktop browser. It warns me itās a questionable certificate (itās self-signed), but it allows me to connect using https over the LAN if I explicitly allow it. Would a trusted certificate behave any differently?
Mine is working, although occasionally the mouse wheel stops scrolling until I refresh the page. Iāve never had the issue until recently. FWIW, all add-ons and the Firefox Enhanced Tracking Protection (Shield symbol in the URL box) are disabled. I should add, no issues with LAN access.
