glkvm.com is not working
That is your corporate web content filtering blocking the connection.
It's probably related to this:
We are currently collecting information on related issues. If the problem persists, could you please provide your device logs, the location of the control device, and your ISP's name?
Device logs can be sent to this email address ([email protected]).
We apologize for any inconvenience.
The issue is Gl.net is using an expired SSL certificate. What needs to happen is a proper ssl cert should be used. That or offer non secure connection.
You can see the SSL cert below being used. Most browsers will block it, though a lot of them will let you get around it.
Thanks for your reply
This is a device-local service certificate. It operates independently from any access restrictions on the public domain glkvm.com, so it won't affect your remote access through glkvm.com.
@FloRa Yes and the certificate is expired. This certificate that you see when you try to go to the web page on the local device. This is what the post is trying to do an not go to a public web page.
The issue is the SSL certificate on the local device exposing the web page is not valid it Expired on December 29, 1979 !!!
This need to be fixed to be valid. Thankfully Chrome & Firefox will let you bypass it.
But this is a BIG issue. Really if don’t want to deal with SSL certificates should let users enable just using HTTP instead of HTTPS.
It's not a real issue because the cert is invalid anyway. Doesn't matter if an invalid cert is expired or not.
And it's not really possible to get a cert browsers will think is valid without an FQDN (meaning you'd need to do some work as a user to buy a domain and configure things - not practical for most consumers but can be done on the KVM since we've got access to the certs). Some vendors get around this the way GLiNet is trying to by creating a public hostname and controlling the cert, for example Western Digital uses a [UUID].remotewd.com hostname and a redirect to serve up a valid cert.
I would add as well that a KVM device isn't for users without any knowledge. So they know how to bypass the cert warning - mostly.