PeteAsking

Since MacOS is posix I imagine it would be fine and stable. Presumably you can leave the machine on like a server.

I personally wouldnt since you will just be migrating again at some point to what unifi want to force you to do.

Unfortunately it has not come to my attention that due to changes by Unifi, the final version this docker will support is 10.0.162. You can ready why here: https://github.com/11notes/docker-unifi/issues/34 There is no further versions you will be able to upgrade to using this docker. What now? You have 2 options - either migrate to the version on this forum that keeps mongodb as a separate docker container and run 2 dockers for your Unifi deployment or migrate to what Unifi want you to use - Unifi OS Server. Since Unifi appears to be trying to abandon their network controller it makes sense to me to recommend using Unifi OS server going forward with a VM. This is what I will be doing personally, although I use proxmox over smb with unraid as a shared NAS area for my vm’s as I prefer this setup. To migrate to Unifi OS server you will need to deploy a VM on unraid or your preferred hypervisor running the server version of Ubuntu LTS Nobel or Debian Trixie. Both will work identically and you should choose the OS you have more comfort using. The vm will need a couple cpus 40gb disk and 4gb ram. However 4cpu and 8gb would certainly perform better. You may follow this guide once a vm is deployed on unraid: https://www.crosstalksolutions.com/complete-unifi-os-server-installation-on-linux-best-practices/ Im sorry this is the end, but seems like Unifi finally caught up and moving to their new preferred option is basically going to have to happen eventually like it or not. Any questions feel free to ask. Kind regards P

I have never done this and never owned a UCG gateway. You should ask on the unifi forum as how this would work is however unifi coded and expect it to work.

I looked up 7.4.156 and it was reased June 1, 2023. You guys should really try keep more up to date as unifi dont really support the network controller in that way when you get so out of date.

Yes seems reasonable. Maybe @RichJacot could try the same path.

We dont provide an upgrade path from such an old version to such a new version. You will need to trawl through the first 10 pages and create an upgrade path that goes through various versions to get to 10.

10.0.162-unraid is considered stable now. Page 1 is updated to reflect: (home) Stable: 11notes/unifi:10.0.162-unraid Old Stable: 11notes/unifi:9.5.21-unraid Old Old Stable: 11notes/unifi:8.6.9-unraid Please note if moving from v9 to v10 you need to follow the instructions on page 32. Simply changing the tag will not provide a workable move from a v9 to v10. P

Yes if you restore a backup config to a new docker then that would be fine and you can potentially stop the new one and start the old one if needed.

Depends if you use method 1 or 2.

I have the same switch and it adopts fine. Did you set the inform ip in the controller settings and ensure the usw flex has at least one port on the same network as the controller and plugged in etc so it can reach it?

Im waiting for the next version of 10. Currently its 10.0.160 released 4 December but this is needing quite a number of patches and unifi have not managed to release the next version yet as stable. Its rare for this to take 2 months so I can only assume there are lots of fixes coming. If you are not missing anything, I would just wait.

Its not windows specific and you can get a new cert in the unifi container. I feel like you are complicating a simple non issue. Just use the mobile phone app if its causing you this much grief. Their own app ignores certs.

Sure but you shouldnt be administering your network administrative controllers and firewalls from every machine in your lan. So if you have more than like 3 admin machines you probably have bigger problems to address.

I believe in your web browser you click on the security seal and there is a download certificate option in there somewhere. Maybe someone can confirm. I personally dont bother but pretty sure its something like that. Then install it and then add entry to hosts file so when you browse its address you go to matches the cert.

No as mentioned you download the unifi cert to your local machine and install it an then create a dns entry like in the hosts file as was explained. Basically when you browse to the address the cert must match and also the pc you do this from must trust the cert. Thats about it.

Google your distro. Eg: https://superuser.com/questions/54615/how-to-install-a-ca-key-self-signed-ssl-on-ubuntu

Ok! i just edited it for you.

Seems like everyone prefers method 1

I have provided 2 methods to update to version 10 on page 32. If anyone testing has any issues just post here and I will assist. Both methods are tested by me, and fully supported. If anyone else can test that would help. Let me know what method you chose to test. Method 2 is advisable for anyone who cannot experience any downtime and needs to go back to an untouched docker running a previous version if anything fails during the update.

Hi I gave you the wrong values in error. This is not critical but when you get time can you change them to: --memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100 Thats what I will be using going forward. Reason is unraid does not support the nobody group for some reason.

Pretty sure you will be fine now and back to normal. Just waiting for community apps to update so I can write up method 2 and let people test for a week or so. -P

Sorry to keep bothering you for more testing, but I believe if you stop your container it will refuse to start up again and run the webui. If that is the case can you edit the extra settings to : --memory=8G --tmpfs /unifi/log:exec,uid=1000,gid=1000 --tmpfs /unifi/run:exec,uid=1000,gid=1000 and report back? I will update the guide above if that fixes it for you.

To update to unifi 10x please follow this thread When the community apps updates from github in a few hours I will edit that post with Method 2 instructions. Both should work fine. If anyone has any issues let me know and I can assist in getting it working. P

Hi there, This actually does work, and I have got it working this way, but is this in line with unraid mentality? You could simply remove all parts of the gui and leave only "extra parameters" and expect everyone to simply add every single switch, volumes, any ports and so on via this single line. I feel there is a case for the GUI having common settings exposed otherwise why have any settings exposed at all no? However this does resolve my immediate problem so will use this method for now. Kind regards P