Closed srquentin closed 9 years ago
It appears that symlinks are broken in your checkout somehow. Are you on Windows perhaps?
Both utils/websockify.py and utils/wsproxy.py should be symlinks to utils/websockify.
Also, I just pushed a change to launch.sh so that it will try and use utils/websockify directly rather than via the wsproxy.py symlink. That should help your problem.
I'm closing the issue. If you still have an issue, please post back and I'll re-open it.
Hi~ I'm new to noVNC, i downloaded files from github, and i found no websockify.py or websockify directory in utils, is the launch.sh instead of it ?
Currently, launch.sh will try to either use a system-installed websockify or download websockify if it can't find it under utils. We switched to this system to avoid having to manually keep noVNC's bundled copy of websockify in sync (i.e. we no longer bundle websockify).
Thanks for DirectXMan12, and i have solved this problem.
Hi all,
I'm new to noVCN, and I've got issue to my first connection:
When I launch >./utils/launch.sh --vnc localhost:5901
I encounter some error shown below.
wsproxy.py: line 1 : websockify : command not found. Fail to start WebSockets proxy.
Could you please tell me how to solve this problem? Thanks a lot!