PeteAsking

Interesting @bmartino1 - so what is working and what is not working at this time?

Normally just takes a minute to restore.

@bmartino1 I will fix (or try to) the web ui error - blocked at some point this week. Once the restore happens is the docker stopped? Can you start it again and it is functional or no?

You cannot change the uid and gid of the docker at this time. It is unsupported. also unclear why you are changing other variables such as privileged and so on. the docker is in alpha state. Changes like this have not been attempted or tested at all. Only a very basic config is working at this time. I would encourage not to change anything beyond what is instructed.

One other thing. This particular tag had an issue where sometimes you have to restart a device to get it to adopt… unifi issue. If that happens just try powercycling the affected device. Could just be a transient error.

@bmartino1 starting afresh sounds fine. Do a restore and let me know. Dont forget to stop the old unifi docker.

Also what is actually not working? It appears like you can connect with the app after? @bmartino1

@bmartino1 please stop the docker from running and use this command: chmod 777 /mnt/user/appdata/unifi-controller-reborn then post the ls -l again. It is not altering the permissions from your output above. I believe the tags are correct.

Please also tell me what version of the controller the backup was made from.

unifi-controller-reborn/ drwxr-xr-x 1 nobody users 16 Nov 5 14:18 appears inconsistent. You need to set the permissions to 777 for it to run correctly at this time.

Can you post issues on the other thread @bmartino1? Start also by showing me an ls -l on the appdata folder so I can verify permissions are correct. Probably you also need to backup and restore like versions. As in dont try to backup on the old controller a very okd version then restore to the new docker container running a much later configuration that same backup. Forst bring the current docker into compliance and then do a backup/restore. This is the thread here:

You guys have to read the last few pages @bmartino1 and @kiwijunglist or you will miss what is happening. You currently have 2 options - go with linuxserver.io and 2 docker images running that communicate with each other as per @wgstarks work or a single new docker option that is the same as /similar to this current linuxserver option that I am working on. The entire hope and point of this exercise is that the community hopefully selects the most reliable/best option and eventually this is used going forward. That can only happen if you make an informed decision and post back your experience and preference after reviewing the options. Hope this makes sense. @wgstarks has been super helpful with everything so far.

Unsupported versions list: 8.0.24-unraid (Known regressions, skipped version). 8.0.28-unraid (Version skipped, did not pass testing).

Unifi no longer support docker, please move to their server version on a VM instead. CRITICAL: This docker requires an AVX capable CPU. There is NO upgrade path from 9x version to 10x. You MUST take a backup, delete the container/rename/archive etc and then redeploy the container from the app store and RESTORE your backup file. Do NOT move from 9x to 10x by upgrading the container. Ensure when moving to 10x you use 10.1.89-unraid as the first 10x version. 10x requires an avx capable CPU. If your CPU is older than 15 years, you cannot run this container anymore past 9x. Do not ignore this warning, mongodb will be broken if you attempt an upgrade. ADVANCED/EXPERIENCED USERS QUICK INFO: Choose your own adventure tag: https://hub.docker.com/r/11notes/unifi/tags Current recommended Home User tag: 11notes/unifi:10.1.89-unraid (Updated 09/09/2025 - “stable”) Current Company/Corporate recommended tag: 11notes/unifi:9.5.21-unraid (Updated 19/06/2025 - “old stable”) Current Critical Infrastructure (no downtime) tag: 11notes/unifi:8.6.9-unraid (Updated 19/06/2025 - “old old stable”) Current ISwearOnAllThatIsGoodAndTrueThatIHaveABackupAndConsentToAlphaTesting tag: 11notes/unifi:10-unraid (Updated continuously - “alpha”) NOTE: do not reduce the ram allocated to the docker image below 8GB. This is unsafe. To upgrade to version 10x from version 9x please see this post on page 32: NORMAL USERS START HERE: The important information at a glance section: --------------------------------------------------------------------------------------------------------------------------------------------------------- Development status of community app: Canary: 31/10/2023 - 04/11/2023 [COMPLETE] Alpha: 04/11/2023 - 23/11/2023 [COMPLETE] Beta: 23/11/2023 - 08/01/2024 [COMPLETE] Delta: 08/01/2024 - 19/10/2024 [COMPLETE] Stable: 19/10/2024 - 04/02/2025 [COMPLETE - stable achieved] Canary - Dev build only, not public use. Alpha - Testing only, not suitable for home or production use. Request for community to help to test if able. Beta - Suitable home use only. Delta - Suitable home or production use, requires specific steps to be followed to function. Stable - Suitable all deployments, easy deploy ready. --------------------------------------------------------------------------------------------------------------------------------------------------------- Docker tags of unifi builds: Alpha: This ‘latest’ tag is now currently disabled as we are not currently testing and does not exist at this time. 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. (home) Stable: 11notes/unifi:10.1.89-unraid Old Stable: 11notes/unifi:9.5.21-unraid Old Old Stable: 11notes/unifi:8.6.9-unraid AlphaTester: 11notes/unifi:10-unraid When a new release is available from unifi, the first 7 days after it is released are reserved for internal testing. No tag will be made available until after 7 days irrespective of how many people complain they really need the new version right now. Deal with it. VERY IMPORTANT NOTE, CRITICAL: In the repository there are 2 types of image. version-unraid and just version. eg: 7.5.187-unraid vs 7.5.187. the pure version numbers run the docker in 1000:1000 and require special changes to the appdata directory permissions to function. If you use the latest tag, you will need to make these changes. If however you are a normal non alpha tester, you can use the version-unraid tag which correctly sets the user as 99:100 eg: 7.5.187-unraid When selecting a new tag to upgrade to, always use the version-unraid tag. These are tested specifically for Unraid. The other tags are for pure docker deployments. Alpha (latest tag, do not use) : This tag is either "latest" or has been released by unifi and reverted back to release candidate due to issues. Do not use except for specific reasons understood by you (do not complain to me when deployment breaks, its on you to fix). Stable: Latest stable build vetted by community for home use only. Newest features present, that are stable. Old Stable: Latest stable build in production vetted by community for home or production use. Old Old stable: Production builds that lag behind to avoid issues. Updated less often and skips low quality builds, has fewest new features by design. --------------------------------------------------------------------------------------------------------------------------------------------------------- Unifi-Controller: Unifi. Unraid. Reborn. https://github.com/pallebone/UnifiUnraidReborn The how to section: This docker expects you to use tags to move between builds. When you install the docker you will note that a specific tag has been chosen for you on deployment. Do not use "latest" tag. Using latest tag means we cannot and will not support or help you on this thread. You are considered the fixer/expert if you use latest. To choose a desired tag review the tags here: https://hub.docker.com/r/11notes/unifi/tags To install this docker Instructions include moving from a different docker image/community app however these steps can be ignored if not appropriate. 1) Login to current running controller web interface and take a backup of 7 days on current controller. You will obtain a backup file such as: network_backup_02.11.2023_08-10_v7.5.187.unf Make sure old version of unifi controller is the same version you will be migrating to. Unifi is difficult if the versions are different. 2) Stop old Unraid controller/Other controller and turn off autostart/disable from self starting. You can leave this old deployment alone at this point in case you ever need it again. 3) Go to apps and install new controller (unifi-controller-reborn). Avoid changing random values you dont understand/cant fix yourself in the template. 4) Start container and set to autostart. Restore your backup, it will require you to manually start it again after backup is restored. Note: When you restore, there is no confirmation the restore completes. After a minute or so the docker simply stops on unraid (refresh docker page on unraid ui) and the unifi web page just hangs on restoring. You must manually start the docker image again when its stops. The container should now be running normally at this point. If not check steps again and ask for help. To Upgrade this docker - eg: from version 7.5.187-unraid to unifi:8.0.7-unraid To upgrade simply edit the docker, change the tag and then hit apply. Your previous tag will look something like: 11notes/unifi:7.5.187-unraid you will change it to some later version like: 11notes/unifi:8.0.7-unraid YOU WILL NOT ALTER ANY OTHER SETTING DURING THIS UPGRADE STEP. YOU WILL NOT EDIT NETWORKING, PORTS, OR ANYTHING. DONT DO IT. This will result in the best success rate of the docker upgrading if you do this, and then readopting the devices. --------------------------------------------------------------------------------------------------------------------------------------------------------- Notes: Your networking should be the same if coming from an old controller or devices wont re adopt eg: ”I had my networking on the old container set to br0 and a fixed IP - it wouldn't adopt in the new world until I made that match” KNOWN ISSUES: 1) Clicking on the docker under a brX network implementation and using the "WebUI" button does not work. This will never be fixed. Type the ip you set and port you set into a web browser if you use brX networking (instead of bridge). Use bridge networking if this is a deal breaker for you. 2) When restoring a unifi config backup file the docker stops, and does not start again automatically due to some error. You must manually intervene and start it when it stops during the restore process. This is being investigated. Removed install instructions no longer needed: 3) Set directory permissions for new container (can be done after deploying image in step 4, see and read instructions). To do this prior to deploying the app, use command such as: install -d -m 777 -o 99 -g 100 /mnt/user/appdata/unifi-controller-reborn Commands must be used via ssh or the web terminal (little icon in top right of unraid web interface). If you deploy the image first by following step 4 without doing this, and let it create the docker appdata directory, then you will need to stop the docker then run these commands and start it again afterwards: mkdir /mnt/user/appdata/unifi-controller-reborn chmod 777 /mnt/user/appdata/unifi-controller-reborn chown nobody /mnt/user/appdata/unifi-controller-reborn chgrp users /mnt/user/appdata/unifi-controller-reborn The entire point of this is that if you do a 'ls -l' on the directory with your docker containers you will see the permissions are set as: drwxrwxrwx 1 nobody users 0 Nov 3 16:41 unifi-controller-reborn/ By default if you do not do this, the permissions will be drwxr-xr-x and the docker app will not be able to run and write files to this directory.

Im going to make a support thread for this new docker container option, then on this thread everyone can discuss the direction you think works best for the community without worrying about what I think. Will edit this comment when the support thread has been moved by a mod and post the link. Hopefully some people provide their opinion so its not like 3 people making a decision for 100s of people. edit:

I have updated the docker to post a popup message for now when installing instructing users what to do on first install. As far as I can tell, so long as you follow the initial setup instructions everything works fine after that. So summary: 1) Take backup 7 days on current controller. 2) Stop old unraid controller and turn off autostart. 3) Set directory permissions (can be done after deploying image if preferred, see notes). 4) Go to apps and install new controller (unraid-controller-reborn) 5) Start container and set to autostart. Ensure it can write files and functions normally and you can change/update it etc as required. Restore backup, will require you to manually start it again after backup is restored. It seems pretty basic, just dont have an immediate fix for the "fix directory permissions" issue at this moment. It is a one time thing, however, not needed ever again.

Ok will take a look, also the container has updated with unraids repository so can be tested, albeit with the instructions to fix the directory.

Ok so for now I can see the issue but not figure out how best to resolve it. There are several ways but none are automatic. The easiest ways I found to change to this image are like this: 1) Take backup 7 days on current controller. 2) Stop old unraid controller and turn off autostart. 3) Go to apps and install new controller (unraid-controller-reborn) 4) Once it is installed, stop the container (it cant write files to the directory unraid creates so does not work) 5) Either ssh into the box and use chmod like "chmod 777 /mnt/user/appdata/unifi-controller-reborn" OR if you dont like that go to Tools - New Permissions then choose "shares" and "appdata" and let unraid fix the permissions (unclear why this is not done by unraid when creating a new appdata directory, also unclear if this tools-new permissions thing is safe/supported?). 6) Start container and set to autostart. Now it can write files and functions normally and you can change/update it etc as required. Thoughts on this? Kind of unsure why unraid behaves like it does. Not really an expert obviously on unraid and its docker implementation -P Edit: also just waiting for unraid to update my xml settings so I have to wait for that to complete before anyone can test it. Edit2: Wow so apparently unraid has a web terminal so you can just open the web terminal and copy and paste the following 1 line at a time before installing the app: mkdir /mnt/user/appdata/unifi-controller-reborn chmod 777 /mnt/user/appdata/unifi-controller-reborn chown nobody /mnt/user/appdata/unifi-controller-reborn chgrp users /mnt/user/appdata/unifi-controller-reborn Instead of these 4 commands you can also try: install -d -m 777 -o 99 -g 100 /mnt/user/appdata/unifi-controller-reborn That also seems to work. Unsure how to make that happen automatically at this time.

I think you might have just helped me figure it out. I will go change something. You were totally wrong but I like the way you think.

Yes but I think that only works if the docker maintainer has actually coded to accept those variables which is not the case for this image and it tries to use 1000:1000 and is hard coded into the image.

So made some progress but still stuck on this last part because I dont understand unraids docker enough. Basically you can deploy the community app "unifi-controller-reborn" now and when you deploy it it will deploy but not start. To fix it you have to stop the container after, then ssh and go to /mnt/user/appdata/ and do a chmod 777 unifi-controller-reborn/. Now it can write to the directory and everything works and saves correctly and it works like a normal container. What I can work out is how to get unraid to initially set the permissions on the folder when creating the docker image so this part Im stuck on now. - P

Yes when its working to my standard of quality. Also if this is the direction people want to go. If everyone votes to go with 2 containers then that would be the direction instead. Have to please the community.

There is now an ALPHA community app that you can test if you would like to. Instructions - 1) Login to current linuxserver.io unifi controller and take a backup (7 day backup seems reasonable?). 2) Turn off current linuxserver.io unifi controller and disable autostart. 3) Download and install new community app "unifi-controller-reborn" and enable autostart if desired. 4) Restore settings from backup file after logging into the app, once it stops the controller you will need to start it again. Current issues: If you change any settings whatsoever on the docker container all settings are lost and you have to restore again from backup. Im working on it. You have your backup file and the old container is untouched so presumably between those 2 options you can go back if need be. Many thanks P

Just an update, still having real trouble communicating with Squid. I will try reach out to someone else. - P

Thank you for doing this and showing how to do it. This is exactly what we need. Multiple options the community can collectively decide on. So long as we dont get super attached to a particular solution and let everyone collectively decide which is a better option then we can go all in one direction or the other when the time is appropriate. Currently I have everything in place except a way to get a community app published for unraid as Im having trouble getting hold of squid who is the unraid person we have to speak to to get something published. However I imagine he is just busy which is why we havent heard from him. Either way Im not particularly worried about getting a good solution in place by January. Since we have 2 potential paths forward it seems likely that one will be fruitful by then and everyone can then start a new forum thread and support each other going forward. Unraid is very flexible and it seems capable in doing pretty much whatever you want.