Omada software controller 4.1.5 - Port 80 and port 443 are already in use
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I have been using the Omada Software Controller version 4.1.5 for a week now. The controller is installed in an Ubuntu 20.04 container with nothing else installed other then the Omada controller. Recently I changed the HTTPS port for management and the HTTP for the portal to 443 and 80. Now the controller fails to start, according to server.log this is because: "Port 80 and port 443 are already in use. Release the ports and try again.".
Netstat -ltnp returns:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 114/mongod
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 86/systemd-resolved
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 132/sshd: /usr/sbin
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 339/master
tcp6 0 0 :::22 :::* LISTEN 132/sshd: /usr/sbin
tcp6 0 0 ::1:25 :::* LISTEN 339/master
This would indicate that port 80 and 443 are available. Can I manually change the ports that are used somewhere and why does the controller indicate that these ports are in use?
