PeteAsking

I have had no issues and its working as expected.

Its received multiple fixed (this version) and people seem happy on the forums. A small subset of users are having issues with vlans and a memory leak but nobody can work out what causes the people affected to have the issue. I see the docker image is regularly updated (last update 1 day ago) for this version so this particular one seems to be the one they are working the most on and have released no new version for over 2 months now. Will do. So far Im having no issues whatsoever.

I have updated to version-6.2.26 today just fyi.

repository is set to linuxserver/unifi-controller:version-6.2.25 on my docker.

No problems, all seems to be working. As you cant provision the new devices without upgrading it seems like its just a matter of time until you will be forced to update anyway. Especially if you want that wifi 6 speeds the new equipment have. This seems like a pretty good version except for the fact you have to bounce back and forth between the classic and new interface to expose all options which is annoying. There was a video on youtube from that pfsense guy about the new version and these annoying quirks if you want to look that up but otherwise all good.

I agree you should use qcow for snapshot support. Raw might appear to work but produce a dirty copy which cant be used so you might want to verify the backup actually works rather than it just saying 'success' and assuming its ok.

There are alternative things you can to to harden this more such as locking the firewall rules down to the public IP the site connects from or if its a dynamic IP having the remote site establish a wireguard connection back to the primary site so that the inform URL can be an internal IP. If both those options are unavailable and the remote site has a dynamic ip another thing you can do is setup a dyndns service on the internet router there and then have a device on your primary network via a script write the ip of the remote site to a text file that can be imported as an alias to the firewall every 15 minutes or so so that if the IP changes the firewall rule is still locked down to an IP. This would ensure after 15 minutes that the AP's are allowed through to the firewall in case of an ip change.

Also using bridge here without issues.

I dont use this plugin but I assume if you have the disk image you just make a new vm with the exact same settings and point it to the disk. Better yet if you saved the XML from before you can just copy and paste it back and it will be identical settings already for you.

Yup so long as you never buy a wifi 6 device from them its the best. Problem is the wifi 6 devices are really good.

Yup all booted with Big Sur now, correct resolution and all working with apple services etc. 100% acceptable VM.

Just an update on this I got further by doing this on my host box : echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs And was able to boot the big sur installation media.

Same issue here as others are having. Following guide can install catalina with no issues whatsoever. If trying to use big sur then its just apple logo stuck and 1 cpu stuck seemingly doing something but actually nothing ever happens. I can even install cataline with opencore using unraid then copy over the big sur installer and make it appear in the boot menu but selecting the big sur installer does nothing and have to reset the machine and select boot from catalina instead. So it basically all works perfect up till the moment big sur is involved then all falls apart. If you try upgrade the catalina install to big sure via any method the same thing happens so it cant get upgraded either.

I updated to 6.2.25 also on the weekend. It seems actually a good version. I have had no issues and you can close the advert these days also. My switch firmware is 5.43.36.12724 and the AP's are now 5.43.36.12724 so unifi have internally made the version numbers the same even though they are 2 different firmware files and sizes. Im sure this wont cause any confusion and be overlooked by anyone at some point in the future. Despite this it is all working so guess this version is good to go. Pete

Ok this weekend Im going to do it then. If it breaks Im holding you guys accountable.

I see on the forums not many people are having issues with this one so maybe its ok? If you guys say you dont have any issues I might try it in a couple days time. P

Keep us posted in 3 days time.

Who is being nominated by everyone here to test tag version-6.2.25 from the unifi docker repo? One of you has to do it I did it last time.

Nobody holds out any hope from unifi. Welcome to the club. if it works great. if not, try different versions and be miserable like the rest of us. Nobody here can change the state of affairs over at ubiquity. We all just have to struggle on together.

As unifi provide the docker image, its up to you to go to the unifi forums and ask them what the error means.

Set a tag in the docker eg: linuxserver/unifi-controller:version-6.1.71 Tags can be found from here: https://hub.docker.com/r/linuxserver/unifi-controller/tags?page=1&ordering=last_updated

Maybe check with the guys over on the unifi forum?

pay = convenient and easy. free = same thing but not easy and you do a lot of work. Take your pick. Companies charge money for value add. Thats why windows server is not free.

Ubuntu server.

I updated to the latest switch firmware and everything still works. RE the inform URL - that has always fixed it for everyone before so no clue what you did wrong.