Omada software controller 4.1.5 - Port 80 and port 443 are already in use

Omada software controller 4.1.5 - Port 80 and port 443 are already in use
Omada software controller 4.1.5 - Port 80 and port 443 are already in use
2020-08-06 10:59:45

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?

 

0
0
#1
Options
3 Replies
Re:Omada software controller 4.1.5 - Port 80 and port 443 are already in use
2020-08-07 08:24:55

Hi @wpvv,

 

could it be that you have a 1:1 mapping of ports between the container and the guest system and a web server is running on the guest system?

 

Just an idea. Maybe, the netstat running in the container can only list ports bound to successfully by an application in the container after such a mapping.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
0
#2
Options
Re:Omada software controller 4.1.5 - Port 80 and port 443 are already in use
3 weeks ago

@wpvv Hi. Where you able to fix it? I have similar problems.

0
0
#3
Options
Re:Omada software controller 4.1.5 - Port 80 and port 443 are already in use
3 weeks ago

@xelius hi, no to be honest I used a backup of the container with the standard port.

The only interesting thing that I found is that the controller will need root rights to use these ports (unfortunately just "sudo tpeap start" doesn't work), like seen here: https://grafana.com/docs/grafana/latest/administration/configuration/#http_port

I don't know what command to run to give the controller these rights

0
0
#4
Options