[Support] - Unifi-Controller: Unifi. Unraid. Reborn.


Recommended Posts

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:8.0.26-unraid

 

Current Company/Corporate recommended tag: 11notes/unifi:8.0.7-unraid

 

Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid

 

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 -

Stable: n/a

 

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. 

 

Stable: 11notes/unifi:8.0.26-unraid

Old Stable: 11notes/unifi:8.0.7-unraid

Old Old Stable: 11notes/unifi:7.5.187-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.

277435263-1b01facd-1b15-4ba7-9495-e709c2

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 (unraid-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.

Edited by PeteAsking
  • Like 1
  • Thanks 1
Link to comment

thank you. was having a hard time finding the dockers' forum post. Quick links for support. yes. i will post my finding here.

 

image.thumb.png.6919c0d83007a5e3df794c94fd9b497a.png

 

root@BMM-Unraid:/mnt/user/appdata# ls -a
./   MakeMKV/              binhex-syncthing/  docker-xfs.img  mongodb/    plex/              unifi-controller-reborn/    vm_custom_icons/
../  Unraid-PiholeDOHDOT/  clamav/            macinabox/      nextcloud/  unifi-controller/  unifi-network-application/
root@BMM-Unraid:/mnt/user/appdata# ls -l
total 52428804
drwxr-xr-x 1 nobody  users             126 Nov  3 22:59 MakeMKV/
drwxrwxrwx 1 nobody  nogroup            58 Sep  7 02:36 Unraid-PiholeDOHDOT/
drwxrwxr-x 1 nobody  users              66 Oct  1 23:46 binhex-syncthing/
drwxr-xr-x 1     100 console           120 Nov  5 01:31 clamav/
-rw-r--r-- 1 nobody  users     53687091200 Nov  5 14:54 docker-xfs.img
drwxr-xr-x 1 nobody  root              312 Nov  5 00:51 macinabox/
drwxr-xr-x 1     999 users             762 Nov  5 14:22 mongodb/
drwxr-xr-x 1 brandon ssh-allow          82 Sep  7 14:41 nextcloud/
drwxr-xr-x 1 nobody  users              14 Sep 28 00:23 plex/
drwxr-xr-x 1 nobody  users              16 Sep  4 18:12 unifi-controller/
drwxrwxrwx 1 nobody  users             174 Nov  5 14:00 unifi-controller-reborn/
drwxr-xr-x 1 nobody  users              16 Nov  5 14:18 unifi-network-application/
drwxrwxrwx 1 nobody  users              40 Nov  1 14:51 vm_custom_icons/
root@BMM-Unraid:/mnt/user/appdata# 

 

 

  • Like 1
Link to comment

I wil run a chmod -R 777 to the apdata fodler and repost here soon.

 

from the docker unifi contorler: im using the latest tags.

form the app it claims that is is network version 7.5.187

 

image.thumb.png.3d1e457efcce9636712e8e195bd199c2.png

 

image.thumb.png.102c1332f924380b923de7e2e16ad453.png

 

 

image.thumb.png.bdac78a510e7dd6d01803ff25e3815a5.png

 

so im not sure what version I made the back from is. Nor how to tell what version unfi-controler-reborn is using:

 

root@BMM-Unraid:~# mc

root@BMM-Unraid:/mnt/user/appdata# chmod -R 777 unifi-controller-reborn/
root@BMM-Unraid:/mnt/user/appdata# ls -l
total 52428804
drwxr-xr-x 1 nobody  users             126 Nov  3 22:59 MakeMKV/
drwxrwxrwx 1 nobody  nogroup            58 Sep  7 02:36 Unraid-PiholeDOHDOT/
drwxrwxr-x 1 nobody  users              66 Oct  1 23:46 binhex-syncthing/
drwxr-xr-x 1     100 console           120 Nov  5 01:31 clamav/
-rw-r--r-- 1 nobody  users     53687091200 Nov  5 15:10 docker-xfs.img
drwxr-xr-x 1 nobody  root              312 Nov  5 00:51 macinabox/
drwxr-xr-x 1     999 users             762 Nov  5 14:22 mongodb/
drwxr-xr-x 1 brandon ssh-allow          82 Sep  7 14:41 nextcloud/
drwxr-xr-x 1 nobody  users              14 Sep 28 00:23 plex/
drwxr-xr-x 1 nobody  users              16 Sep  4 18:12 unifi-controller/
drwxrwxrwx 1 nobody  users             174 Nov  5 14:00 unifi-controller-reborn/
drwxr-xr-x 1 nobody  users              16 Nov  5 14:18 unifi-network-application/
drwxrwxrwx 1 nobody  users              40 Nov  1 14:51 vm_custom_icons/
root@BMM-Unraid:/mnt/user/appdata# 

 

Link to comment

Weird I see that too. i have no problem starting over. mainly use the docker to keep the firmware upto date and to stop spaming pihole unifi dxnaames.

 

I have deleted the folder and starting fresh:

 

root@BMM-Unraid:~# mc

root@BMM-Unraid:/mnt/user/appdata# mkdir /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# chmod 777 /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# chown nobody /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# chgrp users /mnt/user/appdata/unifi-controller-reborn
root@BMM-Unraid:/mnt/user/appdata# ls -l
total 52428800
drwxr-xr-x 1 nobody  users             126 Nov  3 22:59 MakeMKV/
drwxrwxrwx 1 nobody  nogroup            58 Sep  7 02:36 Unraid-PiholeDOHDOT/
drwxrwxr-x 1 nobody  users              66 Oct  1 23:46 binhex-syncthing/
drwxr-xr-x 1     100 console           120 Nov  5 01:31 clamav/
-rw-r--r-- 1 nobody  users     53687091200 Nov  5 15:20 docker-xfs.img
drwxr-xr-x 1 nobody  root              312 Nov  5 00:51 macinabox/
drwxr-xr-x 1     999 users             762 Nov  5 14:22 mongodb/
drwxr-xr-x 1 brandon ssh-allow          82 Sep  7 14:41 nextcloud/
drwxr-xr-x 1 nobody  users              14 Sep 28 00:23 plex/
drwxr-xr-x 1 nobody  users              16 Sep  4 18:12 unifi-controller/
drwxrwxrwx 1 nobody  users               0 Nov  5 15:20 unifi-controller-reborn/
drwxr-xr-x 1 nobody  users              16 Nov  5 14:18 unifi-network-application/
drwxrwxrwx 1 nobody  users              40 Nov  1 14:51 vm_custom_icons/
root@BMM-Unraid:/mnt/user/appdata# 

Link to comment

I run a ASUSTeK COMPUTER INC. ROG STRIX B450-F GAMING II with AMD Ryzen 7 5700G with Radeon Graphics @ 3800 MHz and 32 GB of ram

I mainly run some network security dockers and plex server with unraid.

 

Starting fresh, I make the following extra changes:

 

stoped to old docker that will be depricated after i made a back.

image.thumb.png.5c5e50a0538c43ce6b7e2b67ff12a084.png

I go to system > setting > Backup > download a backup. I now have a file: network_backup_11.05.2023_01-49-PM_v7.5.187.unf this file contins data such as the newrok wifi names and other networking settings.

 

Now to install your verison of the new docker:

*(I have yet to tie that docker to the phone app. the previous post picture is from the old docker.)

 

I go to the community app page and install this docker.

I change your extra parameter from 8 to 4. And add a mac address and hostname for a networking setup.

 

image.thumb.png.1d8bfb7db905d49732e86aef5b0f3d6e.png

 

I add 2 variables (may not be needed.) mainly for top and resource checking.

image.thumb.png.2f8373f6c3cdf25ae746fe92f1686b14.png

 

 

 

Link to comment

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. 

Edited by PeteAsking
Link to comment

OK I have removed the guid and UID.

 

runing the docker i'm now at setup unifi

docker run
  -d
  --name='unifi-controller-reborn'
  --net='br0'
  --ip='192.168.1.4'
  --privileged=true
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="BMM-Unraid"
  -e HOST_CONTAINERNAME="unifi-controller-reborn"
  -e 'TCP_PORT_8443'='8443'
  -e 'UDP_PORT_3478'='3478'
  -e 'UDP_PORT_10001'='10001'
  -e 'TCP_PORT_8080'='8080'
  -e 'UDP_PORT_1900'='1900'
  -e 'TCP_PORT_8843'='8843'
  -e 'TCP_PORT_8880'='8880'
  -e 'TCP_PORT_6789'='6789'
  -e 'UDP_PORT_5514'='5514'
  -e 'MEM_LIMIT'='4096'
  -e 'MEM_STARTUP'='2048'
  -e 'UMASK'='002'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
  -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg'
  -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw'
  --memory=4G
  --mac-address 02:42:C0:A8:01:5B
  --hostname UNIFI-DOCKER '11notes/unifi:7.5.187'
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
78f9b7f9391cbfc94a0006931ac7b55d511a1b2568ba5fd8137084ab3d2d6a42

The command finished successfully!

 

Clicking web UI

 

18137958_Screenshot2023-11-05153820.png.80c6a437b66091594a47aea36dc9ccf0.png

image.png.5338155e721166abf9c3253cd7fce6ec.png

 

but i can access the web ui 

 

image.thumb.png.a8cfea1a9832d5bdd34d5aa9c05f293d.png

 

and log in

noting in the logs:

image.png.10dd6f1c8e83773a96321c2973d6981b.png

 

root@BMM-Unraid:/mnt/user/appdata# ls -l
total 52428800
drwxr-xr-x 1 nobody  users             126 Nov  3 22:59 MakeMKV/
drwxrwxrwx 1 nobody  nogroup            58 Sep  7 02:36 Unraid-PiholeDOHDOT/
drwxrwxr-x 1 nobody  users              66 Oct  1 23:46 binhex-syncthing/
drwxr-xr-x 1     100 console           120 Nov  5 01:31 clamav/
-rw-r--r-- 1 nobody  users     53687091200 Nov  5 15:41 docker-xfs.img
drwxr-xr-x 1 nobody  root              312 Nov  5 00:51 macinabox/
drwxr-xr-x 1     999 users             762 Nov  5 14:22 mongodb/
drwxr-xr-x 1 brandon ssh-allow          82 Sep  7 14:41 nextcloud/
drwxr-xr-x 1 nobody  users              14 Sep 28 00:23 plex/
drwxr-xr-x 1 nobody  users              16 Sep  4 18:12 unifi-controller/
drwxrwxrwx 1 nobody  users             174 Nov  5 15:38 unifi-controller-reborn/
drwxr-xr-x 1 nobody  users              16 Nov  5 14:18 unifi-network-application/
drwxrwxrwx 1 nobody  users              40 Nov  1 14:51 vm_custom_icons/
root@BMM-Unraid:/mnt/user/appdata# 

 

 

 

Link to comment

So now I will configure the unfi docker and go to restore my file the same way I backed it up.

 

last time the restore errored the webpage froze and i got a java error in the docker log. let try with out the uig/guid this time.

 

image.thumb.png.435797eb66caef86c781cfc2ae32bee9.png

 

I go to setting > system > Backup > 

 

image.thumb.png.67563829de820055de9c4c3399bf4102.png

 

i click restore:

 

image.thumb.png.653a60fb80ee989f8e93ceb8e1e1366e.png

 

image.png.f12d9dab640aa643d100d9f921913af1.png

 

 

get the message in the top right:

image.png.b2c4aded3964670831eb7bc01264cdad.png

 

error in docker log:

 

text  error  warn  system  array  login  

Exception in thread "Thread-9" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
        at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:168)
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1172)
        at com.ubnt.service.C.Ö00000(Unknown Source)
        at com.ubnt.ace.Launcher.Ô00000(Unknown Source)
        at java.base/java.lang.Thread.run(Thread.java:833)
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called

** Press ANY KEY to close this window ** 

Link to comment

ok, after refreshing the web page the docker did hault and fail went to stop and got execurtion error clicked doker at the top and saw it is off...

Starting the docker did get me back into my instance with a restroe: will now attempt to readopt or see if the restore grabed my ubiquity devices.

 

the restore failed last time and would not go to the web ui. that is when i DM you.

 

image.thumb.png.1c13a59d2996df0da73e50407f700290.png

Link to comment

At this time, everything is working as it should. idk what broke last time. I have tested a hard reset and adopt. that is working. I assumed there was a java error in the docker where something needed to be installed. This is not the case. I will have to play around and see if backup and firmware restores are working. things are good. Thank you again PeteAsking for your assistance on this.

 

 

 

  • Like 1
Link to comment

side note:

image.thumb.png.a7f1bbfbe95b27d340ac9f8cd96df078.png

To keep firmware and backups from old system.

 

You will need to restore first. Then copy the firmware and backup folder in its entity. This way you keep downloaded device firmware for your devices. And have a restore point for the future in the even of errors.

 

I also recommend stopping the docker and backing up the entire app data folder for Docker settings and config as a precaution before adding or editing any data.

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.