We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The VNCProxy route gives back a UPID for a given task---including VMs https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu/{vmid}/vncproxy
And then you can use the API to monitor the status. Perhaps, if we store the UPIDs of the VNC sessions, then once per minute or so, we check the status of all of them (might have to throttle if the API gets sad), and then use that to remove Websockify targets. https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/tasks/{upid}/status
The text was updated successfully, but these errors were encountered:
Just a note for the future: We might be able to tie this into the redis work I'm doing in #158
Sorry, something went wrong.
WillNilges
No branches or pull requests
The VNCProxy route gives back a UPID for a given task---including VMs
https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu/{vmid}/vncproxy
And then you can use the API to monitor the status. Perhaps, if we store the UPIDs of the VNC sessions, then once per minute or so, we check the status of all of them (might have to throttle if the API gets sad), and then use that to remove Websockify targets.
https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/tasks/{upid}/status
The text was updated successfully, but these errors were encountered: