-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Desktop connection is not automatically disconnected upon idle timeout #5820
Comments
ok the code just simply diverts you to the |
have you tried restarting the meshcentral and also closing ur browser and reopening it then trying again? |
I've tried reseting the mesh itself and also restarting the machine and still not working for me. |
i will look at it again tomorrow, but all seems to work fine here which is weird? |
i still cant get it to show the message, it closed the desktop as it should and then diverts to the logout page. |
Adding the clip. It's in German so sorry in advance, Desktop.mp4 |
FireFox 64bit on Linux Mint. The same happens in Edge on a Windows machine. |
ive just through, whats your full config.json? (as the config doesnt look complete above) |
Can we do it agin later today in the evening? |
sure, my email on my github profile, or leave a comment on my dontation page and i can email you |
just updating this issue for future for others
|
Describe the bug
with "userSessionIdleTimeout" in the Config file, when using the Desktop to connect to another device, the browser is prompting a confirmation request for leaving or staying in the site.
This is true to the Desktop and not the RDP as I didn't test it on RDP.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Disconnecting the Desktop connection upon idle timeout
Screenshots
If applicable, add screenshots to help explain your problem.
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Additional context
Add any other context about the problem here.
Your config.json file
The text was updated successfully, but these errors were encountered: