-
|
Looks like this: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
|
Thanks for the report! This could happen if:
A few questions to help investigate:
If you can reproduce it, checking the browser console (F12 → Console) for any WebSocket errors when the host goes offline would be helpful. In the meantime, the Hosts tab showing correct status suggests the underlying detection is working - it might be a frontend state sync issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your quick reply.
In the beginning I had not the agent but the proxy mode I guess. Maybe there something went wrong with uninstall / install? Best regards. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the additional details. This appears to be a genuine bug where the Proxmox tab is showing stale data while the Hosts tab (using the agent) correctly shows the host as offline. To confirm: The Proxmox tab is likely still showing cached data from before the host went offline. Since you mentioned switching from proxy mode to agent mode, there may be some leftover configuration or cached state. A few things to try:
If those don't help, could you check Settings → Nodes and confirm how Automated triage - pulse-triage[bot] |
Beta Was this translation helpful? Give feedback.
-
|
Fixed in v5.1.35 @rcourtman |
Beta Was this translation helpful? Give feedback.





Fixed in v5.1.35 @rcourtman