Describe the bug
A clear and concise description of what the bug is.
I realize that this is esoteric and probably not high on the requirement list but here goes.
NetLockRMM is set up on a server running Debian
Desktop computer on the same network running EndeavourOS
When connecting to Screen Control from another computer, it gets stuck on Connecting to Device
Docker logs for the relay indicates that it is trying to deserialize but fails with "Failed to deserialize device identity or device_identity is null"
Shell remoting works fine
To Reproduce
Steps to reproduce the behavior:
- Go to Tenant
- Go to EndeavourOS device
- Click on 'Screen Control'
- Accept the flag for pro features
- Forever connecting to device
Expected behavior
I had hoped that I would get access to my desktop remotely and be able to control the computer.
Screenshots
Desktop (please complete the following information):
- OS: EndeavourOS
- Browser Firefox
- Version: latest
Describe the bug
A clear and concise description of what the bug is.
I realize that this is esoteric and probably not high on the requirement list but here goes.
NetLockRMM is set up on a server running Debian
Desktop computer on the same network running EndeavourOS
When connecting to Screen Control from another computer, it gets stuck on Connecting to Device
Docker logs for the relay indicates that it is trying to deserialize but fails with "Failed to deserialize device identity or device_identity is null"
Shell remoting works fine
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I had hoped that I would get access to my desktop remotely and be able to control the computer.
Screenshots
Desktop (please complete the following information):