PeteAsking

Same as the other guy above. Server is out of memory for some reason. Turn off all vms and all other dockers and try again with available resources.

put https:// first eg: https://192.168.1.38:8443

I dont know what this means, what version of unraid did you upgrade to?

Has anyone had any issues with 8.6.9-unraid? This has tested well and has few issues in the forums. This might be what we move the corporate versions to if nobody has issues.

No clue. I use opnsense as I believe it to be a superior product and enterprise ready. I cant imagine using a unifi firewall in a company setting. Sounds ridiculous to me.

No you can use that instead of you prefer to, that is totally a valid option.

Hard to say. What I do is stop the docker and make a copy of the docker folder then start it with the new tag and hope it upgrades all the way. If not you can just delete it and copy back the backed up folder and try less of a jump. Unifi dont really document this anywhere so its kind of a trial and error thing unfortunately. Sometimes you have to do an interum jump and other times you dont.

Looks like 8.1.113

Not sure but why change the old docker if you dont have to? Just try restore the backup to the new one. It may well work and not require potentially breaking your current setup. You can just turn it off and leave it alone.

You are correct it is better to use the same version, however that version was never created so the only option is, take a backup of this version. When installing the reborn container use tag 7.5.187-unraid and then perform a restore. Monitor and check that everything is working. 7.5.187-unraid was the first tag created, so the version you are using never existed for this docker. Unclear why you never moved from that tag, perhaps you can explain as the old unifi controller did have newer tags than that. I would not change anything on the working container at this time and would first try a restore as it may well work despite the versions not being identical.

The new tags for general use are available today: Current recommended Home User tag: 11notes/unifi:8.5.6-unraid "stable" Current Company/Corporate recommended tag: 11notes/unifi:8.1.127-unraid "Old Stable" Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid "Old Old Stable" Please note: a CVE exists for Old Stable and Old Old Stable. Your docker should be run in its own vlan, not accessible by general network computers, and only accessible by a trusted machine for this reason via firewall rules or some such. We are working to find a version over the coming months that will address this issue but at this time no version is determined stable or safe enough for business or critical use other than what is listed. In addition the two older versions do not support the latest unifi equipment (ie cannot adopt them) as the newer equipment requires a slightly higher version. This is being rolled up to be addressed in the same issue and we will find a version capable of achieving both these goals. P

@wgstarks I believe a better way to handle this certificate issue is to use a reverse proxy. I know there are docker reverse proxys on unraid. Im not 100% clear how you do this but traffic would work like request —-> reverse proxy on https —-> forwarded by reverse proxy to unraid. Cert would be handled by reverse proxy.

If anyone believes they are missing a critical security vulnerability after reading unifis release notes for the last 2 versions, or that they need updates within a day after unifi releases a new version of their controller please migrate to bmartino1’s LXC version. This solves the issue for everyone involved giving a rolling release version for those who want it and a delayed schedule for the rest.

Can you post a link on the unifi forum for people who require the absolute latest version at all times via LXC where you assist? Anyone unable to wait a couple months between versions can happily go that route. For people happy to wait they can stay here if they prefer. That way people can decide themselves what they want.

Because I have to support anyone with issues, you should expect there to be a lag between unifi releasing an update and it being supported here fully. Running the absolute latest is not necessary for most cases and provides little benefit over a version that had been well tested a month prior. Is the need to update simply to satisfy a need to feel current or is there some issue that can only be resolved by a later version? At any rate the latest supported tag is 8.3.32-unraid (by the way some unifi users have reported having to revert to this version - ie 2 versions back to resolve issues on their forums which should indicate to you the stability of this version being solid). 8.4.59 Introduced a regression that would break some people upgrading to 8.4.62. For this reason I did not recommend or support upgrading to 8.4.59 despite a tag being created for it (no announcement, it is a choose your own adventure tag). There are no major features since 8.3.32 - which is extremely stable - so you would need to make a case for why we should introduce potential issues for unifi users on unraid using this docker image. Otherwise waiting 3 months for a stable update is fairly normal and of no major consequence for 99.99% of users. Rest assured this unraid docker image is being maintained. This does not mean it will have update frequencies like Fortnite Battle Royale or that every release unifi create will be deemed acceptable for the standard I expect for production and support (You will note no ‘latest’ tag exists for example. This was by design). My personal preferences have been shaped by being a Debian user for 20 years and the ethos of that project which has served well. Its ready when its ready. P