shulemmosko closed issue #8332: noVNC -Websocket issue after upgrading from
4.17 to 4.18
URL: https://github.com/apache/cloudstack/issues/8332
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the spe
shulemmosko commented on issue #8332:
URL: https://github.com/apache/cloudstack/issues/8332#issuecomment-1847698810
@weizhouapache
Ok then i guess we need to go back and have a look at issue#8310
--
This is an automated message from the Apache Git Service.
To respond to the messa
weizhouapache commented on issue #8332:
URL: https://github.com/apache/cloudstack/issues/8332#issuecomment-1847697625
> The cloudstack agents i tried upgrading but it would not connect to the
management server see issue #8310 so I had to downgrade them to 4.17.2
that explains. The clo
shulemmosko commented on issue #8332:
URL: https://github.com/apache/cloudstack/issues/8332#issuecomment-1847689665
Yes the systemVM template is using 4.18.1.0.
The cloudstack ag
shulemmosko commented on issue #8332:
URL: https://github.com/apache/cloudstack/issues/8332#issuecomment-1847683433
@rajujith @weizhouapache
If i change the websocket port to 8080.
shulemmosko commented on issue #8332:
URL: https://github.com/apache/cloudstack/issues/8332#issuecomment-1847681103
@rajujith @weizhouapache
Here you can see that the consoleproxy VM is not listening on port 8443.
