[Support] Linuxserver.io - Unifi-Controller

[b0m541 1]

Hey guys, I have a problem with the unifi controller that I cannot figure out and fix on my own. I had the latest branch container running.

 

The whole thing started with an UAP AC Mesh that was connected using mesh to a wired UAP becoming disconnected and when power-cycled not being able to get connected again.

 

I then wired that UAP AC Mesh to the subnet where the controller and all unifi components are wired. A reset and even a factory reset resulted in the UAP AC Mesh being shown as "Adopting" in the controller but not making any progress.

 

I then realized that UDP port 10001 was not showing in the docker port mappings and experimented with removing port mappings from the Controller container, but after starting the containers the mappings still were there. I could not find an explanation for the UDP 10001 mapping being missing (also after re-installation) or removed mappings still being shown.

 

So I re-installed the container from scratch with default mappings. After that the container would start, but the UI would _not_ work any more.

So I tried the branches 5.9 and 5.8 but none of that worked. Also restarting Docker or the server would not help! Its saying "UniFi Controller is starting up... Please wait a moment"

 

So now I am stuck with a non-working cointainer! (I do have a backup the the "latest" appdata, but my appdata backup folder got somehow wiped - of course when it is needed. But the are:

unifi-controller/data/backup/5.14.23.unf
unifi-controller/data/backup/6.0.20.unf
unifi-controller/data/backup/6.0.22.unf) So I guess I should be able to roll back to 5.14.23.

 

The UAP AC Mesh (default login) shows: Status:      Unknown[11] (http://"controller-ip":8080/inform) which looks fine

 

Any help is welcome!

 

Edited September 26, 2020 by b0m541

[jj_uk 9]

Can you get to the UI from a fresh container install? When i installed the controller docker, it took quite a long time to start up the first time. I also had a bunch of issues with my router (asus) so i changed it for a USG.

Edited September 26, 2020 by jj_uk

[PeteAsking 38]

Just letting everyone know I been on this image:

 

image

5.14.23-ls76

Last updated24 days agobylinuxserverci

 

for 2 weeks, zero issues and all working great. Its pretty up to date and no changes in almost a month from unifi.

 

I see 6.0.24 is released and looks like people are having less issues with v6 now... so most likely major bugs been fixed with it but will probs hold off myself until another 2-3 months have passed to ensure its super stable.

 

So far staying a version behind has worked pretty well for me so far and honestly no clue what features are actually missing from 6.14, or what you are actually gaining by going to 6 so no real rush to change either.

 

Stay safe

 

P

[PeteAsking 38]

4.3.21.11325 firmware update has a lot of complaints, especially apple devices.

 

Would stay on 4.3.20.11298 if you dont have any issues. For some reason this is another pushed update by Unifi, went from RC to stable in 12 hours. Bizarre, same sort of thing happened with v6 so obviously some quality control issues at the moment.

[PeteAsking 38]

Here is an interesting thing to note from latest IOS update. I may think about updating soon as a result (see bottom message). Will review further tomorrow and post findings. 

[jang430 9]

Hi.  Currently using 5.9.29 Stable Release.  I have 3 SSIDs, each using different VLANS.  I am also using Sophos XG Firewall, v18. I have enabled VLAN function.  When you connect to each SSID, I do get different subnets, and each VLAN has it's own firewall rule.  

 

I got this working.  My problem is, every day or 2 days, my APs gets discconected from the controller, and goes adopting loop once again.  Since I'm using docker, and maybe because VLAN, the 2 APs don't see the Unifi Docker controller immediately.  I have to ssh into it, and do set-inform http://......  

 

I think the important question is, why does it disconnect from the controller?  If it doesn't disconnect, I don't have to re-adopt.  The most I've gone without disconnecting from the controller is 2 days.  I don't know where to begin checking.  

[PeteAsking 38]

2 hours ago, jang430 said:

Hi.  Currently using 5.9.29 Stable Release.  I have 3 SSIDs, each using different VLANS.  I am also using Sophos XG Firewall, v18. I have enabled VLAN function.  When you connect to each SSID, I do get different subnets, and each VLAN has it's own firewall rule.  

 

I got this working.  My problem is, every day or 2 days, my APs gets discconected from the controller, and goes adopting loop once again.  Since I'm using docker, and maybe because VLAN, the 2 APs don't see the Unifi Docker controller immediately.  I have to ssh into it, and do set-inform http://......  

 

I think the important question is, why does it disconnect from the controller?  If it doesn't disconnect, I don't have to re-adopt.  The most I've gone without disconnecting from the controller is 2 days.  I don't know where to begin checking.  

If you cant complete the command

ping unifi

from each site then this could be one possible reason. You should ensure dns allows this to resolve.   

[jang430 9]

I can complete the command:

 

set-inform http://192.168.x.x:8085/inform

 

And the AP gets adopted asap.  After a day when I recheck, it's in the adoption loop.

 

[PeteAsking 38]

4 hours ago, jang430 said:

I can complete the command:

 

set-inform http://192.168.x.x:8085/inform

 

And the AP gets adopted asap.  After a day when I recheck, it's in the adoption loop.

 

That doesnt use dns as it is specifying the IP. Check my previous post. 

[PeteAsking 38]

Also 8085 is not the default port. You should change that to the default if you are wanting to minimise issues in your setup. 
 

the default the units will check for is:

 

http://unifi:8080/inform

 

so that should resolve and work if you dont want problems. 

Edited October 21, 2020 by PeteAsking

[jang430 9]

When you say ping unifi, you mean ping the ip address of the controller from devices connected to the AP?  That works currently.  I'm not using 8080 since Sabnzbd docker container already using it.  

 

Is there any way to set in controller set-inform url?

[PeteAsking 38]

No. The name ‘unifi’ is what the AP’s etc look for by default so you should have an A record in your local DNS server that translates unifi to the ip of the controller or alternatively add that to the local hosts file of the device(s). 
 

This is the default hard coded inform url they look for:

 

http://unifi:8080/inform

 

that should be resolvable as in the event of any issues the devices will try that inform url. 
 

You can change your Sabnzbd docker to use a different port so unifi can have the correct port back. Its more important and unifi dont really support changing the port very well/many people have issues. 

Edited October 22, 2020 by PeteAsking

[jang430 9]

Thank you.  I'll see how I can change in my local DNS.  Will report back once done.

[PeteAsking 38]

6 hours ago, jang430 said:

Thank you.  I'll see how I can change in my local DNS.  Will report back once done.

What is your local DNS server you are using? You can also add it to hosts file of AP instead.

Edited October 22, 2020 by PeteAsking

[Morrtin 3]

Maybe it has also to do something with the network type bridge. The Docker is running in 172. network. After I reset port allocation back to 8080 and forgot the AP, the status switch to "Managed by other". When I hit plus button for adopting the AP I saw that the Inform URL was http://172.13.x.y:8080/inform.

 

But the AP itself is not on the bridged network. So I went to Settings / Controller and changed following setting:

 

Controller Hostname/IP: 10.0.0.x

(+) Override inform host with controller hostname/IP

 

The apdopting URL changed to http://10.0.0.x:8080/inform

 

Let's see if this changes helped. Will report back in some days.

 

[PeteAsking 38]

Morriton are you a different person? Or are you following on from the previous post from jang430?

[Morrtin 3]

I am a different person 🙂 My replay was to jang430 posts. I have/had the same problem and took your advice and change sabnzbd to a different port and Unifi to 8080 and had this "findings".

[PeteAsking 38]

11 minutes ago, Morrtin said:

I am a different person 🙂 My replay was to jang430 posts. I have/had the same problem and took your advice and change sabnzbd to a different port and Unifi to 8080 and had this "findings".

What you have written sounds like it will fix it for you.

[jang430 9]

5 hours ago, PeteAsking said:

What is your local DNS server you are using? You can also add it to hosts file of AP instead.

I don't have one.  I use a Sophos XG firewall.  After your instructions, I will have to do research to get it up and running.

 

 

What does this mean?

"But the AP itself is not on the bridged network."  Is mine considered to be on a bridged network?  I mentioned above I've setup VLAN on my Cisco Switch, so that each SSID is on it's own subnet.

Edited October 23, 2020 by jang430

[PeteAsking 38]

11 hours ago, jang430 said:

I don't have one.  I use a Sophos XG firewall.  After your instructions, I will have to do research to get it up and running.

 

 

What does this mean?

"But the AP itself is not on the bridged network."  Is mine considered to be on a bridged network?  I mentioned above I've setup VLAN on my Cisco Switch, so that each SSID is on it's own subnet.

In his case he had to check here:

 

Would be great if you could also check your inform IP on the controller is set correctly.

[PeteAsking 38]

Would also be great if you let us know what is typed into that section currently.

[jzawacki 4]

Apologies if this has been addressed, I saw notes around page 8 of others having issues using custom ports, but I couldn't find a solution.  It's unfortunate that so much of this thread is standard UniFi controller support over container support.

 

Anyway, I have been unsuccessful using custom ports for this container as well.  I have configured the docker properly, but the defaults are still used.  If I go into the container and look as the system.properties file, the port options are all commented out, so I'm not sure how the UniFi controller is supposed to know to use the custom ports.

 

Thanks,

James

[jang430 9]

@PeteAsking

Mine says 

 

I just noticed there is a space between IP and colon ":" Will this explain why it doesn't reconnect when disconnected?  But I believe this doesn't explain why AP keeps on disconnecting from controller.  Will read on it this weekend, how to create local DNS.  Will also change ports 8080.

[PeteAsking 38]

6 hours ago, jang430 said:

@PeteAsking

Mine says 

 

I just noticed there is a space between IP and colon ":" Will this explain why it doesn't reconnect when disconnected?  But I believe this doesn't explain why AP keeps on disconnecting from controller.  Will read on it this weekend, how to create local DNS.  Will also change ports 8080.

Not too sure if that is valid even without a space. You can only put an IP address on its own (that is how I have always used it ) or a FQDN. As @jzawacki mentioned above, the docker has no method to support changing the port so any attempt to change the port to a non default one will not work. The docker has to run on the default port, regardless of if that is convenient for you or not.

[saarg 413]

22 hours ago, jzawacki said:

Apologies if this has been addressed, I saw notes around page 8 of others having issues using custom ports, but I couldn't find a solution.  It's unfortunate that so much of this thread is standard UniFi controller support over container support.

 

Anyway, I have been unsuccessful using custom ports for this container as well.  I have configured the docker properly, but the defaults are still used.  If I go into the container and look as the system.properties file, the port options are all commented out, so I'm not sure how the UniFi controller is supposed to know to use the custom ports.

 

Thanks,

James

You don't change the port inside the container, you change the host side. That is what port mapping is about.

 

Please supply the docker run command.