wayner

I just ran a manual test and it used Teksavvy in the 6ix. My daily auotmated test are using Bell Mobility or Bell Canada in North York and Toronto, respectively.

It is now built into docker. Use network type br0

What is considered the best practice in terms of where to store backups to ensure that you don't lose them. Presumably the backups should be also stored on a drive somewhwere other than your unRAID server in case it totally dies. Do people save their backups somewhere in the cloud? To other PCs on their LAN? External hard drives?

Pretty sure it goes in \appdata\unifi\data\sites\default

So it looks like we are going to have more fun in around 15 months. Unifi just announced that a bunch or products are being EOLed. So it looks like that for controller versions that come after March 2021 you will no longer be able to configure the EOL devices, which include: UAP-Outdoor UAP-Outdoor+ UAP-Pro UAP-IW UAP (v1+v2) UAP-LR (v1+v2) UAP-AC-EDU UAP-AC-IW-PRO So we may need to keep a legacy controller version of whatever was the latest as of March 1, 2021.

I believe that ubnt/ubnt works for the devices - maybe for the docker as well?

I upgraded the container to 5.12.35 and then had to ssh into all of my devices and issue the set-inform command. But everything seems good now. Thanks for your help. p.s. My WAPs were running 4.0.15.9872 so they appeared to be above the minimum version for 5.12.35. I am in the process of updating them.

Last night after I upgraded to the new container, and things didn't go well, I rolled back to the old container with 5.4.60. I then had to do a bunch of futzing around to get the controller to re-adopt the UAPs. In some instances a reboot was enough, but on one or two others I did have to manually issue the set-inform command, and even that didn't work on one of them - I had to restore factory defaults and start over.

I saw that so I haven't mentioned on the Unifi forums that I am using unRAID. It looks like I have two options to get upgraded: 1) Jump right in and jump to 5.12.35. Then I may have to ssh into the UAPs and do a manual upgrade and potentially do some other manually stuff to get them running. 2) Install controller 5.6.4 in Windows. Then I will probably have to adopt all of the devices, upgrade them to the latest version. Then install the docker version 5.12.35 and adopt the devices into the docker version. Any feeling on which is easier? I have at least one of my UAPs with newer firmware so maybe I will do step 1 and ensure that I can get that UAP adopted and then work on the other four.

Here is the advice that I received on the Unifi forums: The problem is that there doesn't seem to be a readily available 5.6.40 version for unRAID. Perhaps I can try 5.7 and see how it goes. Worst case scenario - can I just manually upgrade the firmware on my UAPs (and USG if required) from an ssh session?

Thanks Hoopster. I did see some discussion about moving the network setting from bridge to host, I assume that is what you mean. I wasn't really in a loop you as it hadn't even adopted my devices yet.

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.

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?

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'

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.

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?

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

I am confused about the configuration of the download folder. By default it is set to /downloads. But where exactly is that folder on my unRAID server? Is it contained in one of my shares? If I wanted to change to a share that is mounted at /mnt/user/media/videos then can I just enter this into the config settings in the web UI? And does the address that I entered above make sense?

I recently updated this docker and now when I try to go to the web UI I get a 404/Not found error - nginx/1.16.1 I am using bridge mode (br0) mode with an IP of 192.168.1.240. To try to fix it I temporarily tried host mode and tried to change the Host Port 1 to 9980. I have since changed it back but this seems to have screwed up my docker start command. Here is the docker start command: (notice the 'TCP_PORT_9980'='80' command root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='rutorrent' --net='br0' --ip='192.168.1.240' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'TCP_PORT_9980'='80' -e 'TCP_PORT_51413'='51413' -e 'UDP_PORT_6881'='6881' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/media/downloads':'/downloads':'rw' -v '/mnt/user/appdata/rutorrent':'/config':'rw' 'linuxserver/rutorrent' 6c87d2509a9bf8c68bfca32fb4d9aac37fa19e6dc3f9053319fdcadae9459615 Help! edit - I "fixed" this by deleting the docker, deleting the appdata folder and reinstalling.

No soup for me either. Can someone please get rid of this guy:

And delete them using an rm command from a bash prompt?

I am a bit out of date on 6.4.1. One on my primary uses for unRAID is to act as a SageTV server so I have to ensure that the DVB edition is updated and works properly with SageTV. How do I know what other plugins are out of date. I do update the plugins but that wouldn't have helped in this instance. For all of my other plugins, other than unRAID DVB edition, the plugin version is from 2019 with the exception of Dynamix System Statistics from 2018.08.29a. When I try to update it it wants me to be on version 6.7.0rc1. Out of curiousity - how would I ever know that this Backup plugin was deprecated? Shouldn't it say that in the release notes, as in "No longer supported, move to version 2 of this plugin". If I try to delete the backups again is it still going to hang my server? Am I stuck with those files until I get rid of the drives that the files are on?

Just to clarify, here is the plugin that was installed. A Backup / Restore Appdata Part of the CA family, CA Backup / Restore Appdata will either manually or on a schedule, automatically backup your docker appdata for easy restoring in case of a cache drive failure Andrew Zawadzki 2017.10.28 up-to-date

So when I do that I see a ca.backup directory dated Nov 1 2017. Does that mean it is the old one? And what is the least risky way to bring my system back to life? Doing a reboot command in the ssh session?

Thanks trurl - I will check that out when I get home tonight.