Reply
New Member
Posts: 4
Registered: ‎01-19-2017

Re: AP's disconnected after upgrade to 3.9.19

I just started a live chat from here: https://help.ubnt.com/hc/en-us/requests/new

 

I think the issue is beyond DNS, I use the IP of my controller when I set-inform and still couldn't get it working.

 

New Member
Posts: 20
Registered: ‎06-01-2014
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19


wrote:

I just started a live chat from here: https://help.ubnt.com/hc/en-us/requests/new

 

I think the issue is beyond DNS, I use the IP of my controller when I set-inform and still couldn't get it working.

 


Interesting - it worked for me with a manual set-inform.

 

Of course, I don't want to have to do that across all my APs - plus, that makes it harder to change controller IP - but perhaps there are two issues here.

New Member
Posts: 11
Registered: ‎10-25-2016

Re: AP's disconnected after upgrade to 3.9.19

Has anyone gotten an actual fix from support? Changing from FQDN to IP isn't really a fix. We've got 30+ sites with multiple AP's. If I ssh into the unit and run info sometimes I will get status :Unable to resolve (http://unifi:8080/inform), and sometimes get status :Unknown[11] (https://unifi.ourdomain.com:8080/inform) < This is the domain that it's supposed to be. I'm not sure why it's flapping. 

 

Currently I've tried a couple different things with on our local site since I can get to the AP's without having to drive. I can verifiy they are still working, at least SSID's without Guest portal (I would assume they won't work). I can't even get a downgrade to work, the firmware doesn't downgrade for some reason, anyone got that part working?

 

Capture.PNG

New Member
Posts: 20
Registered: ‎06-01-2014
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19


wrote:

 

Currently I've tried a couple different things with on our local site since I can get to the AP's without having to drive. I can verifiy they are still working, at least SSID's without Guest portal (I would assume they won't work). I can't even get a downgrade to work, the firmware doesn't downgrade for some reason, anyone got that part working?

 

I have had success upgrading/downgrading via ssh.

 

I place the firmware files on a handy web server I have locally. Here is the exact session log from my last downgrade an hour or so ago (well, exact apart from I have redacted the IP addresses!)

 

[user@yyyy unifi]$ ssh x.x.x.x -l ubnt
ubnt@x.x.x.x's password:
 
 
BusyBox v1.19.4 (2018-01-25 18:15:54 MST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
 
 
  ___ ___      .__________.__
|   |   |____ |__\_  ____/__|
|   |   /    \|  ||  __) |  |   (c) 2010-2018
|   |  |   |  \  ||  \   |  |   Ubiquiti Networks, Inc.
|______|___|  /__||__/   |__|
            |_/                  http://www.ubnt.com
 
      Welcome to UniFi UAP-AC-Pro-Gen2!
 
BZ.v3.9.22# info
 
Model:       UAP-AC-Pro-Gen2
Version:     3.9.22.8208
MAC Address: 78:8a:20:xx:xx:xx
IP Address:  x.x.x.x
Hostname:    UBNT
Uptime:      81 seconds
 
Status:      Unable to resolve (http://unifi:8080/inform)
BZ.v3.9.22# upgrade http://y.y.y.y/unifi/BZ.qca956x.v3.9.15.8011.171208.1718.bin
Downloading firmware from 'http://y.y.y.y/unifi/BZ.qca956x.v3.9.15.8011.171208.1718.bin'.
 
notification is sent in managed or upgrade state only. (factory default is excluded)
notification is sent in managed or upgrade state only. (factory default is excluded)
Waiting firmware upgrade ..
Connection to x.x.x.x closed by remote host.
Connection to x.x.x.x closed.

 

New Member
Posts: 4
Registered: ‎01-19-2017

Re: AP's disconnected after upgrade to 3.9.19

Below is the process I got to work for all of my APs.

 

  1. Forget the AP from the controller
  2. Reset the AP using syswrapper.sh restore-default
  3. Do set-inform http://ip-of-controller:8080/inform (this won't work but it seemed to get the AP out of a busy state to allow fw downgrade, before doing this it wouldn't allow me to downgrade firmware and just gave me Device Busy: inform in progress.
    Please try again.)
  4. Downgrade fw using upgrade http://dl.ubnt.com/unifi/firmware/U7PG2/3.9.15.8011/BZ.qca956x.v3.9.15.8011.171208.1718.bin .  This is for an AC Lite, your firmware link may be different, this comes from https://www.ubnt.com/download/unifi.
  5. Once upgrade is done, SSH again and do set-inform https://ip-of-controller:8080/inform

 

New Member
Posts: 20
Registered: ‎06-01-2014
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19


wrote:

I just started a live chat from here: https://help.ubnt.com/hc/en-us/requests/new 


FYI, I have logged a support case, too - ID is 1089691.

New Member
Posts: 11
Registered: ‎10-25-2016

Re: AP's disconnected after upgrade to 3.9.19

I found my issue with downgrading.....Selected the wrong model Man Sad But still don't have a fix for 3.9.19
New Member
Posts: 16
Registered: ‎09-14-2015
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19

We are having the same issue (unknown error) and downgrading the firmware does not fix this bug. The best workaround is to adopt your new AP's through the App -> L3 Adoption.

New Member
Posts: 20
Registered: ‎06-01-2014
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19


wrote:

We are having the same issue (unknown error) and downgrading the firmware does not fix this bug. The best workaround is to adopt your new AP's through the App -> L3 Adoption.


Where is the L3 Adoption option? Is this in the mobile app, or on the UniFi controller itself (I'm on v5.6.29)?

 

The problem I have is that many of these sites are remote, and I don't really want to have to drive to each one just to work round a firmware upgrade. So for now I am sticking to 3.9.15.

 

(I do have some sites where I set the controller IP via a DHCP option - this does work with 3.9.19 and above. It just seems to be DNS resolution that is broken)

New Member
Posts: 16
Registered: ‎09-14-2015
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19

L3 Adoption is a great feature of the mobile app - you just have to connect your smartphone to the same subnet (you need to adopt at least one AP first). You can enter into the site where you want to add your new AP's and go to L3 Adoption where you will find all the AP's waiting to be adopted.. It works great!
New Member
Posts: 4
Registered: ‎10-17-2016

Re: AP's disconnected after upgrade to 3.9.19

[ Edited ]

Hi,

I have the same issue. For 3 weeks I haven't upgraded any of the APs across different sites but finally I had to do it as I didn't want to stays on the old. I tried many ways from factory reset to rebooting and checking DNS in different ways.

 

The workaround I came across for time being till Ubiquiti fix the issue is as follows:

 

I have updated Controller Hostename/IP to the fully qualified domain and change my DNS to the same.

After confirming this and made sure that the AP is connected with new details I tried and upgraded to the 3.9.19

Now all the APs connected as they should.

Of course it is not ideal as then I need to perform first adoption manually as the default AP adoption link is http://unifi:8080/inform.

 

This came with another issue not for the current APs When I tried to add a new AP yesterday. I manually adopted for the first time. Then when the device went for provisioning, it stuck in provisioning and after about a minutes it went to disconnect status. When I logged in using SSH I saw that status is Waiting for IP (http://unifi.domain.com:8080/inform) To overcome this finally I had to use the IP address to get this new AP connected.

 

I hope soon Ubiquiti find the solution and resolve it as it is so annoying specially in large number of APs to do so many work around.

 

I hope this help and maybe someone else can carry on and find better way to overcome this issue.

 

Thanks

New Member
Posts: 5
Registered: ‎02-01-2016

Re: AP's disconnected after upgrade to 3.9.19

I'm having similiar issues.  I am downgrading my APs to 3.9.15.8011.  I have 80 APs which is extremely tedious.

New Member
Posts: 20
Registered: ‎06-01-2014
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19

FWIW - this issue is still present in 3.9.24.8264 (for me, at least). I have also posted in the 3.9.24 announcement thread, so hopefully it will be investigated by Ubiquiti.

Ubiquiti Employee
Posts: 3,611
Registered: ‎01-11-2016
Kudos: 1086
Solutions: 28

Re: AP's disconnected after upgrade to 3.9.19

We are looking into it. Thanks for the report.
Want to try out new features or fixes before they're released as Stable? Sign up for Beta here: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Signup-for-Beta-Access
Having connectivity issues? See: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
Ubiquiti Employee
Posts: 24
Registered: ‎06-27-2016
Kudos: 10
Highlighted
Ubiquiti Employee
Posts: 3,611
Registered: ‎01-11-2016
Kudos: 1086
Solutions: 28

Re: AP's disconnected after upgrade to 3.9.19

cc @jmhunter1
Want to try out new features or fixes before they're released as Stable? Sign up for Beta here: https://help.ubnt.com/hc/en-us/articles/204908664-How-To-Signup-for-Beta-Access
Having connectivity issues? See: https://help.ubnt.com/hc/en-us/articles/221029967-UniFi-Debugging-Intermittent-Connectivity-Issues-on-your-UAP
New Member
Posts: 20
Registered: ‎06-01-2014
Kudos: 3

Re: AP's disconnected after upgrade to 3.9.19

Thanks @UBNT-jeff.

 

(I presume you've received my PMs and just not replied via that channel - otherwise I think I'm not using the PM facility correctly!)

 

Have just tried this firmware, here are the results. (In summary - it made no difference to the problem I am experiencing, as far as I could tell)

 

- From 3.9.15, after 'upgrade', and without 'set-default':

 

 

myap-BZ.ca-curl-hosts-resolve# info

Model:       UAP-AC-Pro-Gen2
Version:     ca-curl-hosts-resolve.8515
MAC Address: 78:8a:20:xx:xx:xx
IP Address:  x.x.x.x
Hostname:    myap
Uptime:      201 seconds

Status:      Unknown[11] (http://unifi:8080/inform)

 

 

and extracts from /var/log/messages:

 

Mar 12 23:32:14 myap daemon.info init: starting pid 1125, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Mar 12 23:32:14 myap user.info syslog: ubnt_protocol.ubnt_usr1_handler(): Get DHCP IP
Mar 12 23:32:14 myap user.info syslog: ubnt_protocol.ubnt_usr1_handler(): my_ip is x.x.x.x
Mar 12 23:32:15 myap daemon.info init: process '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p br0:22' (pid 1026) exited. S
Mar 12 23:32:15 myap daemon.info init: starting pid 1194, tty '/dev/null': '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p 
Mar 12 23:32:15 myap authpriv.info dropbear[1194]: Not backgrounding
Mar 12 23:32:19 myap user.err syslog: ace_reporter.reporter_fail(): Unable to resolve (http://unifi:8080/inform)
Mar 12 23:32:19 myap user.err syslog: ace_reporter.reporter_fail(): initial contact failed #1, url=http://unifi:8080/inform, rc=1
Mar 12 23:32:35 myap user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://unifi:8080/inform)
Mar 12 23:32:35 myap user.err syslog: ace_reporter.reporter_fail(): initial contact failed #2, url=http://unifi:8080/inform, rc=11
Mar 12 23:32:50 myap user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://unifi:8080/inform)
Mar 12 23:32:50 myap user.err syslog: ace_reporter.reporter_fail(): initial contact failed #3, url=http://unifi:8080/inform, rc=11
Mar 12 23:32:50 myap user.err syslog: ace_reporter.reporter_fail(): [STATE] entering SELFRUN!!!!

 

 

Then, after set-default (still on new firmware) we get:

 

 

Hostname:    UBNT
Uptime:      80 seconds

Status:      Unable to resolve (http://unifi:8080/inform)

and in /var/log/messages:

 

 

Mar 13 00:31:55 UBNT user.notice syswrapper: ipready.br0 = x.x.x.x
Mar 13 00:31:55 UBNT daemon.info init: process '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org' (pid 1063) exited. Scheduling for restart.
Mar 13 00:31:55 UBNT daemon.info init: starting pid 1211, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Mar 13 21:56:36 UBNT user.notice syswrapper: hostapd update: conf=/etc/aaa1.cfg iterface=ath0 nas_ip=x.x.x.x res=OK
Mar 13 21:56:36 UBNT daemon.info init: process '/usr/bin/wevent' (pid 1057) exited. Scheduling for restart.
Mar 13 21:56:36 UBNT daemon.info init: process '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p 22' (pid 1064) exited. Sched
Mar 13 21:56:36 UBNT daemon.info init: starting pid 1286, tty '/dev/null': '/usr/bin/wevent'
Mar 13 21:56:36 UBNT daemon.info init: starting pid 1287, tty '/dev/null': '/bin/dropbear -F -d /var/run/dropbear_dss_host_key -r /var/run/dropbear_rsa_host_key -p 
Mar 13 21:56:36 UBNT authpriv.info dropbear[1287]: Not backgrounding
Mar 13 21:56:37 UBNT user.info syslog: ubnt_protocol.ubnt_protocol_init(): UBNT_DEVICE[78:8a:20:xx:xx:xx]
Mar 13 21:56:37 UBNT user.err syslog: ubnt_protocol.ubnt_protocol_init(): no unifi key
Mar 13 21:56:37 UBNT user.err syslog: ubnt_protocol.ubnt_protocol_init(): ubnt socket not running
Mar 13 21:56:40 UBNT kern.debug kernel: [   24.440000] br0: no IPv6 routers present
Mar 13 21:56:41 UBNT kern.debug kernel: [   25.600000] eth0: no IPv6 routers present
Mar 13 21:56:41 UBNT user.err syslog: ace_reporter.reporter_fail(): Unable to resolve (http://unifi:8080/inform)
Mar 13 21:56:41 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #1, url=http://unifi:8080/inform, rc=1
Mar 13 21:56:42 UBNT kern.debug kernel: [   26.760000] ath0: no IPv6 routers present
Mar 13 21:57:02 UBNT user.err syslog: ace_reporter.reporter_fail(): Unable to resolve (http://unifi:8080/inform)
Mar 13 21:57:02 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #2, url=http://unifi:8080/inform, rc=1
Mar 13 21:57:23 UBNT user.err syslog: ace_reporter.reporter_fail(): Unable to resolve (http://unifi:8080/inform)
Mar 13 21:57:23 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #3, url=http://unifi:8080/inform, rc=1
Mar 13 21:57:23 UBNT user.info syslog: ace_reporter.reporter_next_inform_method(): next inform family: 10
Mar 13 21:57:32 UBNT authpriv.info dropbear[1452]: Child connection from y.y.y.y:50178
Mar 13 21:57:34 UBNT authpriv.notice dropbear[1452]: Password auth succeeded for 'ubnt' from y.y.y.y:50178
Mar 13 21:57:44 UBNT user.err syslog: ace_reporter.reporter_fail(): Unable to resolve (http://unifi:8080/inform)
Mar 13 21:57:44 UBNT user.err syslog: ace_reporter.reporter_fail(): initial contact failed #4, url=http://unifi:8080/inform, rc=1
Mar 13 21:57:44 UBNT user.info syslog: ace_reporter.reporter_next_inform_method(): authkey=xxxxxxxxxxxxxxxxxxxxxx

 

 

Finally, after 'upgrade http://y.y.y.y/BZ.qca956x.v3.9.15.8011.171208.1718.bin', we get back to a working state:

 

BZ.v3.9.15# info

Model:       UAP-AC-Pro-Gen2
Version:     3.9.15.8011
MAC Address: 78:8a:20:xx:xx:xx
IP Address:  x.x.x.x
Hostname:    UBNT
Uptime:      124 seconds

Status:      Not Adopted (http://unifi:8080/inform)

Still happy to help via PM..!

Ubiquiti Employee
Posts: 24
Registered: ‎06-27-2016
Kudos: 10

Re: AP's disconnected after upgrade to 3.9.19

[ Edited ]

@jmhunter1

A quick question - is there an entry in your /etc/hosts on the AP that looks like

127.0.0.1       localhost.localdomain   localhost 
127.0.1.1       UBNT 
172.24.0.12     unifi

(to pick an example from one I use where 172.24.0.12 is the IP for the controller here)
specifically the entry with "unifi"
This would happen if you're using a USG DNS server, or option 42 on DNS server.  (I use the second locally - option 42 with ISC dhcp server)

The above should have fixed if this is the case, but we will investigate further.
Also note : I may have misunderstood something in the set up.  Will be checking in more detail too.

Member
Posts: 141
Registered: ‎06-16-2015
Kudos: 6
Solutions: 1

Re: AP's disconnected after upgrade to 3.9.19

"Are they actually reading the posts on this thread?"

Apparently not because for the third time this week tech-support has taken me in a circular hour long session about the issue.
Ubiquiti Employee
Posts: 24
Registered: ‎06-27-2016
Kudos: 10

Re: AP's disconnected after upgrade to 3.9.19

Looking into what happened with searchdomain support.   (to add to the above)

 

The build linked above should fix installations that use option 42 with dhcp + dns.    Still examining searchdomain issues.

Reply