Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] - Unifi-Controller: Unifi. Unraid. Reborn.

Featured Replies

  • Author
16 minutes ago, Taramu said:

Did anyone face the issue that the Controller does not find firmware updates for devices?

 

I have multiple Unifi 6 APs and a USW Flex Switch which all are running with an old firmware.

 

When clicking "Check for Updates" for in Settings -> Device Firmware I get the result no updates avilable, my controller is able to reach the internet and correctly resolves a DNS entry to fw-update.ubnt.com. I don't get the issue.

I think this is working for me as I get firmware updates every now and again… can you tell us the controller version you are on, how you checked the controller could resolve dns and what firmware the devices are on and what you expect them to find?

  • Replies 994
  • Views 185.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • 8.0.28 has failed testing and will not be promoted to an unraid tag and will be skipped.

  • PeteAsking
    PeteAsking

    8.3.32-unraid tag is tested and available for home users in production.

  • Yeah not sure what is happening with Linuxserver.io or their images. I switched to binhex for everything.   As he didnt have a unifi docker I had to make one with 11notes. 11notes has docker

Posted Images

Thanks for the quick reply!

 

My controller is running firmware 9.0.114-unraid and devices didn't receive updates for many months.

The only restriction I have on my Unraid template is that only port 8080 is opened, which is used to manage my devices. All other ports were disabled in my Unraid template.

 

I installed a new USW Flex 2.5G switch today which came with FW 2.0.5, but newer FW releases are available:

https://community.ui.com/releases/UniFi-Switch-Flex-2-5G-8-2-1-5/2052fc64-571c-4e39-9354-3c3759ff8c63

 

Also I have some Unifi 6 Pro APs running on 6.6.77, but 6.6.78 is available since a long time:

https://community.ui.com/releases/UniFi-Access-Point-6-6-78/b0097366-3989-47b8-b46a-13d36aefa96b

 

On my DNS servers I see that all DNS requests by the UniFi controller are successfully answered without any issues.

From the controller itself I'm also able to resolve DNS entries and reach the internet without restrictions.

Edited by Taramu

  • Author
1 hour ago, Taramu said:

Thanks for the quick reply!

 

My controller is running firmware 9.0.114-unraid and devices didn't receive updates for many months.

The only restriction I have on my Unraid template is that only port 8080 is opened, which is used to manage my devices. All other ports were disabled in my Unraid template.

 

I installed a new USW Flex 2.5G switch today which came with FW 2.0.5, but newer FW releases are available:

https://community.ui.com/releases/UniFi-Switch-Flex-2-5G-8-2-1-5/2052fc64-571c-4e39-9354-3c3759ff8c63

 

Also I have some Unifi 6 Pro APs running on 6.6.77, but 6.6.78 is available since a long time:

https://community.ui.com/releases/UniFi-Access-Point-6-6-78/b0097366-3989-47b8-b46a-13d36aefa96b

 

On my DNS servers I see that all DNS requests by the UniFi controller are successfully answered without any issues.

From the controller itself I'm also able to resolve DNS entries and reach the internet without restrictions.

I believe Unifi have misnamed the flex firmware. That is only for POE models, if you have a non poe flex then 2.0.5 is latest.

 

Regards The U6 pro firmware, that link states:

This release is only for these models:

U6-LR/U6-Lite/U6+/U6-LR+

UAP-nanoHD/FlexHD/BeaconHD/IW-HD

So it would not be applicable to you.

 

I believe the firmwares you have are the latest and correct for reasons above.

Wow, thanks for checking the firmware for each model.

I was on my way to reset everything but based on your reply it doesn't seem required.

For now I will just wait for the next updates being released for my systems and wait.

 

Really appreicate your work, it's the best Unifi release for Unraid available.

 

Edit:

Also found the website with firmwares listed for each model.

Might be interesting for someone else.

https://ui.com/download/releases/firmware

Edited by Taramu

  • Author
3 hours ago, Taramu said:

Wow, thanks for checking the firmware for each model.

I was on my way to reset everything but based on your reply it doesn't seem required.

For now I will just wait for the next updates being released for my systems and wait.

 

Really appreicate your work, it's the best Unifi release for Unraid available.

 

Edit:

Also found the website with firmwares listed for each model.

Might be interesting for someone else.

https://ui.com/download/releases/firmware

I have a flex on the same firmware so will make sure it works and finds an update when applicable. Also a non poe one. 

? 2.09 and 2.1 firmware exisit:

https://ui.com/download/software/usw-flex-mini

if you ssh into the device manual you can flash via ubquity or half it wget / scp added to /tmp and then ran

I've yet to see unfi auto firmware update fail on updating a device. Unless it was edited or updated manual improperly...

https://help.ui.com/hc/en-us/articles/204910064-UniFi-Advanced-Updating-Techniques

https://support.hostifi.com/en/articles/3561556-unifi-how-to-upgrade-unifi-device-firmware-via-ssh

 

I have found that ubiquity won't release some updates to EOL hardware. Some early Unifi express won't upgrade pass factory reset v7 Unifi and take on unifi network v9 without a manual update.

 

the current unifi flex switch firmware:
image.png.29a00a0510816c2499658abf7db6fc6f.png

22 hours ago, Taramu said:

Thanks for the quick reply!

 

My controller is running firmware 9.0.114-unraid and devices didn't receive updates for many months.

The only restriction I have on my Unraid template is that only port 8080 is opened, which is used to manage my devices. All other ports were disabled in my Unraid template.

 

I installed a new USW Flex 2.5G switch today which came with FW 2.0.5, but newer FW releases are available:

https://community.ui.com/releases/UniFi-Switch-Flex-2-5G-8-2-1-5/2052fc64-571c-4e39-9354-3c3759ff8c63

 

Also I have some Unifi 6 Pro APs running on 6.6.77, but 6.6.78 is available since a long time:

https://community.ui.com/releases/UniFi-Access-Point-6-6-78/b0097366-3989-47b8-b46a-13d36aefa96b

 

On my DNS servers I see that all DNS requests by the UniFi controller are successfully answered without any issues.

From the controller itself I'm also able to resolve DNS entries and reach the internet without restrictions.

 

the latest update for a flex 2.5G was
USM25G5.esp32_2.0.5+910.240926.1606

https://community.ui.com/releases/UniFi-Switch-Ultra-Flex-Mini-2-5G-2-0-5/cc5ead08-02f9-493b-b6cc-f801fc56278c

 

which is 5 month old...

https://ui.com/download/software/usw-flex-2.5g-5

Some of these updates are not considered stable your controller may be doing stable only firmware updates...
you may want to move off official and enable beta if you want the latest bleeding edge updates:
image.thumb.png.33603e0b78902b09a48f0c7383339772.png

 

You can manual follow unifi device software and firmware release here:

https://community.ui.com/RELEASES

Edited by bmartino1
Data - Typo

Hello,

 

I migrated from the Cloudkey to the Controller in a container. On https://unifi.ui.com/ I had to add it as a new site and it shows it's online but the Launch Options show the local IP of the old controller. Even if I try adding it again, it still shows the old IP so I can't connect through the Site portal. I haven't been able to find something in the UI that lets me change the IP that the controller reports up to Site Manager and trying to ask Unifi GPT just told m how to change the subnet of all of my equipment.

Thanks

  • Author
10 hours ago, thefraybeneath said:

Hello,

 

I migrated from the Cloudkey to the Controller in a container. On https://unifi.ui.com/ I had to add it as a new site and it shows it's online but the Launch Options show the local IP of the old controller. Even if I try adding it again, it still shows the old IP so I can't connect through the Site portal. I haven't been able to find something in the UI that lets me change the IP that the controller reports up to Site Manager and trying to ask Unifi GPT just told m how to change the subnet of all of my equipment.

Thanks

Can you rephrase this question in a way that I can logically understand what you are saying?

12 hours ago, thefraybeneath said:

Hello,

 

I migrated from the Cloudkey to the Controller in a container. On https://unifi.ui.com/ I had to add it as a new site and it shows it's online but the Launch Options show the local IP of the old controller. Even if I try adding it again, it still shows the old IP so I can't connect through the Site portal. I haven't been able to find something in the UI that lets me change the IP that the controller reports up to Site Manager and trying to ask Unifi GPT just told m how to change the subnet of all of my equipment.

Thanks

This sounds like you are running the docker in bridge mode and have not set a docker static IP...


image.thumb.png.e71796f287a065abbd90022a644a7b17.png

 

it also sounds like when you set up and installed the continuer you disabled SSO which is required for the network unif container to be a site. and had teh cloud key running confliting with exisitng data... and since you manual added it and not let the container authenticate... its fu bar...

So for starters, the container is not running unfi OS like the cloud key. the docker container only run the docker network.
When setting up the container yo need to start fresh and have it sing in with your unifi account to have it properly appear on the unifi site manager page.

Then you can restore from backup the configurations... 

I'm not sure what you did in what order that fu bar this up...

 

Once your SSO setup the network control docker. Restore the NETWORK BACKUP ONLY!

image.png.313d5d141f88162e6e4baadf4ab22950.png

 

so on teh cloud key you need to make a backup outlined here:

 

you may need to restart and reinstall the docker image.


And when configuring the new docker, you need to power off the cloud key device...

12 hours ago, bmartino1 said:

This sounds like you are running the docker in bridge mode and have not set a docker static IP...


image.thumb.png.e71796f287a065abbd90022a644a7b17.png

 

it also sounds like when you set up and installed the continuer you disabled SSO which is required for the network unif container to be a site. and had teh cloud key running confliting with exisitng data... and since you manual added it and not let the container authenticate... its fu bar...

So for starters, the container is not running unfi OS like the cloud key. the docker container only run the docker network.
When setting up the container yo need to start fresh and have it sing in with your unifi account to have it properly appear on the unifi site manager page.

Then you can restore from backup the configurations... 

I'm not sure what you did in what order that fu bar this up...

 

Once your SSO setup the network control docker. Restore the NETWORK BACKUP ONLY!

image.png.313d5d141f88162e6e4baadf4ab22950.png

 

so on teh cloud key you need to make a backup outlined here:

 

you may need to restart and reinstall the docker image.


And when configuring the new docker, you need to power off the cloud key device...

 

To rephrase, in https://unifi.ui.com/ the site IP is now wrong.
Screenshot2025-03-26013341.png.732f2c15b0e30436221961e86e65ab88.png

The IP there, 192.168.1.6 is from my old Cloudkey, not 192.168.1.245 which is my Unraid server. The status of the site is connected, it sees it but has the wrong local IP. The one on the left is the one that has been there and the one on the right is from adding the site again last night. I can't find a setting to update the 192.168.1.6 address to 192.168.1.245 so that unifi.ui.com picks up the correct setting.

 

Regarding the migration, I did it about a year ago. I can't remember if this has been broken the whole time or just a long time. It was a lower priority and I'm just now getting around to it. Yes I'm running the containers in bridge mode rather than a dedicated IP. I thought at one point that was recommended for this container but I haven't double checked that. The Cloudkey was down before I brought up the container as suggested. The old "site" for the Cloudkey was still in unifi.ui.com and showing as disconnected until I deleted it recently so the container didn't fully take over the identity of the Cloudkey site, unifi.ui.com saw them as separate and knew the Cloudkey was down but could tell that the container was up. From my notes when I did the migration, here are the steps I followed and my reference.

 

Actual migration between controller steps

I did recently have to re-poke my Unifi Gateway with the correct inform address to get it adopted again. The container has recently been upgraded to 9.0.108-unraid

 

As I said, it seems, I need to update a setting somewhere in the config to have the new local IP address so that when I add the site to unifi.ui.com it picks up the unraid server/container address. Hopefully that clears things up as far as what happened and what setting I'm trying to adjust. Thanks.

  • Author

Interesting. Running in bridge mode is fine but I also dont know how to change that setting. One thing you could do is change from bridge mode to dedicated ip with macvlan or similar and set it to that .6 ip address and change the inform host ip back to .6. Thats not really answering your question how to update the UI to the new IP but it would resolve the issue. 

Edited by PeteAsking

My question is regardless of what is displayed when you connect to that, does it connect to the cloud key? or does it connect to the controller.

as I've heard of unifi not having a correct display, but that is ubiquity/unifi side, not the controller's side.
As you did a restore. I'm not surprised if the ip changed in the controller and the api key that connects to unifi is displaying wrong. 

If its connecting to the cloud key there's your answer... its not the controller...
If its the controller, then its unfi api side and you are better off starting over then trying to dig into a docker over files and configs...

I would recommend reaching out on unifi support forum and contacting them is this is not the dockers fault or issues. This is entirely on how unifi and there api function for remote access via unif account and SSO.

 

https://community.ui.com/questions/Site-Manager-issues-with-Network-Application/df680578-ba5a-479c-8d94-d2926c7d1140

https://community.ui.com/questions/Site-Manager-Issues/07d707e7-7caf-4f95-ab7d-9cd234f4acd6

https://community.ui.com/questions/Site-Manager-Connection-Issues/52485da0-e9d2-4df8-9e8f-5c5ebd06ab10

https://community.ui.com/questions/Site-Manager-Multiple-Problems/5de54320-5a8e-46d8-87ea-1e3874f26d0f
 

As that forum would be better for this kind of issue...

As I ran multiple tests with unfi hardware and controllers. This could have been broken long before your backup and restore. It is a pain getting site manger working 100% and needed if doing unfi teleport WireGuard teleport...

I would recommend clearing the site mange and delete the devices. then have each controller you want to disable sso and reconnect with sso under setting to regenerate a new ID.

Unfi site manager is fickle. They would need to be removed first and re-add to even update the site manager...

https://community.ui.com/questions/How-to-remove-UniFi-Network-Server-from-new-UniFi-Site-Manager/e2f8a171-b8e9-4e7f-a5ee-15f9c504a669

Hi all -

 

I'm installing the Unifi controller Docker fresh for the first time. Had to update the port on the WebUI (to 9443) and to Inform (9080). No matter what I do, I'm not able to get the APs discoverable within the Unifi controller. I've run set-inform http://10.10.0.3:9080/inform, but it doesn't show up in the Unifi controller for me to adopt. Not sure what to do.

My Unraid box and the APs management IP are both on the same subnet, and can ping each other. From the API, I'm able to curl the inform URL, but nothing comes back in the response.

 

What am I doing wrong?

  • Author
10 hours ago, impulse9753 said:

Hi all -

 

I'm installing the Unifi controller Docker fresh for the first time. Had to update the port on the WebUI (to 9443) and to Inform (9080). No matter what I do, I'm not able to get the APs discoverable within the Unifi controller. I've run set-inform http://10.10.0.3:9080/inform, but it doesn't show up in the Unifi controller for me to adopt. Not sure what to do.

My Unraid box and the APs management IP are both on the same subnet, and can ping each other. From the API, I'm able to curl the inform URL, but nothing comes back in the response.

 

What am I doing wrong?

I put the ip address only eg:

 

10.10.0.3

 

in the unifi mobile app:

 

 

IMG_1789.png

Edited by PeteAsking

9 hours ago, PeteAsking said:

I put the ip address only eg:

 

10.10.0.3

 

in the unifi mobile app:

 

 

IMG_1789.png

 

Thanks for responding. I tried using the Unifi Mobile app - was able to get the app connected to my Unifi OS container, and tried doing the adoption - I get "adoption failed. The device could not be adopted. Please make sure the device is online with factory default settings and your UnifI OS Console is connected to the internet, then try again"

The mobile app, through the AP's wifi signal, is able to hit the Docker container... There's no firewall between the AP and the container. Totally at a loss.

  • Author

If this was setup on a different controller before you will have to factory reset it as it states using the pin button on the back. Unifi wont adopt an already adopted device. The fact it sees it but cant adopt it means its just a config issue at this point eg: you didnt reset the device, or set something up wrong etc. 

Edited by PeteAsking

1 hour ago, PeteAsking said:

If this was setup on a different controller before you will have to factory reset it as it states using the pin button on the back. Unifi wont adopt an already adopted device. The fact it sees it but cant adopt it means its just a config issue at this point eg: you didnt reset the device, or set something up wrong etc. 

All brand new configuration.

 

At any rate, I spun up an Ubuntu VM on the Unraid and installed the Unifi controller on that. It immediately discovered the AP and adopted it, and everything seems to be working. Unfortunately have to go on a work trip, but will give the container another try when I'm back after factory resetting the AP.

On 3/31/2025 at 6:56 AM, impulse9753 said:

All brand new configuration.

 

At any rate, I spun up an Ubuntu VM on the Unraid and installed the Unifi controller on that. It immediately discovered the AP and adopted it, and everything seems to be working. Unfortunately have to go on a work trip, but will give the container another try when I'm back after factory resetting the AP.

Just closing the loop on this - the issue was that the container version I was deploying (the default one in the Unraid app store) was too old... In other words, I didn't read the forum closely enough :(

 

Used the tag to deploy the stable version, reset the APs, and they adopted no problems! Thanks for the help.

  • Author
1 hour ago, impulse9753 said:

Just closing the loop on this - the issue was that the container version I was deploying (the default one in the Unraid app store) was too old... In other words, I didn't read the forum closely enough :(

 

Used the tag to deploy the stable version, reset the APs, and they adopted no problems! Thanks for the help.

Thanks for posting the solution. 

yeah, I think its time to update the template xml to the v9 tag.

Hello you wonderful kind maintainer.

I've recently been having issues with connecting to the container using my the app or firefox.

The log files fill with whats attached in the logs.text file.

After doing some digging it seems to point to issues creating a stun connection which from my understanding works via port 3478 UDP. But the issue remains even after portforwarding this port.
Any help would be greatly appreciated.

 

 

 

logs.txt

  • Author
16 minutes ago, MrTroll said:

Hello you wonderful kind maintainer.

I've recently been having issues with connecting to the container using my the app or firefox.

The log files fill with whats attached in the logs.text file.

After doing some digging it seems to point to issues creating a stun connection which from my understanding works via port 3478 UDP. But the issue remains even after portforwarding this port.
Any help would be greatly appreciated.

 

 

 

logs.txt 1.84 kB · 1 download

I think you are in the wrong track. Can you try in a private window to ensure autocomplete history of your browser isnt messed up. 

Using Firefox private window or not it will not connect if I use Chrome it will connect but will flag the connection as experiencing performance issues. I can connect it via my phone however using the app. From memory this only kicked in around network server 8.xx. I have yet to try a full reinstall of the container but I've been trying to fix this on and off for a while.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.