usdzconvert_webui
usdzconvert_webui copied to clipboard
OSError: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions
Hi, I am trying to run the program as you've explained in the previous issue ("C:\Program Files\usdz_webui\Python\python.exe" "C:\Program Files\usdz_webui\usdz_webui.launch.py" in command prompt) but after installing all the dependencies successfully, I get the error mentioned above. Here are all the messages from the command prompt:
C:\WINDOWS\system32>"C:\Program Files\usdz_webui\Python\python.exe" "C:\Program Files\usdz_webui\usdz_webui.launch.py"
18:30 INFO: USDZ Converter located or installed successfully.
C:\Users\antoni\AppData\Local\usdzconvert_webui\instance\converter\pxr_usd_abc1710_py27_win64
18:30 INFO: Providing module with logger: usdz_webui.modules.ftp
18:30 INFO: Providing module with logger: usdz_webui.modules.settings
18:30 INFO: Providing module with logger: usdz_webui.modules.file_mgr
18:30 INFO: Providing module with logger: usdz_webui.modules.usdzconvert_args
18:30 INFO: Providing module with logger: usdz_webui.modules.job
Logging setup called: app.py
Any help would be much appreciated!
Hi, thanks for providing the error messages. The waitress module couldn't open your local port 5000 which either means:
- some other application is running on your localhost:5000, you can check that with opening a cmd prompt
netstat -ano | find ":5000"
if the prompt returns nothing it means there is nothing running on that port - some anti-virus is blocking the app or the port, so you need to anti-anti virus
If this port is really already in use on your machine: try to edit the file serve.py in the usdz_webui/pkgs directory in Line 13 port=5000
and change the port to something between 1024 - 50000
Hi, thank you so much, I really appreciate your help!
@tappi287 - Thanks to this:
if sys.platform == 'win32':
host = socket.gethostbyname(socket.gethostname())
port = 80
running this on windows forces the port to 80 (regardless of how it's set at the top) which is a little bonkers (especially since it's assigned to something more sensible - port 5000 - initially).
The chance that another service is bound to 80 is fairly high. In my case the domain resolution doesn't work that well either, but that's probably unique to my situation. I don't get forcing the port to 80 on Windows, though.