Unifi annoying me! - Pending approval, adopting then disconnect issues

[caffrey]

I'm getting really fed up of these APs seriously wasting my time and I've got 12 to fit this half term!

see this thread - anyone got any suggestions ?

 

Pending approval, adopting, provision then disconnect - Ubiquiti Networks Community

*edit* managed to get it working by jumping through hoops...

Edited October 25, 2013 by caffrey

[Steven_Cleaver]

Hi

 

Try updating the software I was getting exactly this same issue and updating the management software seemed to resolve this.

[caffrey]

The main management machine is on the latest stable, I updated the thread on how I have to do it, seems weird to me - wonder what causes it.

[bodminman]

God knows.

 

I have only provisioned x33 APs and to be hinest I haven't had this issue at all.

 

We've always had the controller s/w installed on an old Svr3003 box and apart from it being a bit slow, it has done it's job every time.

[caffrey]

Well that's the annoying thing, now and again I'll get one that will just work, other annoying thing is I just cannot pinpoint what it causing it.

I thought it was the network, although our network isn't really that complicated, thought it was maybe a smoothwall thing, but none of that explains why after upgrading on a temporary controller using the APs IP range plugged into a laptop using a PoE injector then forgetting them, they adopt just fine without any issues on the main controller ??? Maybe it's the firmware they are shipped with (2.4.4) but then why do they adopt fine on the temporary controller that's running 2.4.6??, nothing makes sense!

 

I'm not even sure where any logs exist to actually see whats happening.

[Graeme-77]

Hi there I think I had this issue, it was on a server 2008 box, so opened up a load of ports see below, and that seemed to sort it:

[h=4]How can I run UniFi Controller on different ports[/h]

1. By default, UniFi controller runs on these ports
   
   • unifi.shutdown.port=8081 (for management purpose)
     
   • unifi.http.port=8080 (device inform)
     
   • unifi.https.port=8443 (controller UI / API)
     
   • portal.http.port=8880 (portal redirect port for HTTP)
     
   • portal.https.port=8843 (portal redirect port for HTTPs)
     
   • unifi.db.port=27117 (local-bound port for DB server)
     

 

[caffrey]

I was thinking that too, but ufw is disabled on the Linux box

[synaesthesia]

Hi there I think I had this issue, it was on a server 2008 box, so opened up a load of ports see below, and that seemed to sort it:

[h=4]How can I run UniFi Controller on different ports[/h]

1. By default, UniFi controller runs on these ports
   
   • unifi.shutdown.port=8081 (for management purpose)
     
   • unifi.http.port=8080 (device inform)
     
   • unifi.https.port=8443 (controller UI / API)
     
   • portal.http.port=8880 (portal redirect port for HTTP)
     
   • portal.https.port=8843 (portal redirect port for HTTPs)
     
   • unifi.db.port=27117 (local-bound port for DB server)
     

 

 

Aye, to expand on that via the Unifi support site quite clearly, had to do this myself for a smaller deployment (12aps). Only needed to shift it off 8080.

UniFi FAQ - Ubiquiti Wiki

[caffrey]

Think I've solved it, Disabling "Uplink Connectivity Monitor" Seems to have done the trick, though why this on by default I've no idea, I'm sure I was told to do this before but must've forgot...

Fitted two AP's today with no issues whatsoever , unless its just coinkidink....