noVNC woes (Win7 64, with UltraVNC, Python 3.2.3)

1,274 views
Skip to first unread message

Matt Sagen

unread,
Apr 12, 2013, 1:04:29 AM4/12/13
to no...@googlegroups.com
Hi all,

I am very excited about the possibilities with noVNC for a new project.

I am a designer+php+js+flash, but alas, I have a strong aversion to configuring services and servers, and I am having no success getting this going.

I have followed this thread about symlinks and I think that symlinks are no longer necessary, as there are already files called websockify and websockify.py in the utils directory...

I know that I have UltraVNC installed properly, because I can use it's in-built Java viewer.  You can see on attached settings file that Loopback  Connections are enabled.

When I got the order of the Ports correct, I got a security dialog, and allowed it, but then here is what I got:
=================================================
C:\Users\Owner\Desktop\kanaka-noVNC-v0.4-61-gcededc4\kanaka-noVNC-cededc4\utils>
C:\Python32\python.exe websockify :7000 127.0.0.1:5900
WARNING: no 'numpy' module, HyBi protocol is slower or disabled
WARNING: no 'resource' module, daemonizing is slower or disabled
WebSocket server settings:
  - Listen on :7000
  - Flash security policy server
  - No SSL/TLS support (no cert file)
  - proxying from :7000 to 127.0.0.1:5900

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Python32\lib\multiprocessing\forking.py", line 368, in main
    prepare(preparation_data)
  File "C:\Python32\lib\multiprocessing\forking.py", line 491, in prepare
    '__parents_main__', file, path_name, etc
  File "C:\Users\Owner\Desktop\kanaka-noVNC-v0.4-61-gcededc4\kanaka-noVNC-cededc
4\utils\websockify.py", line 1, in <module>
    websockify
NameError: name 'websockify' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Python32\lib\multiprocessing\forking.py", line 368, in main
    prepare(preparation_data)
  File "C:\Python32\lib\multiprocessing\forking.py", line 491, in prepare
    '__parents_main__', file, path_name, etc
  File "C:\Users\Owner\Desktop\kanaka-noVNC-v0.4-61-gcededc4\kanaka-noVNC-cededc
4\utils\websockify.py", line 1, in <module>
    websockify
NameError: name 'websockify' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Python32\lib\multiprocessing\forking.py", line 368, in main
    prepare(preparation_data)
  File "C:\Python32\lib\multiprocessing\forking.py", line 491, in prepare
    '__parents_main__', file, path_name, etc
  File "C:\Users\Owner\Desktop\kanaka-noVNC-v0.4-61-gcededc4\kanaka-noVNC-cededc
4\utils\websockify.py", line 1, in <module>
    websockify
NameError: name 'websockify' is not defined
=================================================

I appreciate anyone's help in the matter.

Matt


ultravncsettings.gif

Joel Martin

unread,
Apr 12, 2013, 10:28:37 AM4/12/13
to no...@googlegroups.com
Matt,

Unfortunately, using websockify on Windows is not well supported because I don't regularly use a Windows system (also making it difficult for me to debug things like this). The key issue is that websockify uses a forking model for handling multiple clients and the way this works in Windows is quite different. In windows, the multithreading module has to reload the source from disk when it forks a new process. From your error it looks like the code is not being found. This might be due to a refactoring of websockify a few months ago to make it more modular. I suspect this is a pathing issue, but like I said, I don't really have an easy way to debug this myself. All the work to get websockify running within Windows was done by others.

You might try posting in the github issue that you linked to (https://github.com/kanaka/websockify/issues/2) and explain your problem. Some of the others with more Windows experience might still be listening.

You might also try using the JavaScript (Node.js) implementation of websockify. It has more limited functionality than the python implementation but it shouldn't have the same issues with forking.

Regards,

Joel Martin (kanaka)

Ivan Derevyanko

unread,
Oct 8, 2013, 3:54:07 PM10/8/13
to no...@googlegroups.com
Just copy websockify to websockify.py with replacing. 

code...@gmail.com

unread,
Jul 14, 2014, 5:01:26 AM7/14/14
to no...@googlegroups.com
I have this method  ,but it  just don't work .
Reply all
Reply to author
Forward
0 new messages