PeteAsking

verify the gateway of the server that the docker is running on is set correctly I guess.

Good job.

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.

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

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.

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

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

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

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.

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.

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

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.

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.

It counts them regardless if you use them or not so you will be considered using 4 at this stage.

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.

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

Sorry I did not see you had altered the port for some dark reason. If you do this you break the automatic ability of the AP to get adopted and it will only ever work by ssh to the ap and doing a set-inform http://192.168.1.123:456/inform my recommendation would be to give the port the AP expects back to the unifi docker instead of having to waste time doing this.

Also, this IP, 192.168.1.123, if you have setup the docker correctly should be the same as your unraid IP. So I assume your unraid is running on 192.168.1.123.

192.168.1.123

I updated to tag 5.14.23-ls76 2 days ago, all been fine and note that this tag has not been changed for last 10 days so might be a semi ok version to tag if you want to upgrade. Will check in a week if there is any new ones or movement. P

On the forums there are a lot of complaints about 6.020 and 6.0.22 destroying networks and breaking everything including basic stuff like causing broadcast storms on the network for no reason. Probs best to avoid for now.

Also just letting you guys know that 5.14 dropped support for some very old AP's like the first gen LR AP etc, so if anyone has old devices you might want to check the comparability list (and/or stay on 5.13). I will probs upgrade to 5.14 when they stop releasing a new version every 6 days because that generally means people have stopped moaning on the forums over there (and finding problems).

Not long until people auto get this update if they have it configured that way, the UI dude said: " Hello Everyone, This release has been promoted to stable. It will show up on the repositories on a later date. ( 1 or 2 weeks after promoting stable ) Regards, Glenn R." 20 hours ago now.

Guys I have been checking out 5.14 and while it seems ok, there are quite a few changes so if you have everything working well in production like me on 5.13, you should change your tag from linuxserver/unifi-controller:latest to linuxserver/unifi-controller:5.13.32-ls71 to avoid auto updating to 5.14 when it releases in a short while. Last thing I need is some stuff going offline, so might wait for a bit to see if other people have issues before jumping to the next version.

My one is currently set as "bridge" so it gets a 172 address. The honstame/IP setting is my unraids box IP.