Constant disconnects since firmware upgrade

I have an RM1 connected locally. Ever since the most recent firware upgrade, it seems to disconnect constantly. Often in less than a minute from reconnection. Disconnects were rare before the upgrade. That’s the only change that has occurred.

system_logs_20260407_150351.zip (80.4 KB)

To help us narrow things down:

  1. Are you accessing the KVM via the App or a browser?
  2. Have you tried adjusting the EDID settings?
  3. Are you using the original HDMI cable?
  1. App

  2. I’m using a custom EDID for 3440x1360

  3. Yes

Does the same issue happen when you access the device locally using its IP address?

If possible, could you also try adjusting the EDID settings and testing with a different resolution to see if the issue still occurs?

Hi, it appears that the connection remains with the browser and only fails with the app. I had both open today and the app failed but the browser is still working. I didn’t notice any difference when using different EDIDs.

Could you pls export the app's logs here?

glkvm_app_log.txt (4.8 MB)

It looks like the logs were overwritten. The next time the issue occurs, could you please export both the device logs and the app logs again right away?

glkvm_app_log.txt (3.8 MB)

Here you go. I had to parse some of the older logs from the app log because the file was too large.

system_logs_20260409_142646.zip (102.0 KB)

Thanks for the logs!
Are you using any VPN services?

If so, could you try temporarily disabling them and see if the issue still occurs?

And could you share a screenshot or short video of the issue when it happens?

Hi, no VPN services. I can’t share a video because of intellectual property constraints but the screen just goes white for a few seconds and I get this:

It seems to happen in bursts. It will happen 4-5 times in a row every minute or so and then no issues for hours.

We've identified that the issue is caused by the client detecting an unstable network connection during access. We plan to improve this in a future release.

In the meantime, we recommend using local access via a browser as a temporary workaround.

Really sorry for the inconvenience this has caused.