Jump to content
linuxserver.io

[Support] Linuxserver.io - Unifi-Controller

379 posts in this topic Last Reply

Recommended Posts

linuxserver_medium.thumb.png.255361fdeeef210c2e81ffbe3d7a9a18.png

Application Name: Unifi-Controller

Application Site: https://www.ui.com/software/

Docker Hub: https://hub.docker.com/r/linuxserver/unifi-controller/

Github: https://github.com/linuxserver/docker-unifi-controller/

 

Please post any questions/issues relating to this docker you have in this thread.

 

If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Edited by linuxserver.io

Share this post


Link to post

This container is a drop in replacement for our previous Unifi container. 

 

We have taken the decision to produce a new container rather than update our old container to mitigate the fact that there is a massive change in what version you will be pulling if you use the latest tag.  Our new container allows the use of the following branches.

 

Warning! The latest tag may be broken or buggy (and often is!)

latest - The most recent build version of the Unifi controller software, regardless of release train.

LTS - The most recent Long Term Support release.

5.9 - The most recent 5.9.x release.

5.8 - The most recent 5.8.x release.

5.7 - The most recent 5.7.x release.

 

In our previous container, latest would pull the most recent LTS release, so if you wish to ensure continued stability, you should choose to use the LTS branch of this container.

 

The appdata is fully compatible with your old appdata, however if migrating from our old container and you wish to use your existing appdata then please note you will need to manually select your old unifi appdata folder. 

As always you should ensure you have backups before migrating.

(Regular backups of appdata being recommended general maintenance in any case)

 

This is completely by design, to ensure no inadvertent overwriting and massive version hopping which would be the outcome if we had decided to modify our previous container.

 

Before you attempt to migrate, ensure the old unifi container has been stopped/removed.

 

To select your old appdata folder, first click Show more settings2019-02-17_23-13.thumb.png.998e25ce4dce87b2e1f1ed73f1af3bec.png

 

Click in the appdata box.

 

2019-02-17_23-15.thumb.png.1a8f018016f37ccbed896be90224b83c.png

 

Go up a folder level by clicking in the box shown below.

 

2019-02-17_23-16.png.02b1377858fe644d43006a0114e2e0eb.png

 

Finally select your old appdata folder.  (Reminder, make sure you've made a backup)

 

2019-02-17_23-16_1.png.73107e44a4859edfa5b0b00a21714d82.png

Edited by linuxserver.io

Share this post


Link to post
22 minutes ago, wgstarks said:

I was just about to ask.😏

2019-02-18_00-12.png.4db0525fddb96ac7e16717236ce3e03a.png

 

Have at it.....

Share this post


Link to post

Eazzy Pezzy

There wasn't any mention of shutting down the old docker before installing the new one, but it seemed like the safe thing to do. Don't know if it's necessary or not, but didn't want to find out.

Share this post


Link to post
55 minutes ago, wgstarks said:

Eazzy Pezzy

There wasn't any mention of shutting down the old docker before installing the new one, but it seemed like the safe thing to do. Don't know if it's necessary or not, but didn't want to find out.

Well if you don't shut it down you can't start the new container as all the ports are still in use.....

I thought that would be obvious, but I'll add it to the notes above..

Share this post


Link to post

First thanks for the update much appreciated.

 

I noticed that port 10001 is set to TCP should it not be UDP?

 

Also, I have this error when trying to connect the controller from my external host name? It was working be for and if I stop the new controller and fire up the old controller it connects just fine any ideas where to look?

 

502 Bad Gateway

nginx/1.14.2

 

Thanks,

Dean

Share this post


Link to post

Very smooth transition.  Thanks for another great docker container.  This should please EVERYBODY as far as the supported controller releases goes.

 

I stayed on the 5.9 branch given that it works for me and there have been 7-8 releases to "stable/stable candidate" in the last 10 days in the 5.10 (latest) branch.  Doesn't sound too stable to me and there are still too many complaints in the support forums.

 

The flexibility in selecting the desired branch is really appreciated.

Share this post


Link to post
2 hours ago, dolivas27 said:

I noticed that port 10001 is set to TCP should it not be UDP?

 

I believe that is correct, it should be UDP and I manually changed it before adding this new container.

 

LSIO, this is some great work.  You guys are killers.  I too am sticking with 5.9.x as 5.10.x looks like a $hit show thus far.

Edited by IamSpartacus

Share this post


Link to post
2 hours ago, dolivas27 said:

First thanks for the update much appreciated.

 

I noticed that port 10001 is set to TCP should it not be UDP?

 

Also, I have this error when trying to connect the controller from my external host name? It was working be for and if I stop the new controller and fire up the old controller it connects just fine any ideas where to look?

 

502 Bad Gateway

nginx/1.14.2

 

Thanks,

Dean

Ok I figured it out I needed to change the server name in the letsencrypt proxy-config file. 

 

Everything is now working the way it was.

 

I am still getting this error when I log in to the controller through the proxy, I am sure it’s not the container.

If anyone could lead me in the right direct to solve the problem, I would appreciate it.

 

This is the error that always pops up on the controller while I connected remotely.

WebSocket connection error

 

This is what the console in chrome shows for the error, but I am not sure on what to look at?

WebSocket connection to 'wss://***.*****.com/wss/s/default/events' failed: Error during WebSocket handshake: Unexpected response code: 400

O.open @ components.v5.10.17.1.js:167

 

I blocked out the address it does not show ***.*****.com but the correct address.

 

Thanks for the help,

Dean

Share this post


Link to post

Excellent job LSIO guys. Installed the new version without a hitch. Very pleased with your work 🙂

Share this post


Link to post

First of all thanks for that container. I'am currently running the old version with the unstable tag in the docker settings and never had any issues so far.

linuxserver/unifi:unstable

The controller software shows the following version:

unifi.png.e5cdb8e8a88c3c38c2b5cc3623a42fbb.png

It showed me the last couple days a newer version 5.10 is available for download. Here is my question. If i switch to "latest" in the new container, does that mean it switches to 5.10 and btw which is the the latest LTS version? It's kinda confusing all these different version UBNT provides. Or is the better way to create the new container and set it to 5.9 first? Will it stay on 5.9 or will it also hint me for an update to 5.10? Questions questions questions. Don't know where to start 🤔

 

1. step: appdata already backed up

 

 

Share this post


Link to post
First thanks for the update much appreciated.
 
I noticed that port 10001 is set to TCP should it not be UDP?
 
Also, I have this error when trying to connect the controller from my external host name? It was working be for and if I stop the new controller and fire up the old controller it connects just fine any ideas where to look?
 
502 Bad Gateway
nginx/1.14.2
 
Thanks,
Dean
Yep, my fault have changed the template to UDP now.

Reverse proxy config for our letsencrypt will need changing and I've already submitted a PR for that. It's based on container name so change of name is what is causing the issue.

Alternatively rename this container unifi and it should work (all lower case)

Sent from my Mi A1 using Tapatalk

Share this post


Link to post
First of all thanks for that container. I'am currently running the old version with the unstable tag in the docker settings and never had any issues so far.
linuxserver/unifi:unstable

The controller software shows the following version:
unifi.png.e5cdb8e8a88c3c38c2b5cc3623a42fbb.png
It showed me the last couple days a newer version 5.10 is available for download. Here is my question. If i switch to "latest" in the new container, does that mean it switches to 5.10 and btw which is the the latest LTS version? It's kinda confusing all these different version UBNT provides. Or is the better way to create the new container and set it to 5.9 first? Will it stay on 5.9 or will it also hint me for an update to 5.10? Questions questions questions. Don't know where to start 
 
1. step: appdata already backed up
 
 

Latest is currently on 5.10.x

LTS is currently on 5.6.x

Personally in your position, I would stick to 5.9.x

Sent from my Mi A1 using Tapatalk

Share this post


Link to post

Since it's not explicitly mentioned, is it recommended for all users of the old app to now migrate to the new one?  

Is the old app now deprecated?

Share this post


Link to post

As always guys, thanks for what you do!

 

This was a super quick/easy transition for me. Just pointed to the same appdata and my reverse proxy I had setup still worked, no issues so far on everything. 

 

I had way more ports mapped on my OLD container for some reason, but I'm not sure what they were honestly even all doing. 

Attached here just incase, but I didn't re-create them, just left the defaults in the new template alone and all seems good.

2019-02-18 09_44_52-Server_Docker.png

Share this post


Link to post
3 hours ago, dockerPolice said:

Since it's not explicitly mentioned, is it recommended for all users of the old app to now migrate to the new one?  

Is the old app now deprecated?

Yes Sir.

Share this post


Link to post
6 hours ago, bastl said:

If i switch to "latest" in the new container, does that mean it switches to 5.10 and btw which is the the latest LTS version? It's kinda confusing all these different version UBNT provides. Or is the better way to create the new container and set it to 5.9 first? Will it stay on 5.9 or will it also hint me for an update to 5.10?

If you install the 5.9.x branch of this container, inside the controller it will still prompt you to update to 5.10.17.  You should not update from within the controller.  Do it through the docker container by changing the tag from 5.9 to latest.  Latest is on 5.10.x branch.  However, I would not do that if I were you.  5.10.x is really buggy according to the Ubiquiti forums. Of course, it is your choice.

 

Share this post


Link to post
6 hours ago, CHBMB said:

Latest is currently on 5.10.x

LTS is currently on 5.6.x

Personally in your position, I would stick to 5.9.x

 

34 minutes ago, Hoopster said:

If you install the 5.9.x branch of this container, inside the controller it will still prompt you to update to 5.10.17.  You should not update from within the controller.  Do it through the docker container by changing the tag from 5.9 to latest.  Latest is on 5.10.x branch.  However, I would not do that if I were you.  5.10.x is really buggy according to the Ubiquiti forums. Of course, it is your choice.

Thank you guys for the answer. I couldn't really wait for an answer. I'am on bleeding edge right now, as always. I used the "latest flag" with the old appdata and so far no errors, except of some in the Docker logs @linuxserver.io

 

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 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request

 

Share this post


Link to post
8 hours ago, CorneliousJD said:

As always guys, thanks for what you do!

 

This was a super quick/easy transition for me. Just pointed to the same appdata and my reverse proxy I had setup still worked, no issues so far on everything. 

 

I had way more ports mapped on my OLD container for some reason, but I'm not sure what they were honestly even all doing. 

Attached here just incase, but I didn't re-create them, just left the defaults in the new template alone and all seems good.

2019-02-18 09_44_52-Server_Docker.png

I mapped the ports according to the info here.

https://help.ubnt.com/hc/en-us/articles/218506997-UniFi-Ports-Used

 

I left out 6789, 27117 & 5656-5699 as they are require for mobile speed test, local bound database & EDU products respectively.

Share this post


Link to post
19 hours ago, bastl said:

 

Thank you guys for the answer. I couldn't really wait for an answer. I'am on bleeding edge right now, as always. I used the "latest flag" with the old appdata and so far no errors, except of some in the Docker logs @linuxserver.io

 


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 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused (Connection refused)
Feb 18, 2019 1:34:44 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request

 

I'm getting the same error in my log. I looked at the server log and it's showing an error connecting to the DB server. Any ideas?

Share this post


Link to post

I was having adoption issues when i changed to this docker and then i remembered i had the same problem before after an upgrade and i had to change the docker to "host" from "bridge".

 

Restarted the docker and it has picked up all my devices. 

 

Might help someone if they have the same issue of devices stuck in an "adopting" loop.

Share this post


Link to post
14 minutes ago, Ockingshay said:

I was having adoption issues when i changed to this docker and then i remembered i had the same problem before after an upgrade and i had to change the docker to "host" from "bridge".

 

All my devices, after being connected in the controller after the container update, entered a disconnected/adopting loop last night and had been there for several hours when I noticed it this morning.  I fixed it by connecting via SSH to each device and manually setting the inform host.  All devices instantly became connected.

 

Setting the container to host (and back to bridge after the adoption) also seems to work if you are stuck in an adopting loop.  That is what I did when I first installed the old container and is certainly the easier way to address the issue.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.