Hello All, Port 80 is being grabbed by the NT Kernel somehow and the WASP fails on binding to port 80 for being unavailable. Has anyone seen this behavior before?
No surprise wasp won't start if port 80 is already used. No idea what in "NT kernel" would want to grab it, but I am sure there are some tools in the sysinternals package that can help you identify it.
If you are unable to change what is using port 80, you just need to change the port that the wasp uses. One suggestion would be to change HTTP_PORT from 80 to 8080, and then add HTTPS_PORT = 443. So you start using https instead. Which is probably a good thing anyway
We kinda have the same issue since we run the wasp robot as non-root. Which means it's not allowed to bind to ports below 1024.
Retrieving data ...