Reply
New Member
Posts: 2
Registered: ‎11-21-2017
Solutions: 1
Accepted Solution

Unable to connect to adopt AP v2s after port change on controller.

Hi All,

I am having an issue with our setup at work. We have a physical server that is hosting the unifi controller software and all seems to be working well for most APs (UniFi AP v2) however, I have two which are being very awkward when it comes to the adoption process.

In the past I have had similar issue with enrolment and I have ran the usual "syswrapper.sh restore-default" to reset the unit then run "set-inform IPADDRESS:8080" to point it to the controller and all is well however, in this case I have had to change the port numbers in the properties file of the controller due to a port conflict with our phone system software running on the same server that the ubiquiti controller software is running on.

for some reason when I change the ports of the controller the two APs in question wont connect. - even if I run the inform command with the new port number - nothing. I have tried disabling and opening the ports on windows firewall and this hasnt helped.

For troubleshooting reasons, I stopped the phone system service out of hours and ran the controller on the default port (8080) and all the APs connected.

The ports I have chosen are:
is_default=false
portal.http.port=8891
portal.https.port=8854
unifi.db.port=27128
unifi.http.port=8091
unifi.https.port=8455
unifi.shutdown.port=8092

Is there any reason why this would happen? - are the port numbers I have chosen unusable for some reason?
(All APs are running firmware 3.9.19.8123. Controller version is atag_5.6.30_10266)

Kind regards,

Rob


Accepted Solutions
New Member
Posts: 2
Registered: ‎11-21-2017
Solutions: 1

Re: Unable to connect to adopt AP v2s after port change on controller.

Solved!

Turns out I had another copy of the UniFi controller running on a different server and the two APs were talking to that! - Dohh! Icon Redface

The two APs were connecting to this  as it was running on port 8080. They were ignoring the set-inform IPADDRESScontroller:8091 command (presumably because they had already received a response from a controller on the default port)

As soon as this second controller was stopped the inform command worked. It still doesn't explain why all the other APs could be adopted using port 8091 but these two couldn't! Confused

Nevermind - I thought I would post my solution for reference.


Thanks for your help!
Rob

View solution in original post


All Replies
Highlighted
SuperUser
Posts: 19,862
Registered: ‎09-17-2013
Kudos: 4998
Solutions: 1409

Re: Unable to connect to adopt AP v2s after port change on controller.

check that you don't have any whitespace at the end of the lines in question.  That always caused trouble in the past.

 

If it's only two APs (out of multiple), make sure that there's nothing funny going on for them (e.g. on a different base VLAN, remote, etc) that you forgot to take into account.

New Member
Posts: 2
Registered: ‎11-21-2017
Solutions: 1

Re: Unable to connect to adopt AP v2s after port change on controller.

Solved!

Turns out I had another copy of the UniFi controller running on a different server and the two APs were talking to that! - Dohh! Icon Redface

The two APs were connecting to this  as it was running on port 8080. They were ignoring the set-inform IPADDRESScontroller:8091 command (presumably because they had already received a response from a controller on the default port)

As soon as this second controller was stopped the inform command worked. It still doesn't explain why all the other APs could be adopted using port 8091 but these two couldn't! Confused

Nevermind - I thought I would post my solution for reference.


Thanks for your help!
Rob

Reply