On 10/30/2019 at 10:43 PM, bdillahu said:

 

I tried changing appdata to cache - no change.

 

I was using br0 with a static IP... changed to Bridge mode and can get to it on http, not https... scratch that, I lied... I can get on https... as long as I'm on bridge

 

Seems to still be something with network side, I think.

I'm sorry to drag this back up... I left it for a while, thinking somebody with more skills than me might encounter it and maybe fix it, but apparently I'm "special" 🙂

 

When I have wireguard enabled, then I can't access my Unifi Controller docker (on br0) - don't have to be connected via Wireguard - it just has to be enabled.

 

I turn it off and everything works great.

 

Wireguard works fine when enabled, except for killing this one connection.

 

I don't know how to debug it further... any thoughts?

 

Appreciate it.

I'm sorry to drag this back up... I left it for a while, thinking somebody with more skills than me might encounter it and maybe fix it, but apparently I'm "special" [emoji846]
 
When I have wireguard enabled, then I can't access my Unifi Controller docker (on br0) - don't have to be connected via Wireguard - it just has to be enabled.
 
I turn it off and everything works great.
 
Wireguard works fine when enabled, except for killing this one connection.
 
I don't know how to debug it further... any thoughts?
 
Appreciate it.

Might be worth checking your wireguard config.

I've got WireGuard set up on both Unraid and my firewall (Opnsense) and can access Unifi just fine, however a couple of times when I've misconfigured it I've managed to take out my whole network.

Sent from my Mi A1 using Tapatalk

On 12/8/2019 at 2:50 PM, CHBMB said:

Might be worth checking your wireguard config.

I've got WireGuard set up on both Unraid and my firewall (Opnsense) and can access Unifi just fine, however a couple of times when I've misconfigured it I've managed to take out my whole network.

Sent from my Mi A1 using Tapatalk
 

Hey, thanks for the idea... I went back through things and sure enough...

 

If you actually read the help (:-))

 

"Local server uses NAT"


"When NAT is enabled, the server uses its own LAN address when forwarding traffic from the tunnel to other devices in the LAN network. Use this setting when no router modifications are desired, but this approach doesn't work with Docker containers using custom IP addressess.


When NAT is disabled, the server uses the WireGuard tunnel address when forwarding traffic. In this case it is required that the default gateway (router) has a static route configured to refer tunnel address back to the server."

 

I had it turned on... turned it off, configured the recommended static route on my router and things seem happy.

I am suddenly unable to login to the UniFi controller using my username and password.  When I click the password reset link I never get an email.  I can log in through the UniFi app on my phone, but the same credentials don't work for the docker. Any help would getting back into my controller would be greatly appreciated! I can also connect through the cloud access page...

Edited December 11, 20196 yr by amb5014

After upgrading to Unraid 6.8 the controller suddenly doesn't work. It appears to start up just fine but I can't access the controller using an IP or via the cloud. The container logs look fine too.

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


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.

 

1 hour ago, yippy3000 said:

After upgrading to Unraid 6.8 the controller suddenly doesn't work. It appears to start up just fine but I can't access the controller using an IP or via the cloud. The container logs look fine too.

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


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.

 

Seems like it was a corrupt DB. Don't know if it was related to the upgrade or not but the mongo DB got corrupt and restoring the app data folder from a backup fixed it.

On 12/11/2019 at 2:39 PM, yippy3000 said:

Seems like it was a corrupt DB. Don't know if it was related to the upgrade or not but the mongo DB got corrupt and restoring the app data folder from a backup fixed it.

I have the same issue but a restore did not resolve it.

13 hours ago, surfshack66 said:

I have the same issue but a restore did not resolve it.

Same here. I have reinstalled docker and it's ok but it's a pain to reinstall since I'm afraid I'll experience provisioning problems or something similar. I'm kind of afraid to reboot my USG now.

Although I was surprised to see that my custom jsons transfered over.

 

Edit: Oh thank god! At least the restore function works like a miracle. Created a new docker, restored the backup and everything is back up without any problems. Now onto setting up Wireguard (which is why I have noticed that Unifi is dead).

Edited December 13, 20196 yr by gxs

1 hour ago, gxs said:

Same here. I have reinstalled docker and it's ok but it's a pain to reinstall since I'm afraid I'll experience provisioning problems or something similar. I'm kind of afraid to reboot my USG now.

Although I was surprised to see that my custom jsons transfered over.

 

Edit: Oh thank god! At least the restore function works like a miracle. Created a new docker, restored the backup and everything is back up without any problems. Now onto setting up Wireguard (which is why I have noticed that Unifi is dead).

That seems to have worked for me as well. Deleted the container. Resintallated with defaults. During setup..restored from backup config (which was in a backup of the appdata folder)

Just a quick reply on my experience with the Adoption loop. Docker installed fine and started fine in bridge mode (I had to change the communication port to 8083 since I was already using 8080 for something else). Tried to adopt APs but just kept looping. Tried to change to host mode but it would always revert to using port 8080 for communication (even when the run command listed 8083 or whatever I put in the config??). So I tried setting a different IP for the Unifi-Controller (same subnet). Worked like a breeze. Didn't have to override Hostname/IP on the controller or log into the APs to force inform. This may be a possible solution for those running into problems. 

 

Anyone see any issues with running it this way?

What's the latest version of controller?  I have version 5.6.40 of the docker installed and there appears to be no update available for my docker.  I just upgraded the firmware on one of my APs and this is causing me to get tons of emails as in [UniFi] Alert: UniFi-55Hill AP Generated Event.  This appears to be a known bug and requires a controller upgrade or a AP firmware downgrade.  I would prefer to do the upgrade.  Is there a new version coming soon?

 

FYI - it looks like the latest version of Unifi website for all OSes is 5.12.35.  There also appears to be a 5.6.42 version.  My unRAID OS version is a bit behind at 6.4.1

1 hour ago, wayner said:

FYI - it looks like the latest version of Unifi website for all OSes is 5.12.35.

5.12.35 is the latest version available in this LSIO UniFi container if you use the :latest tag.

 

Available tags are the following:

 

latest - The most recent build version of the 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.

 

You must be using the LTS tag as 5.6.40 is/was the current LTS version.  Support for it was supposed to end in November but, AFAIK, no other LTS version has been designated by Ubiquiti.

Is there a way to reset the password for the controller? I was making changes to my array (removed one of my two cache drives) and after resetting the array my password for the Unifi Controller doesn't work. I don't have an appdata backup (I just set it up, part of the reason why I removed one of my cache drives) of the Unifi controller container. I'm pretty new to Unraid, so any help is appreciated.

 

Thanks!

@skroonigan Make sure you type the name for the user correct. It's case sensitive admin vs Admin is different.

1 hour ago, bastl said:

@skroonigan Make sure you type the name for the user correct. It's case sensitive admin vs Admin is different.

Yeah, I def. double/triple checked my username.

9 hours ago, Hoopster said:

5.12.35 is the latest version available in this LSIO UniFi container if you use the :latest tag.

On my Docker page in unRAID it says that I am up to date.  The repository that I appear to be using is linuxserver/unifi.

 

When I go into the Unifi Controller settings that is what I see the version is 5.6.40

 

Is there any way to force an update?  Or a reinstall without losing all of my settings and config?

15 minutes ago, wayner said:

On my Docker page in unRAID it says that I am up to date.  The repository that I appear to be using is linuxserver/unifi.

 

When I go into the Unifi Controller settings that is what I see the version is 5.6.40

 

Is there any way to force an update?  Or a reinstall without losing all of my settings and config?

You must be using the LTS tag.  There is no way to update to any other version unless you change the tag.  If you want 5.12.35, you must use the "latest" tag.  5.6.40 is the most up-to-date LTS version and as long as you use that tag, you will never be able to update to any version beyond that (or whatever the latest version is in the LTS branch).

 

Post your docker run command for the UniFi container.

Edited December 18, 20196 yr by Hoopster

How do I find the docker run command?  I am trying to do this all via my phone or tablet remotely over VPN right now so it is a bit tricky.

3 minutes ago, wayner said:

How do I find the docker run command?  I am trying to do this all via my phone or tablet remotely over VPN right now so it is a bit tricky.

https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-564345

Here is my docker run command:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='unifi' --net='bridge' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -p '8080:8080/tcp' -p '8081:8081/tcp' -p '8443:8443/tcp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '3478:3478/udp' -v '/mnt/user/appdata/unifi':'/config':'rw' 'linuxserver/unifi'

I think the issue that I may be having is that I am using the old version of this docker that predates the ability to use latest, lts, etc.  I installed the docker a couple of years ago and I can't remember changing docker versions other than doing regular updates.

 

If that is the case then do I just stop the old docker, install the new docker, and point it at my old appdata folder?

18 minutes ago, wayner said:

If that is the case then do I just stop the old docker, install the new docker, and point it at my old appdata folder?

https://forums.unraid.net/topic/78060-support-linuxserverio-unifi-controller/?do=findComment&comment=722571

Just a quick note to anyone that might be going to the Ubiquiti forums for support, they don't support the controllers running in Containers and will stop offering support even if the issue is obviously not container related.  Best not mention you run the controller in a container if you go there looking for help.

Upgrading from 5.4.6 to 5.12 didn't go so well.  The Controller didn't know about any of my devices, and it seemed stuck on adopting.  So I went back to 5.4.6.

 

Maybe going from 5.4.6 to 5.12 is too much of an upgrade.  Anyone know if things would go better if I just went to 5.7 first?  And then if things look good I can go to 5.12 later, or try 5.9 as a further interim step.

3 hours ago, wayner said:

Upgrading from 5.4.6 to 5.12 didn't go so well.  The Controller didn't know about any of my devices, and it seemed stuck on adopting.  So I went back to 5.4.6.

 

Maybe going from 5.4.6 to 5.12 is too much of an upgrade.  Anyone know if things would go better if I just went to 5.7 first?  And then if things look good I can go to 5.12 later, or try 5.9 as a further interim step.

Lots of posts in this forum about the settings needed in the controller to avoid adoption/disconnect loops with this container.  It is not uncommon and easily fixed (unless you have some undiscovered issue).  It is not version related.  I had the same issue when I went from the older unifi container to this unifi-controller container and that was an upgrade from 5.6.x to 5.9.x.  Look back a page or two.