webots
webots copied to clipboard
Webots cannot startup on windows
Click the webots startup icon, using admin, but it also crashed in a few miniutes
ERROR: Could not listen to extern controllers and robot windows on port 1244. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1243. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1242. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1241. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1240. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1239. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1238. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1237. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1236. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1235. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. ERROR: Could not listen to extern controllers and robot windows on port 1234. Cannot set the server in listen mode: 杩欎 釜鍦板潃琚繚鎶や簡. Giving up. webots: failed to open TCP server in the port range [1234-1244]
This might be because you have Hyper-V enabled, causing Windows to reserve these ports (1234-1244). To check the system-reserved TCP ports, run the following command in the console in administrator mode:
netsh int ipv4 show dynamicport tcp
If it includes ports 1234-1244, you can change the reserved ports to 49152-65535 by running the following command in the console in administrator mode:
netsh int ipv4 set dynamic tcp start=49152 num=16384
Reference link: https://github.com/shadowsocks/shadowsocks-windows/issues/2171#issuecomment-603119696
oh, thanks. I will make a test soon
I recently encountered a similar problem on Linux, specifically the following error is output after waiting for a while:
ERROR: Could not listen to extern controllers and robot windows on port 1244. Cannot set the server in listen mode: Network operation timed out. Giving up.
Using sudo ss -tuln
to check, I found that my 1234 port was not occupied. After some attempts, I think it may be related to my network proxy.
After executing sudo systemctl stop [email protected]
and trying to start webots again, it will immediately report the following error:
ERROR: Could not listen to extern controllers and robot windows on port 1237. Cannot set the server in listen mode: Connection to proxy refused. Giving up.
I finally found that I could solve the problem by executing the following command:
unset http_proxy https_proxy all_proxy
I don't know much about network, so I don't know the reason, maybe there is something wrong with my network configuration.
I tried other versions, and R2022a
is the last version that does not have this problem. On my windows laptop, even with the proxy turned on, all versions can work normally.