prior to updating i wasn't having these issues.. but after 48 hours it kinda stabilized..

the amount of notifications has dropped as well.

dont know where it came from, but it seems better now.

1 hour ago, furian said:

prior to updating i wasn't having these issues.. but after 48 hours it kinda stabilized..

the amount of notifications has dropped as well.

dont know where it came from, but it seems better now.

It probably just didnt alert you to a problem before. Nothing more.

On 10/4/2025 at 5:00 PM, MrTroll said:

I'm fairly certain all it takes is port forwarding. A mate of mine managed this with his and his mother's like you. I can ask him if you want homie.

I ended up using the port forward route to be honest. My mom's router is a home setup so only way was forwarding. I use pfsense so I had to tweak the rules a bit with the timeouts as it kept dropping the devices connecting to the controller from time to time.

Hi,

I just updated to 11notes/unifi:9.5.21-unraid and now I cannot start the docker? If I go to the logs I just get "Press Any Key To Close This Window"

Can anyone please nudge me into where I can start working this out? I have reboot the whole server as well.

Thank you!

2 minutes ago, mbc0 said:

Hi,

I just updated to 11notes/unifi:9.5.21-unraid and now I cannot start the docker? If I go to the logs I just get "Press Any Key To Close This Window"

Can anyone please nudge me into where I can start working this out? I have reboot the whole server as well.

Thank you!

Check there are no port conflicts by stopping all other dockers and then starting only this one.

oh! how weird! I stopped all the dockers as you advised, started unifi reborn and it worked! I then started all the other dockers and they are working too! I cannot see anything conflicting but will take a deeper look! Thank you so much for your quick response! I appreciate it! :-)

30 minutes ago, mbc0 said:

oh! how weird! I stopped all the dockers as you advised, started unifi reborn and it worked! I then started all the other dockers and they are working too! I cannot see anything conflicting but will take a deeper look! Thank you so much for your quick response! I appreciate it! :-)

you have a port conflict and the issue will keep coming back until you one day resolve it properly.

12 minutes ago, PeteAsking said:

you have a port conflict and the issue will keep coming back until you one day resolve it properly.

I am not sure where to go with this as my ports are all individual, I have not added any dockers to this server in a year or more (it is just a router/cctv server)

Very strange!

On 10/29/2025 at 4:11 PM, mbc0 said:

I am not sure where to go with this as my ports are all individual, I have not added any dockers to this server in a year or more (it is just a router/cctv server)

Very strange!

Set the docker to use another IP.

For me, I select custom br0 and place another IP. At least one thats not in use on your network.

I am still running the "old" docker controller on version 7.2.95 with a USG3 as my gateway and I want to go to reborn and new hardware, but I have a bunch of things to deal with. I posted about a year ago here but I haven't done anything in the last year. (Of course, depending on my hardware I may not need to self-host controller if I went to a cloud gateway).

Has anything changed in the last year? There seem to be some new hardware models from Unifi, especially the "fiber" units like the UXG-Fiber and UCG-Fiber.

Anything else happen in the last year to change my plan from last year, which was to install the reborn docker and try to restore from 7.2.95 to 7.5.187, which I think is the earliest version that works with the reborn docker? One other option, although I don't know if this is possible, is to upgrade the old Linuxserver.io-Unifi-Controller to 7.5.187, or the closest version possible, before switching to the new docker. But I don't know if the repositories are available to do that.

30 minutes ago, wayner said:

and I want to go to reborn and new hardware

I first went from a USG3 to a UXG Lite a a little over two years ago. That UniFi gateway does not have a built-in network controller so I used the Unifi controller reborn and went through several seamless updates as the controller version changed. A little over a year ago, I upgraded to the Cloud Gateway Ultra which has a built-in network controller which must be used. I have them in both my homes and they work great. Of course there are other models for 2.5G and even 10G networking, but since my Internet speed is "only" 500/500 Mbps, I don't need anything more than the Cloud Gateway Ultra and its gigabit ports.

Here is the process I used to go from the UXG Lite/docker-based controller to the Cloud Gateway Ultra and the built-in controller:

I had a self-hosted controller running in a docker container with a UXG-Lite gateway. I migrated to the Cloud Gateway Ultra (CGU) using a backup (settings only) of the self-hosted controller.

I did the following (not that you have to do it this way):

1 - Changed the Inform host override IP address in the self-hosted controller to 192.168.1.1 (the IP address of the CGU) instead of the IP address of the host running the docker-based controller instance

2 - Made a backup (settings only) of the UniFi network configuration in the docker-based controller

3 - Stopped the docker-based controller instance and set it to not auto start on server reboot

3 - Connected the CGU to my laptop via an Ethernet cable in the CGU WAN port

4 - Did an offline setup of the CGU

5 - Disconnected the UXG-Lite and plugged in the CGU in its place connecting the Internet to WAN port and main switch to adjacent port

6 - Updated firmware on the CGU to latest

7 - Imported the backup from the docker-based controller instance

8 - Waited for all devices (3 switches and 5 APs) to adopt which they did fairly quickly

That was it. I am now running the CGU with its built-in network controller instead of the docker-based controller instance with the UXG-Lite. I can access the CGU network controller in a web browser and everything is configured and functioning as it was when running the docker-based controller.

The UXG-Lite is now a backup. Both the UXG Lite and the Cloud Gateway Ultra run circles around the USG.

Edited December 4, 2025Dec 4 by Hoopster

Thanks - that's helpful. I have cable internet that is supposed to be 500/30 but I get speed tests of 900/32. And I think that the USG may even be limiting my WAN speed. I would like WAN speeds faster than 1G to futureproof.

Any pros/cons vs having Unifi host the controller in the cloud vs self-hosting?

And do you know what controller version you were running in the docker when you switched to the cloud docker? Was there a gap or were you on pretty much the same version?

And with step 4 - what does doing an offline setup entail? It seems like you plugged the CGU into your network before actually restoring the backup.

33 minutes ago, wayner said:

Any pros/cons vs having Unifi host the controller in the cloud vs self-hosting?

For me, having the Cloud Gateway Ultra in two different locations, I am easily able to switch between locations in the cloud-based controller. In addition, any device on site A is accessible to devices on site B and vice versa via the SD WAN capability (WireGuard under the covers). This makes it extremely easy to backup my main Unraid server at site A to a backup server on site B via my rsync backup script.

If you have just one UniFi system you are managing through the controller, you might not see a lot of difference between the Docker-based controller and the built-in/cloud-based controller in the UnifFi gateway device.

38 minutes ago, wayner said:

And do you know what controller version you were running in the docker when you switched to the cloud docker? Was there a gap or were you on pretty much the same version?

They were close to the same version (although I don't remember which version that was as it was over a year ago). The docker-based controller reborn was probably a version or two behind.

40 minutes ago, wayner said:

And with step 4 - what does doing an offline setup entail?

It's fairly straightforward, not too much to be done. I can't recall exactly what it entailed, but you are guided through what you can do in an offline setup.

41 minutes ago, wayner said:

It seems like you plugged the CGU into your network before actually restoring the backup.

Yes, after the offline setup, I replaced the UXG Lite with the Cloud Gateway Ultra and restored the backup I had taken from the Docker-based controller.

Edited December 4, 2025Dec 4 by Hoopster

On 10/15/2025 at 7:59 PM, Xoron said:

Shout out to @PeteAsking for this docker. I was running a quite old version of Unifi Controller docker version 7.2.92. The recommended upgrade path was to install the same version of this docker, but none that old exists. Figured, why not, lets go for the newest stable version of unifi-controller-reborn, see if that will fly.

I backed up my config on my v7.2.92 controller and powered it off. Then I deployed version 9.4.19 of unifi-controller-reborn and the backup restored fine. Logged in with my original credentials. All APs were present, historical logs, everything. Smoothest upgrade I've ever done.

Hi @Xoron - I am in the same boat as you. I am running the old unifi controller docker version 7.2.95. Is everything still looking good with your system? I might be a little more cautious than you and upgrade to an interim version - the lowest version supported by unifi-reborn, which is 7.5.187(I think) and see how it goes before moving to the more recent versions like 9.5 or whatever.

Edited December 4, 2025Dec 4 by wayner

Is anyone moving to the new Unifi OS server? It isn't clear to me what has changed now, and how this is different from the previous way that Unifi worked. Is this something that would be useful for the prosumer market, like many of us in this thread?

Tried the new 10.0.160-Unraid and rolling-Unraid tags just now. Neither would start up with Unraid GUI showing as unhealthy. Rolled back to 9-Unraid tag and everything is working again

Edited December 10, 2025Dec 10 by fat

4 hours ago, fat said:

Tried the new 10.0.160-Unraid and rolling-Unraid tags just now. Neither would start up with Unraid GUI showing as unhealthy. Rolled back to 9-Unraid tag and everything is working again

Had the same experince.

Also noticed a bunch of a new tags for this particular release, not sure whats up with that.

Tags are not ready yet, you will be notified on this thread when they are ready for testing.

1 hour ago, PeteAsking said:

Tags are not ready yet, you will be notified on this thread when they are ready for testing.

Thanks for this, that explains it. I am happy to test once they are available

Hi @Xoron - I am in the same boat as you. I am running the old unifi controller docker version 7.2.95. Is everything still looking good with your system? I might be a little more cautious than you and upgrade to an interim version - the lowest version supported by unifi-reborn, which is 7.5.187(I think) and see how it goes before moving to the more recent versions like 9.5 or whatever.

Sorry for the late reply

Everthing is working exactly as expected. My setup is fairly basic. But you can always just export the config, shutdown the old docker, start the new one, import the config. If things go sideways, you can always revert back to the old docker.

Testing for version 10 needed (see below).

Version 10 introduces some changes that will require manual intervention for users to upgrade from a 9x release to 10x for this docker. There are 2 methods you can use to upgrade. Method 1: In place upgrade. Method 2: Backup of settings of current running docker, and redeploy of docker to a new location. Both these methods are described below.

Method 1 has the advantage of being easier and quicker, but may require restore from an archive/backup if something goes wrong. Method 2 will leave your current running docker alone but requires additional work to create a second unifi docker, and both cannot run/be started at the same time. Both methods would be supported so simply choose what works better for you (non critical systems probably method 1, systems for no downtime method 2 probably).

---

Method1:

Confirm that the DHCP server on your network is functional. This is required for readoption of unifi devices.

Edit the unifi-controller-reborn docker. The following changes are required:

Step 1: Repository. Change this tag to a appropriate tag eg:

11notes/unifi:10-unraid

(note this tag is rolling in this example so dont use this if you cannot experience any downtime ever)

Step 2: Enable advanced view

Step 3: under extra parameters modify them to be this:

--memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100

Click apply to finish and allow new image to be pulled.

Wait 10 minutes for adoption to occur after logging into the web interface via browser or phone.

---

Method 2:

Confirm that the DHCP server on your network is functional. This is required for readoption of unifi devices.

Step 1: Take backup of running container via system - backups. Choose "settings only" (you could chose a time period like 7 days but this was not tested).

Step 2: NB: STOP container in Unraid (very important) and go to apps and search for unifi reborn app. Click install.

Step 3: If you install the app without making any changes at this stage, it will deploy over your current app. You must modify these settings before installing:

a) Turn on advanced view and give the docker a slightly different name such as appending '-10' on the end:

b) Under more settings modify the volume to write data to a different place than your current unraid docker:

NOTE THIS IS CRITICAL, if you fail to do this your current docker will get modified! Note below how I have changed the path to include '-10' on the end:

Step 4:

You will now need to go to the web UI and restore the backup you created in step 1.

Click restore from backup:

Once it restores, it should stop the container. Unraid does not start it again, you will manually have to start it after 2 minutes or so. Wait till its stopped, then start it again and it will be restored. It can take 5 minutes to start up after a restore. Dont forget to set autostart on the appropriate container when done.

---

If anyone can test the above (ie take a backup) and report back if it worked or broke for you that would be great.

Kind regards

P

Edited December 25, 2025Dec 25 by PeteAsking

Updating to 10.0.160 using Method 1 above worked for me. Everything re-adopted and looks to be functioning.

I didn't test any specific features, since I mainly just use the controller for managing WiFi.

27 minutes ago, tehg said:

Updating to 10.0.160 using Method 1 above worked for me. Everything re-adopted and looks to be functioning.

I didn't test any specific features, since I mainly just use the controller for managing WiFi.

Hi @tehg

Can you try this?

Delete the 2 new volumes (log and run) you added and instead under extra parameters (use advanced view) edit it to this:

--memory=8G --tmpfs /unifi/log --tmpfs /unifi/run

30 minutes ago, PeteAsking said:

Delete the 2 new volumes (log and run) you added and instead under extra parameters (use advanced view) edit it to this:

Made those changes and restarted the container. No issues so far. I see devices adopting again as they check in.

To update to unifi 10x please follow this thread

When the community apps updates from github in a few hours I will edit that post with Method 2 instructions. Both should work fine. If anyone has any issues let me know and I can assist in getting it working.

• P

Edited December 16, 2025Dec 16 by PeteAsking