PeteAsking

Interesting. Unsure why unraid would do that. At any rate that tag is about to be the latest stable so it wont matter in your case.

Great. I cant wait to be required to stand up and run an entire server just to setup a few access points and some switches.

Alpha testers on tag unifi:9-unraid will have already been pushed an update for them to test/break their install.

If you are an expert you can change whatever you want. I just dont provide any help or assistance since its beyond the scope of basic support and setup. If you want to fiddle around with settings that change how it works thats fine because you = the support at that point.

Can you explain why you have blanked out your internal ip address? Does unraid run internally on x.x.x.216 or is this some sort of public ip?

The API does not talk to your docker container directly. It requires you to create a link to allow unifi direct control over your self hosted container using the remote management option and signing up on and doing all the linking with their website. Once you can remotely access your container via https://unifi.ui.com and control your unifi docker remotely,as they have a link and can control it, then the api is https://unifi.ui.com/api Most of us do not use this feature as the entire point of self hosting is to control things yourself and not give a 3rd party keys to your box, however its totally up to you. I cant really help much since I dont use that feature myself and have zero interest in it. P

I love you.

I mean I know Im pretty good. But Im not that good. you have to actually tell me something about your setup. Like have you checked its in bridge mode and if your unraid server ip was 192.168.56.4 (example) can you open a browser and access https://192.168.56.4:8443/ As an example? Try in a private browser window and the usual stuff. Also that version would not be a fresh install as its not the tag selected when installing fresh right now. I just checked.

Feel free to get them working on unraid if you want. Then explain how you did it. The images are there for you to use.

Unraid is not compatible with this type of image which is why they were never brought over, and they dont work. We tried to get them working but was impossible due to how unraid dockers work.

Good job. Take a backup and update the container to old old stable at least and then follow that update path (check the forum 1-2 times a year for an updated old old stable tag).

@timg11 it sounds like you are basically done. Remember I can support installing the docker but how the actual controller works and what it supports - that is up to unifi. If there is some warning or error with your config you can go to their forums and ask them what to do. We dont create the code or the unifi controller and have no say over how it functions. That error has been raised on their forums as a bug or some sort of anomaly. How to resolve it exactly, you can investigate directly with them: https://community.ui.com/questions/Your-WiFi-networks-need-attention-Your-previous-WLAN-Override-configurations-are-not-supported-by-t/f30cf0fb-f54a-425d-af8f-875e4b8d6b0d End of the day there will bound to be some fixing up of your config to be done after waiting so long before updating. You are essentially 3 years out of band for updates. Unifi barely support moving between each update properly, so you might want to manage your expectations on expecting everything to go 100% smoothly. As far as I can tell, barring some functionality issues you are good to go. Engage with their forums if you consider the last few steps to be a big deal or just bite the bullet and go for it and fix anything that needs fixing after. Good luck P

What happened @timg11 ?

No clue if they are supported. You should look that up, your site specific requirements etc. The error is normal and unraid related. Dont worry about it.

No nothing else to change. Just that tag. “So, on the new controller it will need to have the IP of the Unraid server, and I will check the box by "Override inform host with controller hostname/IP" Correct?” Yes if you dont set this then aps will fail to adopt and it wont work. You dont need the l2 discovery typically. That is mdns and not normally required.

When you hit install it will bring up a page with a newer tag listed. Im saying to change it to an older tag which I suggest above. Once installed it will be blank. You will need to turn off the old controller, login to this new controller and restore the backup. Then set the inform ip to be the unraid server. Eg: 192.168.2.7 or something. Hopefully the ap’s will detect the new controller after this has happened. If not reboot the docker on unraid then if still not try one of the ap’s next.

Seems like the ap you listed is supported. Dont forget to set the inform ip or devices wont adopt when you try. And make sure the old network controller is not running at test time.

I would take a manual backup from your current windows install, then install using this tag fresh: 7.5.187-unraid Then I would import that backup file and see if it worked. You can then move to an 8 series tag and then 9 so long as the ap’s support it. Note: if you have very old AP’s unifi dropped support for them. I will try look up what the latest docker image is that supports your ap you mentioned. Try finding this out before you upgrade .

The u7 lites are incredible pieces of kit imho and priced fairly for what you get out of them (and seem like they wont ever break). I always get the lites as they have no moving parts and upgrade whenever a new spec comes out like wifi6-wifi7. I have 4 aps around my home so its worth just getting many cheaper but capable aps as I have a large area to cover including the garden area. Works really well.

This depends, on even on that page there are exceptions. We use an ubuntu image that requires an full init system and is designed to be secure, and thus having it all in one is no issue, and arguably more secure (havent checked how linuxserver does their separate containers or what base image they use). I feel the reliability and robustness of the container will over time, speak for itself. As far as I know, once people are up and running they have had near zero issues after. At least based on this forum.

We no longer officially support a migration from the old linuxserver option. This was provided for 1 year, and then dropped as 1 year was deemed enough time for users to migrate so there is now no official support. To do this you can try it on your own, and I would suggest using the oldest tag available in the docker repository and then restore a config from your linuxserver.io deployment. It should work if you do this and dig through the old posts on this page, as people asked many questions during this transition and all managed to do it. To answer your other question, yes this is a single container approach. P

I will let someone else comment on their experiences but the design goals of the project are : 'secure' and 'ease of use'. You are expected to throw whatever resources it needs at it and we expect it has a half decent CPU of 4 cores and 8gb assigned to deploy this docker. In 2025 I expect this requirement to be totally achievable on any modern system.

The tags are updated! Current recommended Home User tag: 11notes/unifi:9.2.87-unraid (Updated 19/06/2025) Current Company/Corporate recommended tag: 11notes/unifi:9.1.120-unraid (Updated 19/06/2025) Current Critical Infrastructure (no downtime) tag: 11notes/unifi:8.6.9-unraid (Updated 19/06/2025) Current ISwearOnAllThatIsGoodAndTrueThatIHaveABackupAndConsentToAlphaTesting tag: 11notes/unifi:9-unraid (Updated 19/06/2025) This docker now installs 8.6.9-unraid when deploying new by default. Some of you will notice a new 9-unraid tag. Please ensure you read the disclaimer before using it. Three times. Disclaimer: If you abuse this tag and complain things break it will be taken away from you forever and you will ruin it for everyone else and I will direct them to your inbox to complain. This is not a joke. You are helping to test if you use this tag and have a backup to restore from. 9-unraid will follow all updates on the 9 branch from unifi and deploy to you as they are available without testing. You can expect a similar tag for 10-unraid when unifi move to that version nomenclature. Thanks P

Yes it will automatically stay on the latest 9.2 branch if you use that tag (similar for 9 tag but wider scope). This is not supported with assistance here if you use that tag without some sort of backup automation so you can revert if it breaks as you will effectively be automatically an alpha tester at all times. This is to allow you to track a major build automatically while avoiding moving between major builds automatically. Its something new we have never tried before. Im not sure how intelligently unifi do their versioning. If it becomes a problem it may get removed in the future (ie people demand support and dont have any backups - as people seem to need protecting from themselves). There is the ca apps backup in the repository if you want to try these tags. Tracking 9-unraid is probably more useful than 9.2 as there is normally only 1-2 versions of minor point releases anyway.

Tag is 9.2.87-unraid for anyone alpha testing.