04/02/2025

 

Today marks this docker as stable.

Current tags are:

Stable (home user): 11notes/unifi:9.0.108-unraid

Old Stable (business user): 11notes/unifi:8.6.9-unraid

Old Old Stable (Zero downtime user): 11notes/unifi:8.5.6-unraid

 

The xml for this docker has been changed today. Installing a new docker will install version Old Old stable going forward.

 

A result of this change means there is now no supported upgrade path from the linuxserver.io image to this image. You can try it, but we no longer support it and you are on your own. Sorry if you cant migrate to this image and are still using linuxserver.io. You had over 1 year to migrate so I feel enough time was provided.

 

Please ensure you pick a tag, make sure you are using one of the above, and check in every so often to manually upgrade to the next tag if you need to. You can expect a new Stable tag once a month or so or maybe every 2 months, and every 6 months for Old Stable. Check yearly if you use Old Old Stable. Remember to make a copy of your appdata unifi docker before upgrades (while it is stopped) somewhere for rolling back if need be and you wont have to worry about issues.

 

Thanks

P

 

 

4 hours ago, PeteAsking said:

Current tags are:

Stable (home user): 11notes/unifi:9.0.108-unraid

I’m a little confused???

Is the tag “Stable” or is it “11notes/unifi:9.0.108-unraid”?

5 minutes ago, wgstarks said:

I’m a little confused???

Is the tag “Stable” or is it “11notes/unifi:9.0.108-unraid”?

11notes/unifi:9.0.108-unraid

 

be confused no more, friend. 

Edited February 5, 20251 yr by PeteAsking

Just now, PeteAsking said:

11notes/unifi:9.0.108-unraid

Thanks.

 

Perhaps consider a request. I know you want to evaluate new versions before implementing. I agree with that. Perhaps a new tag system though. “stable”, “old_stable” and “old_old_stable” just as an example. This would allow everyone to update in their preferred branch without having to change the tag every time. Just an idea. I have no idea if it could be implemented or not.

3 minutes ago, wgstarks said:

Thanks.

 

Perhaps consider a request. I know you want to evaluate new versions before implementing. I agree with that. Perhaps a new tag system though. “stable”, “old_stable” and “old_old_stable” just as an example. This would allow everyone to update in their preferred branch without having to change the tag every time. Just an idea. I have no idea if it could be implemented or not.

It can be implemented. This automatic updates will never be implemented however until unraid has a system in place that guarantees a copy and safe backup of a container that is to be upgraded or tag changed by default so that if a bad update occurs, we are guaranteed to know everyone has a safe backup. Unless this is implemented you will never get an automatic tag. 
 

my official reason for not implementing a ‘latest’ tag is this:

 

I do not feel like it. 
 

This opinion has 0% chance of changing until unraid has an auto backup feature that is on by default. If this is an issue for you please make your issues known to unraid feature requests, requesting auto backups by default of appdata containers. 
 

thanks. 

Edited February 5, 20251 yr by PeteAsking

33 minutes ago, PeteAsking said:

If this is an issue for you please make your issues known to unraid feature requests, requesting auto backups by default of appdata containers.

Not an issue. Just a request.

Unfortunately some users need to be protected from themselves. 

Hello, I just saw unifi unraid reborn on the new app page. What is the difference with the unifi network app that already exist here: https://github.com/linuxserver/docker-unifi-network-application ?

AFAIK this one has the mongodb build in, no other docker needed.

AH, ok. I do like having it on the side, allow for better db backup

1 hour ago, Nodiaque said:

Hello, I just saw unifi unraid reborn on the new app page. What is the difference with the unifi network app that already exist here: https://github.com/linuxserver/docker-unifi-network-application ?

Linux IO was originally going to kill this docker and stop maintain it.. Originally, Linux IO had a docker that had MongoDB db and unifi all in one. then they moved to not house mongdb due to CVE and issues with unif and the network stack. Since Unifi doesn't acknowledge a docker instance of the unif network application and linux IO having issues with unifi and the database and maintain it. They moved to a different approach... (there is a lot of old data on linux IO forum page when Pete Asking made the XML for this AIO docker image...

As Linux IO have been flip-flopping back and forth...
Review: https://docs.linuxserver.io/images/docker-unifi-network-application/
 

My understanding atm is that Linux IO does maintain a unfi network application docker that doesn't come with mongdb, meaning you must provide and maintain your own separate docker...

My understanding is that linux IO also left unraid due to other reasons...
If you want unif by linux io you can
https://github.com/linuxserver/docker-unifi-network-application/issues/new/choose

there support forum and more info:

 

I didn't know that Linux Io left unraid. That's new to me considering the amount of app I see from them still being release in ca

17 minutes ago, Nodiaque said:

I didn't know that Linux Io left unraid. That's new to me considering the amount of app I see from them still being release in ca

There was quite a few that exodus left during Unraids core and Key sub changes. There are some community members that maintain their dockers. Linux IO still makes and maintains docker images themselves. They appear to be active on the forum still...
https://forums.unraid.net/profile/66820-linuxserverio/

As I said flip flops... data a few yearas ago to now... I personly like linuxIO docker iamges they have a good support folowing and maintain...

Exampls, as forum cahges and Some data lost on the form other from old respoinse on dockers being depriacted... etc etc...

as I'm having a hard time Looking for there old response... 
 

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 images for unifi based on ubuntu which you can use on non-unraid deployments. We worked together and created an unraid specific docker.

 

Reason for this implementation was I had the following requirements:

1) Secure (reason for picking an ubuntu based image)

2) Reliable (testing is perfomed on new images prior to release announce - we do not auto build and just push them out without manual testing)

3) Ability to upgrade safely with no downtime (version changes are tested between previous tags eg: old stable ---> new version etc)

4) Was an all in one docker (I believe splitting the docker can impact 1-3).

 

When using linuxserver.io the issues of reliability were most prominent especially between version changes.

 

Since creating the images I believe the objective has been by in large achieved over the past 1+year.

 

At this time there are 11notes images for either unraid or your own linux box deployments so you are not tied to any specific deployment.

 

As I use unifi myself everything is also loaded up for you guys to use if you want to. If you find something better, feel free to use that. We have our way of achieving 1-4 and believe its the best but thats just our opinion.

 

Some downsides to our approach:

 

1) Slower release time. Releases are ready when they are ready. If it takes 20 days to be happy then you just have to wait. 
 

2) No automatic updates. You have to check in every few months and manually update as and when you can schedule in time for your deployment. 
 

3)? probably something else I forgot. 

 

P

 

 

Edited February 5, 20251 yr by PeteAsking

1 hour ago, PeteAsking said:

Since creating the images I believe the objective has been by in large achieved over the past 1+year.

I agree with this and thank you.  

 

I switched to this image ASAP after Linuxserver announced the dual docker approach to the UniFi controller.  I have several current docker containers from Linuxserver installed in Unraid (also a couple from Binhex) but I may also look into switching.

 

I was very, very happy with this image as long as I was using it which was until very recently.  I only went away from it when UniFi implemented Site Magic (super easy SD-WAN site--to-site VPN) and the UniFi routers/gateways i chose to use at both sites required use of their built-in controller. 

 

For anyone looking for a UniFi controller Docker container, I see no reason to not use this one.

I just noticed that there's a different instance of unifi-controller-reborn in the Community Apps Directory from the one I have installed.

 

The unifi-controller-reborn I installed (months ago) shows it was added "May 30, 2015". It no longer shows a Maintainer.

 

The unifi-controller-reborn shown in the Community Apps Directory shows it was added "Feb 4, 2025". Maintainer is PeteAsking.

 

They both link to this forum thread, pretty sure it's the same app. What's going on? Do I need to uninstall my existing instance and install the new PeteAsking's unifi-controller-reborn?

32 minutes ago, gentlemoon said:

I just noticed that there's a different instance of unifi-controller-reborn in the Community Apps Directory from the one I have installed.

 

The unifi-controller-reborn I installed (months ago) shows it was added "May 30, 2015". It no longer shows a Maintainer.

 

The unifi-controller-reborn shown in the Community Apps Directory shows it was added "Feb 4, 2025". Maintainer is PeteAsking.

 

They both link to this forum thread, pretty sure it's the same app. What's going on? Do I need to uninstall my existing instance and install the new PeteAsking's unifi-controller-reborn?

Not sure how this happened for you as the app never existed in 2015. However it is not relevant. If it is installed, then it is working and it does not matter if your apps directory is showing some quirk. To update it just change the tag on your docker container to one of the currently supported tags that is newer than what your are running and the network application will be updated. Everything you need once it is installed is entirely contained in the docker image in your unraid box so whatever happened to the apps cache or whatever is no longer of any consequence for you. 

to explain: the apps directory of unraid is just reading an xml file on what to do to setup and install a docker image for you. It does not reread this xml file once the docker is running. So in your docker tab and under the docker settings the setup is done once installed and whatever the apps tab says is not relevant to the function of the docker running then on. Simply modify the docker how you want at this point forward. 

 

What is your current tag you are using?

Edited February 7, 20251 yr by PeteAsking

Thanks for your response, PeteAsking.

 

My tag is: 11notes/unifi:8.6.9-unraid

 

I have occasionally updated that tag using the old stable version from the top of this thread.

 

Quote

Not sure how this happened for you as the app never existed in 2015.

 

Right, I installed unifi-controller-reborn last year when the Linux IO docker switched to requiring a separate docker with the database. It's also strange that the current unifi-controller-reborn in Community Apps shows "Added Feb 4, 2025", since this app has existed for over a year (this thread was started in November 2023).

 

Attached what I see in the Community Apps directory versus what is installed.

 

 

Edited February 8, 20251 yr by gentlemoon

9 minutes ago, gentlemoon said:

Thanks for your response, PeteAsking.

 

My tag is: 11notes/unifi:8.6.9-unraid

 

I have occasionally updated that tag using the old stable version from the top of this thread.

 

 

Right, I installed unifi-controller-reborn last year when the Linux IO docker switched to requiring a separate docker with the database. It's also strange that the current unifi-controller-reborn in Community Apps shows "Added Feb 4, 2025", since this app has existed for over a year (this thread was started in November 2023).

 

Attached what I see in the Community Apps directory versus what is installed.

 

 

Regards tag: 

 

that is fine. Just carry in checking in every 6 months for an update to old stable and you will be fine. 
 

Regards apps: unsure how unraid works but I can tell you it is not relevant at all. Once the docker is installed, I could literally delete the xml and remove the app front that community apps page and it would not inpact your docker one bit. The docker checks with dockerhub for any changes (eg; for dockers that use a latest tag) directly and never uses that apps page ever again. As long as you can change the tag on your docker occasionally to a new tag in the 11notes repository on dockerhub it will always work fine. So dont worry about it as its not relevant. 
 

Feb 4 was when I made some changes to the xml file so probably something happened then but I dont know and squid who might know does not respond to my messages or reply on threads when you tag him so no clue. Only he knows the inner workings. 

Home user tag (Stable) now available: unifi:9.0.114-unraid

 

https://community.ui.com/releases/UniFi-Network-Application-9-0-114/35b6e9ac-f63d-46c9-bbbe-74a4a61ac95f

 

As always a backup of your container prior to upgrade is required.

 

P

On 2/4/2025 at 1:00 PM, PeteAsking said:

...

A result of this change means there is now no supported upgrade path from the linuxserver.io image to this image.

...

 

Can you elaborate what this actually means?  I hope it doesn't mean I can't import my configuration from the linuxserver.io image running 7.5.187. 

 

Main reason I haven't upgraded is because I never saw an upgrade path that would preserve my private SSL keys so that I would not have to redo it (I am still trying to recall how I got it to work).

Edited February 12, 20251 yr by beanmeister

8 hours ago, beanmeister said:

 

Can you elaborate what this actually means?  I hope it doesn't mean I can't import my configuration from the linuxserver.io image running 7.5.187. 

 

Main reason I haven't upgraded is because I never saw an upgrade path that would preserve my private SSL keys so that I would not have to redo it (I am still trying to recall how I got it to work).

Can you explain why you use a private ssl key and what your end goal is for doing this? 

10 hours ago, PeteAsking said:

Can you explain why you use a private ssl key and what your end goal is for doing this? 

May be I used the wrong terminology.  I issue and manage my own certificates via pfsense for internal https usage like Unifi, pfsense, and unRAID admin web pages (servers that have no reason to be on the public Internet).  With Unifi, I somehow got the linuxserver docker to use my private certificate so that it does not pester me with the security warning when I access the Unifi web interface via https.

I just cant recall how I did it, but eventually will have to accept the fact that once I move to the reborn docker, I will have to redo configuring the docker to use my self authorized certificate.  I just hope I can import my current configuration file once I can track down the instructions for configuring the Unifi docker to use my self authorized certificates.

 

Hopefully that is a little bit clear.  I apologize for any wrong usage of terminologies, but my end goal is to avoid being pester with the security warning every time I access the Unifi admin web page using https.

Thanks @bmartino1.  Yes, I am trying to use my self authorized certificate for the Unifi controller.  However, if I recall correctly, I just need the commands to run within the Unifi Controller docker instance to register/import my certificate files so that the Unifi controller uses my self authorized certificate for https connection within my internal network.

I just can't seem to find the instructions for importing in self authorized certificates for now.

I even tried to use a copy of my current unifi appdata for the reborn docker (thereby reusing the keystore file, but that did not work.). Somehow, I need to import my self signed certificates files into the reborn unifi controller keystore file.

@beanmeister you realise you can just import a certificate to a machine right?

for windows like:

eg: access unifi webpage in Edge browser. Get cert error. 
click lock then error then cert icon. 
 

click details

click export. Save cert to desktop. 
view under details : subject alternative name. Note name you must use (unifi)

 

ensure you can ping unifi by name eg:

ping unifi

in cmd

 

if not working add entry on dns server or add in local pc hosts file entry eg:

x.x.x.x  unifi

 

right click cert on desktop and choose install. Install to local machine. Place into personal store. 
 

access https://unifi:8443

 

note there is no cert warning as cert is trusted. 
 

this is not acceptable to you? Seems easier than waiting and searching for a solution for more than a whole year.

 

also does not change functionality in anyway, error or no error. Running a docker with known exploits however… 
 

p

Edited February 13, 20251 yr by PeteAsking