In support of anyone else struggling adopting a Unifi AP to the TrueNAS Unifi App in Electric Eel (but might apply in other configurations, but I don’t know)
I struggled this weekend to Install my first AP under Unifi.
Basically after much hit and miss, it got as far as (not) adoption stage.
Googling eventually led me to a link and to complete adoption I did the following (YMMV)
ssh into the new AP (WiFiman seemed to be the easiest way to get this)
ssh ubnt@“IP Address of AP”
Password ubnt
This issue this command
set-inform http://“IP Address of your TrueNAS server”:30073/inform
Once issued, it immediately started adoption. What I am NOT certain about is what if any preceding steps were needed in unifi IOS app or the controller, but this was my stumbling block.
Thank you for that. I thought I was the only suffering from Unifi-Derangement Syndrom (UDS), an affliction similar to Frigate-Derangement-Syndrome (FDS) in that UDS and FDS take something that should be simple and make it incredibly hard. In the case of UDS, I get the container up, it boots, it presents a web-ui, it manages to talk to the mothership for authentication but then initiating a restore of a working cloudkey backup file results in a KerSPLAT!
The Unifi is never heard from again, remaining stuck in a “Deploying” state of mind. What I take from the process is that relying on a backup to make the switch from a hardware cloudkey 2 to a unifi container is a no-go, so the entire controller setup has to be rebuilt from scratch. I am not going to even start to attempt that until I have Fangtooth running here so I can set the unifi docker App at the same IP address as the original IP for the cloudkey 2.
But if even that doesn’t work re: adoption, I’ll have your tip to fall back on. Thank you again!
In the settings of the Unifi app you need to override the Inform Host and set the IP address of your server. Otherwise it advertises the IP of docker network.
Thank you for that. So after an hour of “Deploying” after attempting a restore from a backup file (same version), I decided to stop the App, and restart it. To my surprise, the App did finally start.
I pull up the interface which then helpfully tells me that the login and password I have used successfully earlier today to do a Cloudkey 2 backup no longer functions.
I wonder, is perhaps the Unifi App not able to reach the internet once it has restored a profile and that’s the reason why the thing is not able to authenticate the password?
Thing is, it says the password is wrong, suggesting it can reach the internet or that I should be using a login/password combo like ubnt/ubnt. Has anyone else had this issue?
