06-24-2014 05:21 AM - edited 06-24-2014 05:35 AM
Controller Version 220.127.116.1101
Windows Server 2008 SP2
I need help with this. I am in the process of deploying 13 new Unifi APs. I got 8 installed without any trouble, I plug a 9th one in and no matter what I try I can't get the controller to find it (have tried different APs as well). I've run the Unifi Discover app and it detects it fine. I've tried setting the inform url (which actually appears to be correct even on a new AP, which makes me think it's communicating on some level with the controller). I was even able to upgrade the firmware which grabs the .bin from the controller, so it is able to communicate with the controller, it's just not coming up for adoption. It feels like a port issue, but I even turned off the firewall on the controller server. I'm not using the default ports because I have other services that are using them. Here is the error I get.
ace_reporter.reporter_connected(): reporter connected to http://10.111.106.19:13080/inform ace_reporter.reporter_send(): request sent, waiting for response ace_reporter.reporter_read(): Failed!! HTTP Status code: 400 ace_reporter.reporter_fail(): Server Reject (http://10.111.106.19:13080/inform) ace_reporter.reporter_fail(): initial contact failed #1626, url=http://10.111.106.19:13080/inform, rc=5 ace_reporter.reporter_next_inform_url(): next inform url=http://unifi:8080/inform
Here is a thread with a similar problem, seems he only had 8 APs before he had trouble too, I don't know if that's coincedence or not. Is there some sort of limit to 8 APs?
08-03-2015 02:32 AM
I spent 90 minutes trying to adopt an AP into a working environment getting the dreaded 'server reject' message and in the end I worked out that I'd missed the /inform off the end of the URL...
01-08-2019 07:23 AM
Bit of an old thread, but just had this problem recently.
We use a FQDN to adopt AP's ie inform.mydomain.com
SSH into the AP
Checked the AP could access the internet - check
Checked we could ping the FQDN - check
Set inform ... nothing on the controller
Says that the inform response is : server reject
I noticed the AP was running a version of firmware a few points behind where the controller was.
Did an upgrade on the AP:
SSH into the AP again ... send the set-inform again, worked first time.
May help someone in future! Good luck!
This Unifi gear always reminds me of my children, how can they all react so differently when they all come from the same place!
01-31-2019 11:01 AM
I had similar issues getting an AP to adopt (AC Mesh), with the server rejecting it for whatever reason.
The fix for me was to factory default the AP (this would have been the 2nd factory default performed), and adopt it again. Then it worked and adpoted fine.