You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Loosing power state when upgrading MC from one version to another
To Reproduce
All agent have some power state, after upgrade of MC power state is gone and showing info after the upgrade only, no old information shown.
Expected behavior
To keep power state records when upgrading MC
Screenshots
Upgraded to the latest 1.1.33 yesterday from 1.1.32
Server Software (please complete the following information):
OS: Debian
Virtualization: none
Network: LAN/WAN, nginx reverse proxy
Version: 1.1.33
Client Device (please complete the following information):
Device: [e.g. Laptop]
OS: [e.g. Ubuntu]
Network: [e.g. Local to Meshcentral, Remote over WAN]
Browser: [e.g. Google Chrome]
MeshCentralRouter Version: [if applicable]
Remote Device (please complete the following information):
Device: All client devices
OS: Windows 10, windows 11, Linux
Network: Local to Meshcentral and Remote over WAN
Current Core Version (if known): Current Core: Dec 9 2022, 679808363
Your config.json file
If you really need it can post it, but not sure if this is configuration issue. Thanks
The text was updated successfully, but these errors were encountered:
This problem has happened to me several times. After the upgrade or suddenly (after some time), the connection with the agent is automatically disconnected...
Describe the bug
Loosing power state when upgrading MC from one version to another
To Reproduce
All agent have some power state, after upgrade of MC power state is gone and showing info after the upgrade only, no old information shown.
Expected behavior
To keep power state records when upgrading MC
Screenshots
Upgraded to the latest 1.1.33 yesterday from 1.1.32
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Your config.json file
If you really need it can post it, but not sure if this is configuration issue. Thanks
The text was updated successfully, but these errors were encountered: