wayner

Sorry to be confusing. The APs that were EOL'ed 7 days ago that I own are plain UAPs. The EOL announcment was made a year ago but it just took effect 8 days ago - and that is assuming that it wasn't delayed. According to the year old EOL announcement, you will not be able to configure the obsolete hardware on Controller versions released after March 1, 2021. So I am assuming that any versions released prior to March 1, 2021, or eight days ago, should not be an issue. So unless I am interpreting this incorrectly, any software version released more than 8 days ago should support my UAPs. Looking at the release notes pages of the Unifi Community that would seem to take you up to controller version 6.0.45 - the release notes were posted "a month ago" in the Unifi Community. Therefore which software version released up to and including 6.0.45 would be the most stable? So as long as 6.0.45 is not stable, and never will be, then I guess I will stay on 5.14 until I upgrade my UAPs and I hear that there is a more stable controller version.

Why 5.11 over 5.14? Is it more stable?

Thanks folks. Anyone know the last version that is supposed to work with the older hardware? FYI - I am referring to this announcement which says: We are now past that date so presumably this means that any version that is released from this day forward will not support the old APs. I have 3 or 4 of the older UAPs that I will eventually replace, but I don't want to spend the cash right away.

Thanks Jonathan. I am back up now. There has been a lot of discussion on the stability of various versions. any quick recommendation as to which is the most stable version. I have some older UAPs which have just become unsupported. I will want to pick a version and stick with it for a while as I believe that I won't be able to upgrade my controller and continuing using those UAPs.

I tried to update my docker and I appear to have broken my Unifi docker and I need some help getting back. I am not sure what version I was running but when I look in my appdate folder autobackups they are named like this: autobackup_5.12.35_20210301_0000_1614556801716.unf When I look at the docker install it shows: 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. If I try to install 5.9 and go to the web UI I get a dialog to install the backup I get a message that I can't install this backup as it is from a newer version. Can I install version 5.12? If not then what version can I install that are after 5.12 but are stable? And can I manually specify the version in the repository name, as in linuxserver/unifi-controller:5.12 ? But when I do that it says command failed. How do I get back and what version do I move to? And how do I specify the version that I want as 5.9 works, but 5.12 does not.

Is it possible to just restore just one subdirectory of appdata? I am having issues with one docker and want to restore. My backup is a tar file that is 39.4 GB. Can I extract just the appdate\unifi folder? If so, how would I do this?

Very true, FireWire is somewhat obsolete. But it is still the most dependable way to tune channels on cable boxes that support that functionality. So it is commonly used for DVR software, like SageTV. Running SageTV in a docker under unRAID is a great solution. But this software is also fading away as linear TV becomes less popular and DVR solutions from cable companies, etc improve as does the amount of content available on-demand. I think I was the one who asked for FireWire support in DVB several years ago.

Does that mean no? And if so, are there other similar functionality not currently available?

Is there any functionality missing in this version version that was in the older DVB plugin. For example, FireWire support?

Thanks. I have neglected my unRAID system in recent years as I am only running 6.4.1 with the DVB edition and I use Firewire as it is often the best option for changing channels if it is supported by your cable box. But now I am scared to do an upgrade as I don't want to break things and it is working fine, except for the odd system crash.

Does anyone know if this plugin works for the Hauppauge HD-PVR. I have been using unRAID with the old DVB edition for years. This allowed me to use HD-PVR encoders with the SageTV docker in unRAID. It also added firewire support for channel changes. Anyone know if this still works in the new plugin?

Sorry for scaring people but I was worried as I thought CHBMB was the person behind this docker as he was the one providing support on page 1 of this thread.

Ok, thanks. I did read too much into that then. My mistake.

Maybe I read too much into this, but that occured last November when unRAID incorporated Nvidia drivers into the core OS. Here is a quote from CHBMB: (in this thread: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta35-available-r1125/?tab=comments#comment-11340&searchlight=1) And also:

I apologize if this has been dealt with elsewhere, but I read that linuxserver.io will not longer be building dockers for unRAID. Does that apply to this docker, and if it does what does that mean for the future of this docker?

Another thing to keep in mind is that in 45 days Unifi is going to EOL a bunch of their older hardware. You can continue to use the old hardware but you can't upgrade your controller version. So people may want to be cognizant of that and purposely stay on older versions of the controller. https://community.ui.com/questions/Select-UniFi-Access-Point-AP-Models-Obsoletion-Date-March-1-2021/65487283-ce9d-49f4-85b9-b6aa54659ef7

Thanks, I tried checking the cables but they seem secure. I have been error free for a few hours, early I was getting about an error every hour.

I have started getting udma crc errors for my cache drive which is a 240GB SSD. Is this anything to worry about? Searching about this error, it isn't clear if this is something you need to deal with.

I used to use the Let's Enccrypt docker but I am having trouble with swag. I have forwarded router ports 443 and 80 to my unraid server port 5443 and 5080. I am using dyndns and my url is wayner.dyndns.org. This resolves properly to my WAN IP address. In the docker config I have a domain of dyndns.org and a subdomain of wayner. I have only subdomains set to true Validation is set to http But when I start the docker I get a challenge failed for wayner.dyndns.org. To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container What am I doing wrong? Do I have to manually create a certificate? I have other ports that are forwarded and they work.

If you make this change then won't you permanently stay on that version until you change the repository field info? But I guess maybe that is ok for now. There may be folks wanting to stay on Controller versions for a while as a lot of hardware will become deprecated in March 2021, like my four UAPs, unless you stick to old controller versions. I appear to be on 5.12.35 which appears to be about a year old.

I want to install and Android version as a VM on my unRAID server so that I can install the Android app for Control4 to have a way to control my Home Automation system on my PC. Note that first I tried the Android 8.0 docker container but it was so unresponsive as to be useless. There appear to be a few options, like AndroidX86, PrimeOS and there may be others as well. There is a thread on reddit: https://www.reddit.com/r/unRAID/comments/axctkh/how_to_run_android_x86_in_vm/ But that thread is over a year old and it has some instructions that I don't understand, namely: Anyone have any advice on which OS to use and step by step instructions?

This is a bit orthogonal to the discussion, but Windows has had native support for ssh for over 2.5 years. https://www.howtogeek.com/336775/how-to-enable-and-use-windows-10s-built-in-ssh-commands/. So you can just run ssh from a command prompt, assuming that it is installed. No more need for putty. And you can install Windows Subsystem for Linux and have pretty much a fully functional distribution of Ubuntu as an application in Windows. Very useful! Install it from the Windows Store: https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6?activetab=pivot:overviewtab

I can't say that I have this issue, and I have a USG as well, but I ALWAYS have my networking equipment connected to a UPS. The USG only draws a few watts so a decent sized UPS would power it for days, even if you also plug in a modem, switch, etc. If you have a POE switch powering your WAPs then your wifi will even stay up when your house power is off. You might want to post in the Unifi forums as this issue isn't really an unRAID docker issue.

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