Arrived Yesterday
Binding fails - factory reset doesn´t change anything
Thanks in advance
Hello,
Please refer this guide to check:
BTW, please disable the VPN of the primary router.
I was able to rebind manually
I am accessing through GLKVM App - Blank screen with no options to interact (with GL-RM1 or remote desktop)
I have checked but did not help
PLease help with the blank screen now
A black screen usually means there is no correct signal source. When you connect HDMI to a normal monitor, can the desktop be displayed normally?
yes - normal display on differtent monitor
Its not just a blank screen - there are no taskbars or anything from the KVM app either that schould appear
Can you provide some screenshots?
Can you try the new app? It's not officially released yet, but you can test
unforunately I get an error message trying to load tghe new file?
Sorry I gave the wrong link, please use this one
This one also does not work
https://limewire.com/d/yeK6q#zFrl8smFPe
It seems that there is some problem with the forum identifying the link. The parameters after the # sign will be lost. I will first provide the link in code format.
At least for me it works now:
Thanks for your help
I am having the same issue. The device and app are on the same network and the app cannot find the device. Even manually adding the device serial number does not work.
What is odd however is that I can access the RM1 through the IP without an issue.
The app should give that choice as well, not only the S/N.
Upgrade the firmware on it to the most recently public release, if you have not done so already.
I bought 3, of which 2 came with an older firmware (1.0.0 maybe? I don't remember), and worked fine in the app. One was a newer firmware than that - 1.1.0, but still isn't the most recent public firmware. Like yours, that 1 unit, would not show up in the app.
When I looked at it from the DHCP server, it was registering itself with a different name/description than the others, and I don't think the client app recognized it.
I was able to correct it by logging in directly as you did through the IP, then upgrading the firmware to 1.3.0 release 1 (which was the current public version at the time). After rebooting, it then showed up (and named itself like the others).
Does your problem still exist?
Please send us the system log for inspection.
Yes, issue still exists even with the updates.
OK.
Please export the system log and send it to us for inspection.
https://fw.gl-inet.com/kvm/rm1/test/glkvm-RM1-1.3.1-0710-1752118006.img
If it is not convenient for you to export the log for analysis, you may try to use the test firmware.