Unifi on truecharts

[ChaosBlades]

It has been a while since the last post on this thread but I want to hopefully save someone some time.

set-inform did not work for me exactly. I needed to set-defaults to reset the AP and tell the controller to forget the device as well. Then send the set-inform command. Once it shows up and you tell it to adopt I needed to send the set-inform command about once every 5 seconds while refreshing the page until I finally got "Getting Ready". Also noticed the container trying to chown 999:999 /unifi but the operation was not permitted. I did this manually. Not sure if that was part of my problem.

 

[eddwills95]

Based on these ports: https://help.ui.com/hc/en-us/articles/218506997-UniFi-Ports-Used I'm wondering if the 10001 should also be opened? That might help avoid having to use set-inform since the controller will be able to find the devices. Could be totally wrong though

 

[ChaosBlades]

Based on my searching this issue it is by no means uncommon or new. The UniFi thread that clued me into spamming set-inform was 5 years old.

https://community.ui.com/questions/UniFi-is-stuck-at-Adopting/596ee99e-5828-4fa2-930d-e6d3b68deba6

 

[petzku]

I just got this to discover my devices nicely without any of that set-inform nonsense. All that I needed to do is to make sure that my local dns resolves hostname unifi to the ip that has unifi controllers' ports visible and bam the devices were adoptable.

-Petteri

 

[Aviatorpaal]

As long as your IP address or hostname (which ever you used when you initially did set-inform on the Unifi gear) remains the same, you can just restore from backup. No need to perform tens, hundreds or thousands of set-informs

 

[Akshunhiro]

Hi all, found this while searching for my issue as I'm trying to move containers to use host path as storage

Also stuck on the chown 999:999 /unifi issue but not sure where I should be manually changing permissions after seeing @ChaosBlades reply above

Tried in the UniFi "AppData" dataset I've created for it and also in the run folder that's already created but it's not picking it up

Even tried create the data and log folders before recursively chowning unifi

Also tried recreating the container with "Automatic Permissions" but that's not working either

My errors;

Code:

chown 999:999 /unifi
chown /unifi: operation not permitted
<docker-entrypoint> Starting unifi controller service.
mkdir: cannot create directory '/unifi/data': Permission denied
mkdir: cannot create directory '/unifi/log': Permission denied

 

[Aviatorpaal]

Hi all, found this while searching for my issue as I'm trying to move containers to use host path as storage

Also stuck on the chown 999:999 /unifi issue but not sure where I should be manually changing permissions after seeing @ChaosBlades reply above

Tried in the UniFi "AppData" dataset I've created for it and also in the run folder that's already created but it's not picking it up

Even tried create the data and log folders before recursively chowning unifi

Also tried recreating the container with "Automatic Permissions" but that's not working either

My errors;

Code:

chown 999:999 /unifi
chown /unifi: operation not permitted
<docker-entrypoint> Starting unifi controller service.
mkdir: cannot create directory '/unifi/data': Permission denied
mkdir: cannot create directory '/unifi/log': Permission denied

This works like a charm for me:

 

[Aviatorpaal]

Code:

root@truenas[/mnt/WDPool/unifi]# ls -l
total 18
drwxr-xr-x 5  999 docker 11 Mar  1 17:33 data
drwxr-xr-x 3  999 docker  6 Nov 30 23:15 log
drwxr-xr-x 2 root apps    2 Nov 30 23:06 run

 

[Akshunhiro]

Thanks so much! I couldn't get it to work with the options you've shown in the GUI (Automatic Permissions) but it's working now after recursively chowning the UniFi folder and setting root:apps on the run file.

 

[Aviatorpaal]

Awesome! Glad I could help

Thanks so much! I couldn't get it to work with the options you've shown in the GUI (Automatic Permissions) but it's working now after recursively chowning the UniFi folder and setting root:apps on the run file.

 

[jaharmi]

I created datasets for "apps" and then "unifi" on a new TrueNAS Scale installation. I'm trying to deploy a UniFi app to use that, as per #27.

The app doesn't finish deploying with the Type of Storage set to "Host Path" and the Host Path set to tank/apps/unifi.

It did deploy for me when I used PVC.

I have "Automatic Permissions" checked, but that does not seem to be working for me. I see permissions errors in the log for this app.

ls -al tank/ | grep apps drwxr-xr-x 3 apps apps 3 Mar 29 15:06 apps ls -al tank/apps | grep unifi drwxr-xr-x 3 root root 3 Mar 29 15:08 unifi $ ls -al tank/apps/unifi total 53 drwxr-xr-x 3 root root 3 Mar 29 15:08 . drwxr-xr-x 3 apps apps 3 Mar 29 15:06 .. drwxr-xr-x 2 root root 2 Mar 29 15:08 run

Before I go chmod-ing and chown-ing, I want to verify what the ownership/permissions ought to be for each level. TIA.

 

[trekkie]

For those of you who google leaves you here.

An easier way to migrate your devices from your old controller to the new controller is here: https://lazyadmin.nl/home-network/migrate-unifi-controller/

Essentially - if you turn on the 'old' or 'legacy' interface, and 'export' the site, it will send the inform command to all your devices and they migrate over automagically. I mean ssh into each is easy, but if you have more than a couple can be tedious and it bemuses me that you used to be able to do this with a few clicks but now they want you to do it via command line? weird. (they = ubiquiti)

Hope that helps.