mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 10:05:56 +03:00
[GH-ISSUE #53] Unable to use VM console #41
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gilbertoferreira on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/53
Hi...
When try to open VM Console I got this:
Connection Error
For self-signed certificates:
Open this link in a new tab:
https://192.168.122.198:444/
Accept the certificate in your browser
Come back and try again
If I click Accept Certificate, I got it:
https://:444
Failed to open a WebSocket connection: invalid Connection header: keep-alive.
You cannot access a WebSocket server directly with a browser. You need a WebSocket client.
If I click open in Proxmox or External, I got this:
https://undefined:8006/?console=qemu&novnc=1&vmid=101&node=proxmox01
Thanks
@gilbertoferreira commented on GitHub (Feb 21, 2026):
Oh! Never mind.... After some minutes, console appears.
But the External link still leads to https://undefined:8006/?console=qemu&novnc=1&vmid=101&node=proxmox01
Thanks.
@gilbertoferreira commented on GitHub (Feb 23, 2026):
I'm sorry to reopen this thread, but it's seems something wrong still happens.
When click in external, is calling the correct IP from my Proxmox VE, however it's showing this:
Do I need to do something in PVE side?
Thanks
@mkellermann97 commented on GitHub (Feb 23, 2026):
Hi @gilbertoferreira ,
Unfortunately, this is a Proxmox-side issue that we can't fix – we're just using their API.
Currently, we use a session code for this, which unfortunately doesn't work with the external view.
Regards,
Marcus