noVNC console not working #82

New issue

Open

opened 2021-01-20 13:23:47 +00:00 by rafael · 3 comments

rafael commented

2021-01-20 13:23:47 +00:00

(Migrated from gitlab.privaz.io)

No description provided.

rafael commented

2021-01-20 13:25:29 +00:00

(Migrated from gitlab.privaz.io)

The noVNC console proxy seems to be not working properly

the websocket is hardcoded to 8080, and that conflicts with our manager for now.

Anyway, as a workaround novnc.console.default can be set to false to use the previous version.

The noVNC console proxy seems to be not working properly the websocket is hardcoded to 8080, and that conflicts with our manager for now. Anyway, as a workaround novnc.console.default can be set to false to use the previous version.

rafael commented

2021-01-20 13:29:12 +00:00

(Migrated from gitlab.privaz.io)

The conflict might resolve itself after the following: #78 is fixed and rolled out in our environment

then we could map 8080 to websockets into the SVMs

However we dont use this kind of console that much...

The conflict might resolve itself after the following: #78 is fixed and rolled out in our environment then we could map 8080 to websockets into the SVMs However we dont use this kind of console that much...

rafael commented

2021-01-20 14:00:35 +00:00

(Migrated from gitlab.privaz.io)

mentioned in commit 6e377582dc

mentioned in commit 6e377582dcff77a2699404ac687004278bb3ee5e