So my hub updated from LG-RDK_7.6.20-2306.5 to LG-RDK_11.6.2-2410.1 just a sight disconnect over night and all when fine still in modem mode :D
But it seems VM wants you to connect to 192.168.100.1 by HTTPS now nothing to do with the browser like really! whats the point.
The point is just “security” — HTTP sends everything in clear text, including your hub login password. Forcing HTTPS means at least it’s encrypted on your local network (even if the self-signed cert is clunky). VM will say the point is to secure the login page. In practice it’s mainly cosmetic — encryption helps, but since it’s a self-signed cert it doesn’t add much for the average home user beyond looking “more secure.”
It’s actually quite annoying if you want to access the Hub web UI from an iOS/iPadOS device. Due to an iOS/iPadOS bug with untrusted certificates, when you say you want to continue to visit the site even though it is insecure the page doesn’t reload properly until you press the back button.
Also, if you ask me, the warnings you get for a self signed certificate are much more “scary” than the warnings you get for an unencrypted HTTP page. If I was a less technically savvy user I think I would be phoning Virgin Media to ask them why my router was insecure!
"bug with untrusted certificates" is that a web browser issue ?
Perhaps Firefox or Chrome or Opera would work.
Given you can now register SSL certificates by IP now and have it singed you would think VM would do that so we don't see a insecure connection to the hub IP...guess thats too much work for them to do...then again how would you validate that? unless the server giving you the certificate validates 192.168.100.1 on your behalf?
