Skip to content
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.

Start vnc process first #10

Open
yuvipanda opened this issue Nov 20, 2019 · 0 comments
Open

Start vnc process first #10

yuvipanda opened this issue Nov 20, 2019 · 0 comments

Comments

@yuvipanda
Copy link
Owner

Since 18d7fb7, we don't actually start the websockify process until /vnc is hit. This causes intermittent failures where the websocket isn't up quick enough for noVNC to treat it as up, and stuff fails.

yuvipanda added a commit that referenced this issue Nov 20, 2019
Removes the server extension, so the HTML for the interface
*is* served by websockify itself. This is a fix for
#10
This reverts commit 18d7fb7.
cmd-ntrf pushed a commit to cmd-ntrf/jupyter-desktop-server that referenced this issue Feb 4, 2022
Removes the server extension, so the HTML for the interface
*is* served by websockify itself. This is a fix for
yuvipanda#10
This reverts commit 18d7fb7.
yuvipanda added a commit that referenced this issue Jan 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant