9 minutes ago, Samson said:

Hi,  Noticed that you have the Unifi AC Pro. Did you update to 5.10? Any Issues?  The post at the top of this page complains of adoption issues. Wondering if you have the same.

Err, my entire post was about adoption issues. and the fact that mine was a fresh install of 5.10, not an upgrade. So yes I had an adoption problem but this was due to firmware not updating, if that was a 5.10 issue or not I have no idea.

Is there a recommended stable firmware for the AP to pair with the 5.9 controller?  I am still on the LTS (5.6.40) controller with older firmware for the APs because I can't afford to have downtime for my customers.

 

I would like to switch to the new Unifi docker app and maybe install the 5.9 controller at the same time.  Then slowly upgrade the remote APs to the firmware that works best with the 5.9 controller.

9 minutes ago, mifronte said:

Is there a recommended stable firmware for the AP to pair with the 5.9 controller?  I am still on the LTS (5.6.40) controller with older firmware for the APs because I can't afford to have downtime for my customers.

 

I would like to switch to the new Unifi docker app and maybe install the 5.9 controller at the same time.  Then slowly upgrade the remote APs to the firmware that works best with the 5.9 controller.

3.9.42 is the recommended minimum AP firmware for the 5.9.29 controller according to Ubiquiti.  With the 5.9.29 controller, I am currently running 4.0.21 firmware on the APs and switches and 4.4.36 (both the latest available) on the USG.

 

See this page. 

48 minutes ago, Hoopster said:

3.9.42 is the recommended minimum AP firmware for the 5.9.29 controller according to Ubiquiti.  With the 5.9.29 controller, I am currently running 4.0.21 firmware on the APs and switches and 4.4.36 (both the latest available) on the USG.

 

See this page. 

Thanks Hoopster.  Do you know if the recommended step is to update the controller first and then the APs or update the APs first then the controller?

10 minutes ago, mifronte said:

Thanks Hoopster.  Do you know if the recommended step is to update the controller first and then the APs or update the APs first then the controller?

I am not sure if there is a recommendation as to which to do first.  I believe my APs/switches had already been updated to 3.9.42 while on the 5.8 branch so the controller update came after the firmware update.  Since then, the firmware on all devices has been updated two or three times without any issues until they are now at the latest.

Having an issue when i move the docker to Custom: Br0 due to having conflicts with host mode. When i change to Br0 custom, i get this error. Things seems to be working at first glance tho

 

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] done.
[services.d] starting services
[services.d] done.
Feb 25, 2019 9:15:56 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 25, 2019 9:15:56 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Feb 25, 2019 9:15:56 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 25, 2019 9:15:56 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Feb 25, 2019 9:15:56 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 25, 2019 9:15:56 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request

 

Another issue I just found is when I add UDP 1900 as a port it does not show up.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='unifi-controller' --net='br0' --ip='192.168.0.101' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/Halifax" -e HOST_OS="Unraid" -e 'UDP_PORT_3478'='3478' -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8443'='8443' -e 'TCP_PORT_8880'='8880' -e 'TCP_PORT_8843'='8843' -e 'UDP_PORT_10001'='10001' -e 'TCP_PORT_6789'='6789' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/unifi-controller':'/config':'rw' 'linuxserver/unifi-controller:latest' 

bdccaa76c7e239f12a4706a4b823c61b8c429cd08ede539bc77b459af80b27f3

The command finished successfully!

I don't know if the issue is with the container, but, it is the only thing that has changed recently with my UniFi network.

 

Every couple of days ALL of my devices go into the disconnected/adopting loop.  It is guaranteed to happen if I reboot the server for an unRAID update (currently on 6.7.0 rc5); at least it has both times I have updated OS since moving to this container.   I either have to manually run set-inform or change the container to host (maybe I will leave it there) to get the devices to be readopted.

 

I am still running the same version of UniFI (5.9.29) and the same firmware (the latest on all devices) as I was with the prior container with which I never had these issues through many updates.  Again, I don't necessarily know why it would be the container as I do not see other reports of repeating adoption issues, but, it is the only change on my UniFi network, so, I am starting there.

 

If the answer is "it is NOT the container and something else is broken", can you point me at what that might be?

 

Latest server log attached

 

Here's the docker run command:

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='unifi-controller' --net='host' --log-opt max-size='100m' --log-opt max-file='2' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'UDP_PORT_3478'='3478' -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8443'='8443' -e 'TCP_PORT_8880'='8880' -e 'TCP_PORT_8843'='8843' -e 'UDP_PORT_10001'='10001' -e 'UDP_PORT_1900'='1900' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/unifi/':'/config':'rw,slave' 'linuxserver/unifi-controller:5.9'

 

server.log

5 hours ago, Hoopster said:

I don't know if the issue is with the container, but, it is the only thing that has changed recently with my UniFi network.

 

Every couple of days ALL of my devices go into the disconnected/adopting loop.  It is guaranteed to happen if I reboot the server for an unRAID update (currently on 6.7.0 rc5); at least it has both times I have updated OS since moving to this container.   I either have to manually run set-inform or change the container to host (maybe I will leave it there) to get the devices to be readopted.

 

I am still running the same version of UniFI (5.9.29) and the same firmware (the latest on all devices) as I was with the prior container with which I never had these issues through many updates.  Again, I don't necessarily know why it would be the container as I do not see other reports of repeating adoption issues, but, it is the only change on my UniFi network, so, I am starting there.

 

If the answer is "it is NOT the container and something else is broken", can you point me at what that might be?

 

Latest server log attached

 

Here's the docker run command:

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='unifi-controller' --net='host' --log-opt max-size='100m' --log-opt max-file='2' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'UDP_PORT_3478'='3478' -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8443'='8443' -e 'TCP_PORT_8880'='8880' -e 'TCP_PORT_8843'='8843' -e 'UDP_PORT_10001'='10001' -e 'UDP_PORT_1900'='1900' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/unifi/':'/config':'rw,slave' 'linuxserver/unifi-controller:5.9'

 

server.log

Can you try turning on L2 adoption in the UniFi controller. When I was on host mode I was having this problem and after turning on L2 adoption everything fixed itself. 

 

Obviously you need the two ports 1900 and 10001 which I see you have.  

 

Let me know if this works for you

18 minutes ago, rcmpayne said:

Can you try turning on L2 adoption in the UniFi controller. When I was on host mode I was having this problem and after turning on L2 adoption everything fixed itself. 

The L2 discoverability option is and always has been selected.  I don't have the 'Override inform host with controller hostname/IP' option selected, but, I have never needed it through many controller version.  All devices have had the inform host set explicitly through SSH.

im on 5.9.29 or the 5.9.x release, and the docker image is showing an update.

is this correct?

im on 5.9.29 or the 5.9.x release, and the docker image is showing an update.

is this correct?

Yes, but it is likely not a controller update. LSIO update their images every Friday with any upstream updates related to the Linux distro and other things that may not have anything to do with the actual application.

Sometimes there is an application update as well, but it is not likely in this case unless Ubiquiti has updated the 5.9.x branch.


Sent from my iPhone using Tapatalk

38 minutes ago, Hoopster said:

Yes, but it is likely not a controller update. LSIO update their images every Friday with any upstream updates related to the Linux distro and other things that may not have anything to do with the actual application.

Sometimes there is an application update as well, but it is not likely in this case unless Ubiquiti has updated the 5.9.x branch.


Sent from my iPhone using Tapatalk

 

We are not updating every Friday anymore as we changed to building on changes in upstream projects or OS or dependencies updated. 

2 minutes ago, saarg said:

 

We are not updating every Friday anymore as we changed to building on changes in upstream projects or OS or dependencies updated. 

Is this just with the new Unifi docker?

3 minutes ago, wgstarks said:

Is this just with the new Unifi docker?

It's for all containers. 

Thanks for the replies!

Hi all!

Has anyone come across this before?

Had to do the set-inform thing from the command line on two of my APs, but aside from that, the changeover to the new container seems to have gone reasonably smoothly.

how do i let it autostart?

i dont see any options in the settings menu of the app

2 hours ago, skank said:

how do i let it autostart?

i dont see any options in the settings menu of the app

You autostart the docker.

19 minutes ago, wgstarks said:

You autostart the docker.

thx

sorry silly of me

On 2/26/2019 at 11:20 AM, Hoopster said:

I don't know if the issue is with the container, but, it is the only thing that has changed recently with my UniFi network.

 

Every couple of days ALL of my devices go into the disconnected/adopting loop.  It is guaranteed to happen if I reboot the server for an unRAID update (currently on 6.7.0 rc5); at least it has both times I have updated OS since moving to this container.   I either have to manually run set-inform or change the container to host (maybe I will leave it there) to get the devices to be readopted.

 

I am still running the same version of UniFI (5.9.29) and the same firmware (the latest on all devices) as I was with the prior container with which I never had these issues through many updates.  Again, I don't necessarily know why it would be the container as I do not see other reports of repeating adoption issues, but, it is the only change on my UniFi network, so, I am starting there.

 

If the answer is "it is NOT the container and something else is broken", can you point me at what that might be?

 

Latest server log attached

 

Here's the docker run command:

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='unifi-controller' --net='host' --log-opt max-size='100m' --log-opt max-file='2' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'UDP_PORT_3478'='3478' -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8443'='8443' -e 'TCP_PORT_8880'='8880' -e 'TCP_PORT_8843'='8843' -e 'UDP_PORT_10001'='10001' -e 'UDP_PORT_1900'='1900' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/unifi/':'/config':'rw,slave' 'linuxserver/unifi-controller:5.9'

 

server.log

 

I have the exact same issue after switching to the new container (using the 5.9 branch).  Did you ever find a solution?

 
I have the exact same issue after switching to the new container (using the 5.9 branch).  Did you ever find a solution?

I have not rebooted since posting but I have changed the container to host mode and left it there. Since doing so, the devices have not entered the disconnected/adopting loop.

Time will tell if that is the “fix.”


Sent from my iPhone using Tapatalk

19 minutes ago, Hoopster said:

Time will tell if that is the “fix.”

I have Unifi running on a custom network (br1) and set a fixed IP address, never experienced disconnected or adopting devices after a Unraid upgrade.

It is working very stable for me.

I have Unifi running on a custom network (br1) and set a fixed IP address, never experienced disconnected or adopting devices after a Unraid upgrade.
It is working very stable for me.

Same for me with the prior UniFi container; never an issue. On my network, this newer UniFi container seems to want to be in host mode or it enters a disconnected/adopting loop every few days and floods the logs.

The only change was the container but I am not sure if it really has anything to do with the container.

Perhaps I will try a custom IP on my docker VLAN just for grins.


Sent from my iPhone using Tapatalk