52 minutes ago, wgstarks said:

Thanks. I’m guessing this would need to be done for every machine on the LAN though. I might try adding a DNS A record for the unifi docker webUI to my DNS server and add the docker to my LetsEncrypt cert. I think I could use HA Proxy then and browsers would use the LE certificate.

I know its probably more complicated but would be network wide and a permanent solution if I can figure it out.

Sure but you shouldnt be administering your network administrative controllers and firewalls from every machine in your lan. So if you have more than like 3 admin machines you probably have bigger problems to address.

On 1/12/2026 at 11:13 AM, PeteAsking said:

I believe in your web browser you click on the security seal and there is a download certificate option in there somewhere. Maybe someone can confirm. I personally dont bother but pretty sure its something like that. Then install it and then add entry to hosts file so when you browse its address you go to matches the cert.

That's correct. Download the certificate from the browser, upload the certificate to your machine's CA store then modify the hosts file to point to it

36 minutes ago, fat said:

That's correct. Download the certificate from the browser, upload the certificate to your machine's CA store then modify the hosts file to point to it

Thanks but as far as I can tell that is windows specific and I’m not entirely convinced it’ll work with expired certs.

2 hours ago, wgstarks said:

Thanks but as far as I can tell that is windows specific and I’m not entirely convinced it’ll work with expired certs.

Its not windows specific and you can get a new cert in the unifi container. I feel like you are complicating a simple non issue. Just use the mobile phone app if its causing you this much grief. Their own app ignores certs.

Will the stable version be updated to a new version soon since people have been running 10 for a few weeks? Or should I still stick with 9.x?

2 hours ago, CrashnBrn said:

Will the stable version be updated to a new version soon since people have been running 10 for a few weeks? Or should I still stick with 9.x?

Im waiting for the next version of 10. Currently its 10.0.160 released 4 December but this is needing quite a number of patches and unifi have not managed to release the next version yet as stable. Its rare for this to take 2 months so I can only assume there are lots of fixes coming. If you are not missing anything, I would just wait.

Edited January 22Jan 22 by PeteAsking

3 hours ago, PeteAsking said:

Im waiting for the next version of 10. Currently its 10.0.160 released 4 December but this is needing quite a number of patches and unifi have not managed to release the next version yet as stable. Its rare for this to take 2 months so I can only assume there are lots of fixes coming. If you are not missing anything, I would just wait.

10.0.162 is marked as official for a while now, but only a minor bugfix release. 11 Notes has not pushed this release out though

https://community.ui.com/releases/UniFi-Network-Application-10-0-162/2efd581a-3a55-4c36-80bf-1267dbfc2aee

Edited January 22Jan 22 by fat

1 minute ago, fat said:

10.0.162 is marked as official for a while now

Both of my Unifi gateway devices (runs Network on the device) have been on 10.0.162 for a few weeks now with no issues. If there are things that still need to be fixed in Network 10.0.160+ that have not been affecting me. Finger crossed that does not change.

On 1/11/2026 at 2:54 PM, wgstarks said:

I'm not sure this is the right place for this question, but maybe. I'm sick of getting invalid certificate warnings from my browser when connecting to the webui. My preference would be to access the ui via http since it's only exposed locally but that doesn't seem to be an option at all.☹️

I'm wondering if there is some way to make a self-signed certificate work???

Don't know if you have this resolved yet, but yes it is possible to load a self-signed P12 certificate into the Docker container using the keytool command (inside the Docker container) to import the certificate into the Unifi keystore.

I believe this is the general commands I used (sorry it has been awhile since I imported my self-signed certificate)

###Runinng shell in docker container

docker exec -it container-name sh

### Create a P12 file for Unifi

openssl pkcs12 -export -out {your desired pfx/p12 file} -inkey {your private key} -in {your certificate file} -certfile {the signing intermediate} -password pass:{your desired pfx/p12 password}

### Backup the old cert and install the new one

sudo mv /usr/lib/unifi/data/{pfx/p12 name as above} /usr/lib/unifi/data/{pfx/p12 name as above}.old

sudo cp {pfx/p12 name as above} /usr/lib/unifi/data/{pfx/p12 name as above}

### Backup the old keystore and install the new one

sudo mv /usr/lib/unifi/data/keystore /usr/lib/unifi/data/keystore.old

keytool -importkeystore -destkeystore /usr/lib/unifi/data/keystore -srckeystore {pfx/p12 name as above} -srcstoretype PKCS12 -srcstorepass {pfx/p12 password as above} -deststorepass aircontrolenterprise -srcalias 1 -destalias unifi

Don't know if you have this resolved yet, but yes it is possible to load a self-signed P12 certificate into the Docker container using the keytool command (inside the Docker container) to import the certificate into the Unifi keystore.

I believe this is the general commands I used (sorry it has been awhile since I imported my self-signed certificate)

###Runinng shell in docker container

docker exec -it container-name sh

### Create a P12 file for Unifi

openssl pkcs12 -export -out {your desired pfx/p12 file} -inkey {your private key} -in {your certificate file} -certfile {the signing intermediate} -password pass:{your desired pfx/p12 password}

### Backup the old cert and install the new one

sudo mv /usr/lib/unifi/data/{pfx/p12 name as above} /usr/lib/unifi/data/{pfx/p12 name as above}.old

sudo cp {pfx/p12 name as above} /usr/lib/unifi/data/{pfx/p12 name as above}

### Backup the old keystore and install the new one

sudo mv /usr/lib/unifi/data/keystore /usr/lib/unifi/data/keystore.old

keytool -importkeystore -destkeystore /usr/lib/unifi/data/keystore -srckeystore {pfx/p12 name as above} -srcstoretype PKCS12 -srcstorepass {pfx/p12 password as above} -deststorepass aircontrolenterprise -srcalias 1 -destalias unifi

Thanks. I’ll give this a try.

On 1/22/2026 at 4:27 PM, Hoopster said:

Both of my Unifi gateway devices (runs Network on the device) have been on 10.0.162 for a few weeks now with no issues. ...

Just curious if you are still using this Unifi Reborn docker since you have two gateways (assuming they are cloud gateways vs. UXG) running the Unifi Network server. How does that work having two instances running on your network? Did you have to update your APs to inform to the gateway instances?

I am just trying to understand how the Cloud gateways works with or eliminate the need of running a Unifi Controller docker. I will be deploying a UXG-Lite since I did not quite understand how I would manage the cloud gateways from my current Docker Unifi Controller since they run their own Unifi network server.

Edited February 6Feb 6 by beanmeister
Spelling

5 hours ago, beanmeister said:

Just curious if you are still using this Unifi Reborn docker since you have two gateways (assuming they are cloud gateways vs. UXG) running the Unifi Network server. How does that work having two instances running on your network? Did you have to update your APs to inform to the gateway instances?

I am just trying to understand how the Cloud gateways works with or eliminate the need of running a Unifi Controller docker. I will be deploying a UXG-Lite since I did not quite understand how I would manage the cloud gateways from my current Docker Unifi Controller since they run their own Unifi network server.

The two Unifi Cloud Gateways (Network Controller built in) are one each in my two homes 260 miles apart. They are on separate subnets but thanks to the magic of Ubiquiti SD-WAN/Teleport, devices on both subnets are accessible as if they were on the same LAN. It sure makes scripted backup of one Unraid server to another in the other location easy.

I have this Unifi Reborn network docker as a backup should a UCG fail and I quickly need to put my old USG back into service temporarily. Before getting the UCG, I used this docker with great success.

Edited February 7Feb 7 by Hoopster

Having issues with USW Flex 2.5G 8 PoE not adopting, I had to ssh into my u7 pros to change the inform ip, but I can't ssh into the switch.

Any help is appreciated?

1 hour ago, Sean1911 said:

Having issues with USW Flex 2.5G 8 PoE not adopting, I had to ssh into my u7 pros to change the inform ip, but I can't ssh into the switch.

Any help is appreciated?

I have the same switch and it adopts fine. Did you set the inform ip in the controller settings and ensure the usw flex has at least one port on the same network as the controller and plugged in etc so it can reach it?

10.0.162 was pushed by 11 notes yesterday it looks like. Unraid showed the update as I am using the 10-unraid tag. Update went fine and it is back up and running so far without any immediate issues. It has only been running for 5 mins so far but will update this thread if anything goes wrong

On 2/8/2026 at 6:58 AM, Sean1911 said:

Having issues with USW Flex 2.5G 8 PoE not adopting, I had to ssh into my u7 pros to change the inform ip, but I can't ssh into the switch.

Any help is appreciated?

Are you using the inform host override function in the controller? If so have you set this to the unraid server IP? I have the same switch and it is working fine. Also are you using any VLANs with this switch? If so try disabling any VLANs and try again as some of the older flex mini switches would have issues because of this

10.1.84 has just gone official according to the UI releases forum. There is a large changelog, so if you need stable functions I would suggest waiting a few weeks after a few people here test it out after 11 Notes pushes it out.

I am finally getting around to moving to this container from the old Unifi container. If things don't go well on my upgrade can I just delete the new Unifi reborn container and go back to my old Unifi Controller container?

From the release notes of the latest 10.1.84 update, sounds like ubiquiti is starting to push their Unifi OS server over the network application.

9 hours ago, wayner said:

I am finally getting around to moving to this container from the old Unifi container. If things don't go well on my upgrade can I just delete the new Unifi reborn container and go back to my old Unifi Controller container?

Depends if you use method 1 or 2.

I am not sure what you mean by method 1 or 2. I am going by post 1 "To install this docker" where you say to backup, stop the old container, install the new container, start it and restore. Is that method 1?

If there were problems could I then just. stop and delete the new container and then start up the old container and it will work as if nothing ever happened.

18 minutes ago, wayner said:

I am not sure what you mean by method 1 or 2. I am going by post 1 "To install this docker" where you say to backup, stop the old container, install the new container, start it and restore. Is that method 1?

If there were problems could I then just. stop and delete the new container and then start up the old container and it will work as if nothing ever happened.

Yes if you restore a backup config to a new docker then that would be fine and you can potentially stop the new one and start the old one if needed.

10.0.162-unraid is considered stable now. Page 1 is updated to reflect:

(home) Stable: 11notes/unifi:10.0.162-unraid

Old Stable: 11notes/unifi:9.5.21-unraid

Old Old Stable: 11notes/unifi:8.6.9-unraid

Please note if moving from v9 to v10 you need to follow the instructions on page 32. Simply changing the tag will not provide a workable move from a v9 to v10.

• P

Hello,

I'm still running on lscr.io/linuxserver/unifi-controller:7.4.156 on by backup unraid server. I installed 11notes/unifi:10-unraid on my primary unraid server. I'm moving my backup unraid server to another home that I have unifi in and need a controller there.

I took a backup and shutdown the unifi 7.4 docker on the backup server, installed the new unifi reborn on the primary server, restored the backup, waited and restarted the docker. I had to change the container port from 8080 to 8081, 8080 was already in use by another docker. I ssh'd to my switches and APs and used the set-inform http://<controller-ip>:8081/inform on each. They 'seemed' to adopt after doing the set-infrom. However after a short while, everything went offline. I couldn't get to anything, even on the same vlan. I couldn't ping anything even when I set my desktop to a static IP (same vlan). I had to factory reset the switch both the primary, backup, and desktop were plugged into. After which I shutdown the unifi reborn docker, started the old 7.4 controller. I then went around and factory reset my other devices. They adopted into the old 7.4 and all is well again and has been for a few hours. I'm assuming it's stable.

What did I do wrong or what is the best approach to what I'm trying to do? Or a better suggestion(s)?

45 minutes ago, RichJacot said:

Hello,

I'm still running on lscr.io/linuxserver/unifi-controller:7.4.156 on by backup unraid server. I installed 11notes/unifi:10-unraid on my primary unraid server. I'm moving my backup unraid server to another home that I have unifi in and need a controller there.

I took a backup and shutdown the unifi 7.4 docker on the backup server, installed the new unifi reborn on the primary server, restored the backup, waited and restarted the docker. I had to change the container port from 8080 to 8081, 8080 was already in use by another docker. I ssh'd to my switches and APs and used the set-inform http://<controller-ip>:8081/inform on each. They 'seemed' to adopt after doing the set-infrom. However after a short while, everything went offline. I couldn't get to anything, even on the same vlan. I couldn't ping anything even when I set my desktop to a static IP (same vlan). I had to factory reset the switch both the primary, backup, and desktop were plugged into. After which I shutdown the unifi reborn docker, started the old 7.4 controller. I then went around and factory reset my other devices. They adopted into the old 7.4 and all is well again and has been for a few hours. I'm assuming it's stable.

What did I do wrong or what is the best approach to what I'm trying to do? Or a better suggestion(s)?

We dont provide an upgrade path from such an old version to such a new version. You will need to trawl through the first 10 pages and create an upgrade path that goes through various versions to get to 10.