Problems with update AP-LR from 4.0.10.9653 to 4.0.14.9736 / 4.0.15.9872 AP Disconnected [ Edited ]

[pipo10]

Hi i have two AP-LR 's and one AP-AC-PRO

In the UNIFi controller software i got the message that there was an upgrade available for all three devices. (Automatic upgrades ON)

Upgrading the AP-AC-PRO from 4.0.10 to 4.0.14  went smooth

On both AP-LR 's  it doesn't work, after hitting "upgrade" he starts but at the end he got in "disconected" state and the light was red on the AP-LR. Waited 15 minutes but still red and disconnected. I switch power for the AP-LR, Off and than On and he got  "connected" again but with the old firmware level 4.0.10

Then i tried to update it manually with the BIN file, this has the same result after the upgrade the device went Disconnected, after reboot it came online with the old firmware.

Has somebody a clue for me what i can do to solve this.

Or is the firmware not compatible/tested with the AP-LR

regards

Jan

[AmazedMender16]

Hello @pipo10,

Welcome to the community!

Are you running into any errors when updating via the CLI?

What commands did you use?

Could you give the following commands a shot?

curl https://dl.ubnt.com/unifi/firmware/U7PG2/4.0.14.9736/BZ.qca956x.v4.0.14.9736.181224.1723.bin -o /tmp/fwupdate.bin

syswrapper.sh upgrade2 &

Only use these commands for the following UAPs: UAP-AC-Lite/LR/Pro/EDU/M/M-PRO/IW/IW-Pro

Regards,

Glenn R.

[pipo10]

Hi @AmazedMender16,

The string you mentioned in your post is, i guess, for the AP-LR-v2. 

When you checked the firmware via on the unifi site:

https://www.ubnt.com/download/unifi/unifi-ap/uaplr

You have two choices for firmware:

UAP-LR the string name starts with BZ.ar7240.v4....    (with ar)

and UAP-LR-v2 it starts with BZ.qca9342.v4......          (with qca)

Until yesterday i had always used the"Automatic Upgrades" function. So i only have to click "upgrade" when it is displayed.

The AP-AC-PRO went well with the Automatic upgrade function, but the two AP-LR 's starts the update you see the different update stages passing, but in the end when he has to restart with the new software you see the Disconected state appear and the AP light is red.

So i figured out how to update manual. I used the program "HTTP file Server" HFS.exe and made the string:

http://192.168.1.207/BZ.ar7240.v4.0.14.9736.181224.1724.bin

This string i enter in the UNIFI portal.

Klik on device > config > manage device > custom upgrade 

There i copied the string and hit the "custom upgrade" button.

A simular proces is visual, upgrade starts you see the different stages of the update, but he wasn't able to reboot with the new firmware and went again in "disconnected" during both upgrade processes (manual/automatic) i didn't see any errror message.

Switch the AP OFF and ON, he starts with the old firmware.

Your command string is for under unix i guess, but i'm not familiar with that.

When thats the only way to debug, i have to find out how that proces works...

regards Jan

[AmazedMender16]

Hello @pipo10,

Sorry that command was for the G2 UAPs..

SSH into the UAP and run the following command ( UAP, UAP-LR, UAP-OD, UAP-OD5 )

curl https://dl.ubnt.com/unifi/firmware/BZ2/4.0.14.9736/BZ.ar7240.v4.0.14.9736.181224.1724.bin -o /tmp/fwupdate.bin

syswrapper.sh upgrade2 &

Regards,

Glenn R.

[warren_alerts]

I've got the same issue with my AC-AP-LR. Whenever I update it trys to do the update cycle then disconnects then comes back to the previous release.

My US-8-60W updated just fine.

Don't really feel like doing a manual since other that have tired it have had no joy.

I really think there is a problem with the update.

Is there a log I can display that would help determin the problem.

Why don't you have a support number that's easy to locate?

Tried to do a manual and got this.

------------------------------------------------------------------------------------------------------------------------------

AP-AC-LR-Hall-BZ.v4.0.10# curl https://dl.ubnt.com/unifi/firmware/BZ2/4.0.14.9736/BZ.ar7240.v4.0.14.9736.181224.1724.bin -o /tmp/fwupdate.bin syswrapper.sh upgrade2 &
AP-AC-LR-Hall-BZ.v4.0.10# curl: (6) Couldn't resolve host 'dl.ubnt.com'
curl: (6) Couldn't resolve host 'syswrapper.sh'
curl: (6) Couldn't resolve host 'upgrade2'

[1]+ Done(6) curl https://dl.ubnt.com/unifi/firmware/BZ2/4.0.14.9736/BZ.ar7240.v4.0.14.9736.181224.1724.bin -o /tmp/fwupdate.bin syswrapper.sh upgrade2
AP-AC-LR-Hall-BZ.v4.0.10#

------------------------------------------------------------------------------------------------------------------------------

So what's next?

[AmazedMender16]

Hello @warren_alerts,

Could you SSH into the UAP and see if you can resolve dl.ubnt.com?

I would recommend creating your own thread.

Regards,

Glenn R.

[warren_alerts]

I edited into the above post.

When I create a new thread with the same problem I get yelled at. When I add to an existing thread about the same problem I get yelled at. Normal Internet protocol is if it's the same issue you add to the thread.

Will someone please make up their mind how they want this forum to operate?

Can't ping dl.ubnt.com from the AP but it's just fine from the Ununto system running the Unifi controller software.

[AmazedMender16]

Hello @warren_alerts,

Ahh, set the UAP to a static IP with google DNS and try to upgrade again

Regards,

Glenn R.

[warren_alerts]

Actually that both was and was not the problem. I had previously changed all the UniFi devices over to static addresses so I could group them.

During that change the DNS used for all of them was the USG @ 10.0.2.1 but in this case I tranposed two octects and entered 10.2.0.1. Change that and problem solved.

Might I suggest that errors from the devices during upgrades get placed in the log so we could see them. Had I seen a DNS fail the I likely would have spotted the issue much sooner.

Thank you

John

[AmazedMender16]

Hello @warren_alerts,

I believe it does show something in the logs and event tab.

Regards,

Glenn R.

[pipo10]

Hi @AmazedMender16,

All devices in my network have static adresses

My US-8-150W and the AP-AC-PRO updated fine.

I also tried to use the original injectors for the AP-LR but same results.

Regards 

Jan

[AmazedMender16]

Hello @pipo10,

Are you able to resolve dl.ubnt.com?

Have you tried a factory reset of the UAP?

Regards,

Glenn R.

[pipo10]

Just a minute ago i saw that there was already a new update for the firmware 4.0.15.9872.  

I updated the USW-8-150W and the AP-AC-PRO whitout any problem, but again the same issue with all  AP-LR 's.

At the end of the update they went "disconnected" after restart they came up with the 4.0.10 firmware.  

Tomorrow i will reset them to factory defaults and will try again.

regards

jan

[AmazedMender16]

Hello @pipo10,

Did you SSH into the UAP and checked if you can resolve dl.ubnt.com on the UAP?

Regards,

Glenn R.

[pipo10]

Hi @AmazedMender16

I can ping dl.ubnt.com

Jan-BZ.v4.0.10# ping dl.ubnt.com
PING dl.ubnt.com (52.85.253.162): 56 data bytes
64 bytes from 52.85.253.162: seq=0 ttl=248 time=4.466 ms

In the ALERTS tab of the UNIFI controller software i found an error:

 upgrade failed: download failed (error: curl:7, http:000)

regards Jan

[AmazedMender16]

Hello @pipo10,

And what is the output of the commands above? ( upgrade via CLI )

Regards,

Glenn R.

[pipo10]

Hi @AmazedMender16

Waited over 45 minutes, AP is flashing yellow/green and nothing happends further.

Asked for info and AP is still on 4.0.10

 it looks he is already 30 minutes up but still flashing all the time yellow/green.

I reset the AP and he starts in 4.0.10 and steady green light.

No error messages or other messages.

regards Jan

[AmazedMender16]

Hello @pipo10,

Downgrade the UAP to 3.9.54 and try to upgrade straight to 4.0.14

Regards,

Glenn R.

[pipo10]

---

@AmazedMender16 wrote:

Hello @pipo10,

Downgrade the UAP to 3.9.54 and try to upgrade straight to 4.0.14

Regards,

Glenn R.

---

---

hi AmazedMender16

thats is probably a good idea, going to bed now, will do that tomorrow

Thanks for your help.

regards Jan

[AmazedMender16]

Hello @pipo10,

Goodnight, please update me tomorrow!

Regards,

Glenn R.