I deleted the container, used fresh template and changed the port, that worked. However no my 3 APs are showing as adopting. All my other settings are there the SSIDs and network override etc.

Did you run set_inform on the AP’s?

https://community.spiceworks.com/how_to/9692-manually-setting-the-controller-address-for-a-unifi-ap

Be sure to use port 8081.

18 minutes ago, bally12345 said:

I deleted the container, used fresh template and changed the port, that worked. However no my 3 APs are showing as adopting. All my other settings are there the SSIDs and network override etc.

Also have a look at this where this was discussed. I had the same problem and this fixed it.

 

12 minutes ago, snowboardjoe said:

Also have a look at this where this was discussed. I had the same problem and this fixed it.

 

It is working fine on 8080 I will just my other container to run on 8081

20 hours ago, Babar said:

Of course, I am using Unraid.

Then you are not installing through CA. Remove the existing one and add it again from CA.

You have modified settings you shouldn't modify.

2 hours ago, saarg said:

Then you are not installing through CA. Remove the existing one and add it again from CA.

You have modified settings you shouldn't modify.

I have removed and downloaded the latest docker again from CA.

But still unable to load the web gui. Any ideas where to start looking now? Thanks.

 

See screenshots below.

 

 

 

 

 

 

Hello All 

 

Ever since I moved the unifi controller over to the custom network within docker so I can use Let’s Encrypt as a reverse proxy all my unifi devices are showing disconnected 

 

am i missing something ? Do i need to change some other settings?? 

 

Unifi uses other ports for comms, so as its on its own network within docker all the ports in the past were forwarded to an IP address on my local network for example 192.168.0.100

 

do i now just forward them to the UNRAID box? Or do i forward them to the 172 address that docker gives the controller when I move it over to the internal network ? 

Edited January 22, 20206 yr by IKWeb

On 1/16/2020 at 11:05 PM, helpermonkey said:

hey folks - so I need help with a problem + a little hand holding/how-to.

 

First, when I go to setup the docker, it fails to start because it wants to map to port 8080 for device communication (i have sabnzbd on port 8080). So to that end, is there a recommended alternative port? I'd rather not adjust sab b/c of how many other utilities rely on it.

 

Then my next question is what's a good "Idiots Guide to Moving Controllers"? I setup my unifi a long time ago and when i did it - i did not realize that the device married itself to the controller - i no longer have the computer that was the original controller. Furthermore - i don't remember all of the tweaks i made to the configuration and finally - while i would like to use my unraid server as the controller - i usually use wifi to connect into it - so i'm guessing that i'll need to attach KVM to it and i just want to make sure I don't screw it up. I looked at this https://community.ui.com/questions/Transferring-Unifi-Controller/1e541dee-e484-407e-aaec-28c2711db6d7 but when i go to wizards in EdgeOSX i get

Any advice would be welcomed.

bumping as i'd still love some help with this.

20 hours ago, Babar said:

I have removed and downloaded the latest docker again from CA.

But still unable to load the web gui. Any ideas where to start looking now? Thanks.

 

See screenshots below.

 

 

 

 

 

 

Which port are you connecting to?

11 hours ago, saarg said:

Which port are you connecting to?

Default config points to https://10.10.100.64:8443/

2 hours ago, Babar said:

Default config points to https://10.10.100.64:8443/

Try changing the appdata path to /mnt/cache/ instead of /mnt/user/.

Finally got it going. I didnot have to change any config.

 

I guess there was something not working in the background and finally everything clicked.

I have migrated my controller config from VM to the docker, and the devices have migrated and integrated with the new controller docker.

Thanks.

Have had the controller up and running from years. For some reason no able to access the webui today.  Logs were no help but changed from mnt/user to mnt/cache and have access again which is great.  Was there some change to the container that caused this?

 

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

I'm pretty new to Ubiquiti's Unifi Controller - is there a version people recommend? Is LTS newer than 5.9?

9 hours ago, Derek_ said:

I'm pretty new to Ubiquiti's Unifi Controller - is there a version people recommend? Is LTS newer than 5.9?

At the time of this post, LTS is 5.6.42, so no, LTS is several versions older.

 

LTS is definitely the recommended version, unless you enjoy being a beta tester. Unifi has a pretty consistent history of breaking things with new releases, so stick with what works, especially if this is a production setting. If it's your testing lab, go right ahead with latest, but be ready for havoc with any given update.

I am still on the old deprecated container running LTS 5.6.40 and really would like to update to the current container.  I see in unRAID under the Docker tab that there is an apply update link next to the old docker container.  Should I use that to update or should I do it manually as posted on page 1 of this thread?  I would like to stick with LTS for now.

 

My current Unifi container is configured to run on a virtual interface in its own VLAN (br0.30).  I hope the update will maintain this settings since it has been so long that I forgot how to do it if I had to do it again.

 

Edited January 25, 20206 yr by mifronte

2 hours ago, mifronte said:

I see in unRAID under the Docker tab that there is an apply update link next to the old docker container.

The will just update to the latest version of the old container.

 

2 hours ago, mifronte said:

should I do it manually as posted on page 1 of this thread?

Do this to change to the new UniFi-Controller container.

8 hours ago, Hoopster said:

Do this to change to the new UniFi-Controller container.

It has been a long time, but how do I get the new container again?

 

Never mind, I found it in the APPs tab.

Edited January 26, 20206 yr by mifronte

So I updated to the current LTS container using my current appdata.

 

I can login into the controller, but all my APs are showing up with their radios (2g and 5g) showing disabled.  Also, I cannot see the clients connected to each AP.  The APs themselves are still working fine and clients have connections.  It is that the controller is not showing the client connections and is reporting that the radios are disabled.

 

I am running firmware 3.9.3.7537 on the APs.  If I need to update the AP firmware, what is a good stable firmware to use for the current LTS 5.6.42?

 

Update

====================

Looks like I need a newer firmware.  I upgraded one of the AP to 4.0.66.10.832 and now it correctly reports the radios and the client list is back.  Don't know if this is the best 4.0.x.x firmware for the UAP-AC-Pro and UAP-AC-Lite.

 

So if I am going to run the newer firmware, is there a recommended controller and device firmware that is quite stable?  I have several remote APs and can only maintain them via the controller.

Edited January 26, 20206 yr by mifronte

Just started moving everything other to unraid docker and unifi controller is on the list. The installation was pretty simple, but when I navigate to the WebUI I get an SSL error and chrome won't let me move forward.

 

Running the latest release, since my old controller is on 5.12.xx. 

On 1/25/2020 at 11:46 PM, jonathanm said:

At the time of this post, LTS is 5.6.42, so no, LTS is several versions older.

 

LTS is definitely the recommended version, unless you enjoy being a beta tester. Unifi has a pretty consistent history of breaking things with new releases, so stick with what works, especially if this is a production setting. If it's your testing lab, go right ahead with latest, but be ready for havoc with any given update.

Thanks.

 

I'm currently running it on an old laptop (it's mostly off). My friend told me to update it, and export the settings ".unf" file (?) and then try the Docker. But in doing so i see that the laptop is running 5.12. Would it be safe to use the LTS (5.6x) Docker? Perhaps i'll have to use 'latest' Docker to safely import the .unf file?

 

I'm generally happy to be a bit behind.  I wouldn't mind changing it to a different stream down the track - Is that possible?

 

Last question i think: I don't see any LTS monikers on Ubiquiti's site. Where does the LTS come from?

5 hours ago, exdox77 said:

Just started moving everything other to unraid docker and unifi controller is on the list. The installation was pretty simple, but when I navigate to the WebUI I get an SSL error and chrome won't let me move forward.

 

Running the latest release, since my old controller is on 5.12.xx. 

 

It's caused by the self-signed certs. So you need to add the controller to the whitelist. If that doesn't work, try using Firefox.

10 hours ago, saarg said:

 

It's caused by the self-signed certs. So you need to add the controller to the whitelist. If that doesn't work, try using Firefox.

Crises diverted with proxy server and some SSL certs. Thank you for the feedback.

Looking forward to the upgrade form the 5.12 to 5.13 train.  Personally, I'd love to see 5.13.9 so I can test (on this controller) some of the beta hardware.

1 hour ago, RokleM said:

Looking forward to the upgrade form the 5.12 to 5.13 train

And that will happen when Ubiquiti releases the 5.13 branch as "stable."  As long as it is just a testing or RC release, it won't show up in this container, thankfully.  When it becomes a "stable" release, the "latest" tag will pull that instead of the 5.12 branch.