I just purchased the GL-RM1 over the weekend to use on my LAN at home. The entire home LAN is behind one router, peer-to-peer, nothing special. I set it up on Sunday, got the firmware on the GL-RM1 updated to V1.8.0 release 3 (RM1), and then updated to the latest windows client software. It worked great for 2 days, now it won’t connect with the Windows client (Windows 10 Enterprise LTSC 2019) anymore, showing an error at the bottom left of the window “Error connecting to the Janus WebSockets server: Is the server down?”
I found some old post where a support rep asked if the problem client could connect with a browser via GLKVM.com, so I tried that and it does work. Is this the only way to connect to the remote machine, by using a browser as the Windows client?
You know, this device worked fine for a couple days, so it proved that the device would work fine in the current environment. I don’t need all this trouble. I’ll just return it for a refund.
Unless of course you can fix the B.S. on your end and get it working again like it was when I purchased it.
I had the unit unplugged for a couple days, then plugged it back in to use it for a bit before returning it and it worked fine with the Windows Client. I assume the ‘server’ in the unit itself is crashing every day or two. If this gets solved, maybe it will be worth keeping around. I suppose I could plug it into a network plug and schedule a power down/up every morning or something, just seems silly for a new device.
I just rebooted my router today with a startling realization that every time this device has a very short loss of ethernet connectivity, I can’t connect to the it and the “Janus Websockets server” error, until I physically power cycle the unit. Even more surprising, the error only occurs when trying to connect with the Windows client across the LAN, so when that connection fails I have to use the web interface until I can manually power cycle the unit. As a temporary workaround until this is fixed, is there a way to power cycle the unit from the web interface?
Finally, please update the settings so I don’t have to enable audio _every_single_time_ I connect to it.
The issue where the KVM fails to automatically restore the network after an upstream outage is expected to be fixed in the firmware release 1.8.1.
You can restart KVM here.
Dude, you’re being a little hostile here. Relax just a little. In a chrome based browser, there’s zero lag introduced. The websockets are opened directly from chrome, it’s only http for the initial connection. When you click the full screen button, all special keys, and everything just works. It’s way more stable than the (windows) app. It’s not transcoding it to HTTP and sending across like that.
Been using RDC for years, never had this kind of lag. Describe how I would use a Chrome browser over the LAN (not connected to the Internet).
Just to sum things up, I (and many others) purchased a $100 product that’s clearly still in its beta testing stage, and other forum users are now starting to bring up potential security issues - for a piece of hardware that has the lowest level access possible to computers here in the US, by a Chinese manufacturer.
