Hello,
Version:
Pegaprox v0.9.9
Description:
when using noVNC Console access from the client portal, the socket connection will not be properly closed.
To reproduce:
You will have to reopen an console session multiple times until the webbrowser wont get a connection anymore in the "Client Portal"
Also on the Proxmox host, you will get a "TIMEOUT" for this connection, while when you are opening a connection through the main UI the connection wil be closed correctly.
Client Portal session Log:
May 11 16:48:34 pm03n01 pvedaemon[212086]: <xxx@pam!pegaprox_468581> starting task UPID:pm03n01:0003FFCD:39BDF07A:6A01EC42:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:48:34 pm03n01 pvedaemon[262093]: starting vnc proxy UPID:pm03n01:0003FFCD:39BDF07A:6A01EC42:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:48:44 pm03n01 pvedaemon[212086]: <xxx@pam!pegaprox_468581> end task UPID:pm03n01:0003FFCD:39BDF07A:6A01EC42:vncproxy:35004:xxx@pam!pegaprox_468581: connection timed out
WebUI session Log:
May 11 16:52:17 pm03n01 pvedaemon[233746]: <xxx@pam!pegaprox_468581> starting task UPID:pm03n01:000410A6:39BE478A:6A01ED21:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:52:17 pm03n01 pvedaemon[266406]: starting vnc proxy UPID:pm03n01:000410A6:39BE478A:6A01ED21:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:52:29 pm03n01 pvedaemon[233746]: <xxx@pam!pegaprox_468581> end task UPID:pm03n01:000410A6:39BE478A:6A01ED21:vncproxy:35004:xxx@pam!pegaprox_468581: OK
As you can see, the socket connection will be closed correctly from the WebUI, but not from the "Client Portal"
kind regards
Michael
Hello,
Version:
Pegaprox v0.9.9
Description:
when using noVNC Console access from the client portal, the socket connection will not be properly closed.
To reproduce:
You will have to reopen an console session multiple times until the webbrowser wont get a connection anymore in the "Client Portal"
Also on the Proxmox host, you will get a "TIMEOUT" for this connection, while when you are opening a connection through the main UI the connection wil be closed correctly.
Client Portal session Log:
May 11 16:48:34 pm03n01 pvedaemon[212086]: <xxx@pam!pegaprox_468581> starting task UPID:pm03n01:0003FFCD:39BDF07A:6A01EC42:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:48:34 pm03n01 pvedaemon[262093]: starting vnc proxy UPID:pm03n01:0003FFCD:39BDF07A:6A01EC42:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:48:44 pm03n01 pvedaemon[212086]: <xxx@pam!pegaprox_468581> end task UPID:pm03n01:0003FFCD:39BDF07A:6A01EC42:vncproxy:35004:xxx@pam!pegaprox_468581: connection timed out
WebUI session Log:
May 11 16:52:17 pm03n01 pvedaemon[233746]: <xxx@pam!pegaprox_468581> starting task UPID:pm03n01:000410A6:39BE478A:6A01ED21:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:52:17 pm03n01 pvedaemon[266406]: starting vnc proxy UPID:pm03n01:000410A6:39BE478A:6A01ED21:vncproxy:35004:xxx@pam!pegaprox_468581:
May 11 16:52:29 pm03n01 pvedaemon[233746]: <xxx@pam!pegaprox_468581> end task UPID:pm03n01:000410A6:39BE478A:6A01ED21:vncproxy:35004:xxx@pam!pegaprox_468581: OK
As you can see, the socket connection will be closed correctly from the WebUI, but not from the "Client Portal"
kind regards
Michael