February 17Feb 17 40 minutes ago, PeteAsking said: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.Ouch! Thank you! I'll skim through the first pages to get an idea but I may just redo everything. It's not a huge setup.Thanks again!
February 18Feb 18 I just upgraded from the old docker container to unifi reborn and all is well. Thanks @PeteAsking for all your work on this!I went from 7.2.95 to 7.5.187 and am now trying to figure out a path to more recent versions. I skimmed through this thread and it seems like a viable upgrade path would be to 8.0.26 to 8.5.6 to 9.0.108 to 9.5.21. This is not being too aggressive and skipping too many upgrades along the way.Does this make sense to those of you with more experience at this? I guess I could always try rolling back if required.
February 18Feb 18 Author 7 minutes ago, wayner said:I just upgraded from the old docker container to unifi reborn and all is well. Thanks @PeteAsking for all your work on this!I went from 7.2.95 to 7.5.187 and am now trying to figure out a path to more recent versions. I skimmed through this thread and it seems like a viable upgrade path would be to 8.0.26 to 8.5.6 to 9.0.108 to 9.5.21. This is not being too aggressive and skipping too many upgrades along the way.Does this make sense to those of you with more experience at this? I guess I could always try rolling back if required.Yes seems reasonable. Maybe @RichJacot could try the same path.
February 18Feb 18 Author 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.
February 18Feb 18 8 minutes ago, PeteAsking said: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.this is why the recomendation to the lxc alternativeas if you want rolling lattest updates...Docker lattest won't do any good here and can brick. (what would normaly be set for the curent lattest stable..)*Somethign we can sugest and ask 11 notes if they are willling to make a docker tag and with the lattst stables chang and set teh docker tag...with the release of unfi OS for a VM I would recemd runing a debain VM and ther unfi stack there any more...https://itadon.com/blog/unifi-os-server-self-hosting/as it has to do with superviosr unifi docker stack and other where unfi wonlt let there stack run outside of podman supervisor and there weird sytem....Docker is still great for network only. and light weigh qucik contorl center sytems.
February 18Feb 18 30 minutes ago, wayner said:I just upgraded from the old docker container to unifi reborn and all is well. Thanks @PeteAsking for all your work on this!I went from 7.2.95 to 7.5.187 and am now trying to figure out a path to more recent versions. I skimmed through this thread and it seems like a viable upgrade path would be to 8.0.26 to 8.5.6 to 9.0.108 to 9.5.21. This is not being too aggressive and skipping too many upgrades along the way.Does this make sense to those of you with more experience at this? I guess I could always try rolling back if required.I migrated mid last year, looking at my backups to piece together my upgrade path:I went from 7.4.162 to 8.0.24 (last tagged release) in lsio containerfrom there I backed up and imported into unborn container running same tagthen upgraded to 9.3.43later upgraded to 9.5.21 where I current sit (still need to move to 10.x)
February 18Feb 18 So far I have gone from 7.5.187 to 8.0.26 to 8.5.6. You can see that it has to do a database conversion on some of these upgrades.It seems that it leaves behind orphaned images. What do you do to get rid of them?
February 18Feb 18 19 minutes ago, wayner said:So far I have gone from 7.5.187 to 8.0.26 to 8.5.6. You can see that it has to do a database conversion on some of these upgrades.It seems that it leaves behind orphaned images. What do you do to get rid of them?If you toggle advanced view in the top right corner of the page you’ll see the orphaned images and a check box to delete them.
February 19Feb 19 I am now 22 hours ago, wayner said:I went from 7.2.95 to 7.5.187 and am now trying to figure out a path to more recent versions. I skimmed through this thread and it seems like a viable upgrade path would be to 8.0.26 to 8.5.6 to 9.0.108 to 9.5.21. This is not being too aggressive and skipping too many upgrades along the way.I went through this path and I am now on 9.5.21. Pretty much up to date. But maybe time to upgrade my USG3P to something newer!
February 23Feb 23 I am going to be switching to a UCG gateway so I won't be using the Unifi Network Application docker container anymore.Any advice on which version on the docker container that I should be on when I migrate to the UCG device? I am on 9.5.21 right now. Should I try to install 9.5.2 on the UCG so that I am on the same versions before migrating?
February 23Feb 23 On 2/19/2026 at 7:14 PM, beanmeister said:Upgraded from 9.5.21 to 10.0.162 using method 1 on page 32 without any issues.Same. Everything went smoothly. Thank you @PeteAsking !
February 23Feb 23 Author 17 hours ago, wayner said:I am going to be switching to a UCG gateway so I won't be using the Unifi Network Application docker container anymore.Any advice on which version on the docker container that I should be on when I migrate to the UCG device? I am on 9.5.21 right now. Should I try to install 9.5.2 on the UCG so that I am on the same versions before migrating?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.
February 23Feb 23 Author 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/34There 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 regardsP
February 24Feb 24 42 minutes ago, PeteAsking said:Any questions feel free to ask.Any advice for migrating to the LSIO version and MongoDB?
February 24Feb 24 Author 21 minutes ago, wgstarks said:Any advice for migrating to the LSIO version and MongoDB? I personally wouldnt since you will just be migrating again at some point to what unifi want to force you to do.
February 24Feb 24 59 minutes ago, PeteAsking said:I personally wouldnt since you will just be migrating again at some point to what unifi want to force you to do.Thanks. My Unraid server doesn’t really have the cores or ram for VM’s but looks like unifi offers a macOS version of their OS. I might give that a shot.
February 24Feb 24 Author 16 minutes ago, wgstarks said:Thanks. My Unraid server doesn’t really have the cores or ram for VM’s but looks like unifi offers a macOS version of their OS. I might give that a shot.Since MacOS is posix I imagine it would be fine and stable. Presumably you can leave the machine on like a server.
February 24Feb 24 2 hours ago, PeteAsking said: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.I am now very glad that I decided to buy a UCG model as my new gateway rather than a UXG. Thanks for all your hard work @PeteAsking !
February 24Feb 24 2 hours ago, PeteAsking said:Unfortunately it has not come to my attention that due to changes by Unifi, the final version this docker will support is 10.0.162That really is a shame that Unifi are forcing this change. Given these changes I think it is time that I move away from self hosting to a cloud gateway. I have just ordered a UCG Fibre to get me going on that journey. Thanks @PeteAsking for keeping the dream alive so long!
February 24Feb 24 Sorry if I'm asking a dumb question but couldn't this be an "easy" docker compose to have the OS and mongodb stood up as needed? or is that you mean by, "either migrate to the version on this forum that keeps mongodb as a separate docker container and run 2 dockers for your Unifi deployment" but also, what about this, from you? https://github.com/11notes/docker-unifi-network-application sorry just a bit confused here :-;
February 24Feb 24 36 minutes ago, jumperalex said:Sorry if I'm asking a dumb question but couldn't this be an "easy" docker compose to have the OS and mongodb stood up as needed? or is that you mean by, "either migrate to the version on this forum that keeps mongodb as a separate docker container and run 2 dockers for your Unifi deployment" but also, what about this, from you? https://github.com/11notes/docker-unifi-network-application sorry just a bit confused here :-;No a dumb quesiotn but in the wrong area asking for thiis kiind of support...this is what the linux server does and can be acomplised using docker compose...https://hub.docker.com/r/linuxserver/unifi-network-applicationhttps://docs.linuxserver.io/images/docker-unifi-network-application/There is also a differnet support area onteh unraid form for this as well..and I've done what I could to assint useres wanting a CA unraid install vareint seen here:https://forums.unraid.net/topic/78060-support-linuxserverio-unifi-controller/page/56/#findComment-1326226on that supoprt fourm side... as its is issues withteh mongo db setup and its creation...the issues was users had issues seting up mongdb that was requried with the use of the compose file thuis this docker that combines them as a All in one...using the linux server docs. (even thogh this should be on that support side...here is an example compse alternative..Step 1 — Create the init script firstSave this as /mnt/user/appdata/unifi-db/init-mongo.sh on your Unraid server:#!/bin/bash if which mongosh > /dev/null 2>&1; then mongo_init_bin='mongosh' else mongo_init_bin='mongo' fi "${mongo_init_bin}" <<EOF use admin db.auth("root", "${MONGO_INITDB_ROOT_PASSWORD}") db.createUser({ user: "${MONGO_USER}", pwd: "${MONGO_PASS}", roles: [ { db: "${MONGO_DBNAME}", role: "dbOwner" }, { db: "${MONGO_DBNAME}_stat", role: "dbOwner" }, { db: "${MONGO_DBNAME}_audit", role: "dbOwner" } ] }) EOFThen make it executable: chmod +x /mnt/user/appdata/unifi-db/init-mongo.shStep 2 — The docker-compose file--- services: unifi-db: image: docker.io/mongo:7 container_name: unifi-db environment: - MONGO_INITDB_ROOT_USERNAME=root - MONGO_INITDB_ROOT_PASSWORD=yourRootPassword # change this - MONGO_USER=unifi - MONGO_PASS=yourUnifiPassword # change this - MONGO_DBNAME=unifi - MONGO_AUTHSOURCE=admin volumes: - /mnt/user/appdata/unifi-db/data:/data/db - /mnt/user/appdata/unifi-db/init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro restart: unless-stopped unifi-network-application: image: lscr.io/linuxserver/unifi-network-application:latest container_name: unifi-network-application depends_on: - unifi-db environment: - PUID=99 # Unraid's nobody user - PGID=100 # Unraid's users group - TZ=America/New_York # change to your timezone - MONGO_USER=unifi - MONGO_PASS=yourUnifiPassword # must match above - MONGO_HOST=unifi-db - MONGO_PORT=27017 - MONGO_DBNAME=unifi - MONGO_AUTHSOURCE=admin - MEM_LIMIT=1024 - MEM_STARTUP=1024 volumes: - /mnt/user/appdata/unifi-network-application:/config ports: - 8443:8443 # Web UI (https) - 3478:3478/udp # STUN - 10001:10001/udp # AP discovery - 8080:8080 # Device communication (do NOT change) - 1900:1900/udp # L2 discovery (optional) - 8843:8843 # Guest portal HTTPS (optional) - 8880:8880 # Guest portal HTTP (optional) - 6789:6789 # Mobile speed test (optional) restart: unless-stopped*THis doen't have the ui stack forthe icon nor adatianl label as i dont' want to get off suport topinc for this are...a A few Unraid-specific notes:PUID=99 / PGID=100 are Unraid's standard nobody/users — this avoids permission headaches with appdata shares.Pin MongoDB to a major version (e.g., mongo:7) — never use latest since Mongo doesn't support auto-upgrades between major versions.The init-mongo.sh only runs on the very first start with a clean /data/db. If you've already run the MongoDB container without it, you'll need to delete the data folder and start fresh.After everything is up, the UI is at https://your-unraid-ip:8443.For device adoption, go to Settings > System > Advanced and set the Inform Host to your Unraid server's IP.Please use the other support area for that setup...Thsi is the suport area for:Ultimately with teh unif capabilitet to run the consol os (which runs superviosr docker and podman...I would run teh full consoel os (In a VM) per ealier posthttps://forums.unraid.net/topic/147455-support-unifi-controller-unifi-unraid-reborn/page/35/#findComment-1608639
February 24Feb 24 Author 49 minutes ago, jumperalex said:Sorry if I'm asking a dumb question but couldn't this be an "easy" docker compose to have the OS and mongodb stood up as needed? or is that you mean by, "either migrate to the version on this forum that keeps mongodb as a separate docker container and run 2 dockers for your Unifi deployment" but also, what about this, from you? https://github.com/11notes/docker-unifi-network-application sorry just a bit confused here :-;I dont know how to run full docker compose on unraid. Seems like unraid is just single docker deployment. That link to 11notes unifi network application has no benefit over just using the one other people are using here already where you deploy a mongodb docker totally separate and then the network application after separately on unraid. There is already a forum post and videos how to do that on unraid.
February 24Feb 24 No a dumb quesiotn but in the wrong area asking for thiis kiind of support...this is what the linux server does and can be acomplised using docker compose...https://hub.docker.com/r/linuxserver/unifi-network-applicationhttps://docs.linuxserver.io/images/docker-unifi-network-application/There is also a differnet support area onteh unraid form for this as well..and I've done what I could to assint useres wanting a CA unraid install vareint seen here:https://forums.unraid.net/topic/78060-support-linuxserverio-unifi-controller/page/56/#findComment-1326226on that supoprt fourm side... as its is issues withteh mongo db setup and its creation...the issues was users had issues seting up mongdb that was requried with the use of the compose file thuis this docker that combines them as a All in one...using the linux server docs. (even thogh this should be on that support side...here is an example compse alternative..Step 1 — Create the init script firstSave this as /mnt/user/appdata/unifi-db/init-mongo.sh on your Unraid server:#!/bin/bash if which mongosh > /dev/null 2>&1; then mongo_init_bin='mongosh'else mongo_init_bin='mongo'fi"${mongo_init_bin}" <<EOF use admin db.auth("root", "${MONGO_INITDB_ROOT_PASSWORD}") db.createUser({ user: "${MONGO_USER}", pwd: "${MONGO_PASS}", roles: [ { db: "${MONGO_DBNAME}", role: "dbOwner" }, { db: "${MONGO_DBNAME}_stat", role: "dbOwner" }, { db: "${MONGO_DBNAME}_audit", role: "dbOwner" } ] }) EOFThen make it executable: chmod +x /mnt/user/appdata/unifi-db/init-mongo.shStep 2 — The docker-compose file---services: unifi-db: image: docker.io/mongo:7 container_name: unifi-db environment: - MONGO_INITDB_ROOT_USERNAME=root - MONGO_INITDB_ROOT_PASSWORD=yourRootPassword # change this - MONGO_USER=unifi - MONGO_PASS=yourUnifiPassword # change this - MONGO_DBNAME=unifi - MONGO_AUTHSOURCE=admin volumes: - /mnt/user/appdata/unifi-db/data:/data/db - /mnt/user/appdata/unifi-db/init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro restart: unless-stopped unifi-network-application: image: lscr.io/linuxserver/unifi-network-application:latest container_name: unifi-network-application depends_on: - unifi-db environment: - PUID=99 # Unraid's nobody user - PGID=100 # Unraid's users group - TZ=America/New_York # change to your timezone - MONGO_USER=unifi - MONGO_PASS=yourUnifiPassword # must match above - MONGO_HOST=unifi-db - MONGO_PORT=27017 - MONGO_DBNAME=unifi - MONGO_AUTHSOURCE=admin - MEM_LIMIT=1024 - MEM_STARTUP=1024 volumes: - /mnt/user/appdata/unifi-network-application:/config ports: - 8443:8443 # Web UI (https) - 3478:3478/udp # STUN - 10001:10001/udp # AP discovery - 8080:8080 # Device communication (do NOT change) - 1900:1900/udp # L2 discovery (optional) - 8843:8843 # Guest portal HTTPS (optional) - 8880:8880 # Guest portal HTTP (optional) - 6789:6789 # Mobile speed test (optional) restart: unless-stopped*THis doen't have the ui stack forthe icon nor adatianl label as i dont' want to get off suport topinc for this are...aA few Unraid-specific notes:PUID=99 / PGID=100 are Unraid's standard nobody/users — this avoids permission headaches with appdata shares.Pin MongoDB to a major version (e.g., mongo:7) — never use latest since Mongo doesn't support auto-upgrades between major versions.The init-mongo.sh only runs on the very first start with a clean /data/db. If you've already run the MongoDB container without it, you'll need to delete the data folder and start fresh.After everything is up, the UI is at https://your-unraid-ip:8443.For device adoption, go to Settings > System > Advanced and set the Inform Host to your Unraid server's IP.Please use the other support area for that setup...Thsi is the suport area for:Ultimately with teh unif capabilitet to run the consol os (which runs superviosr docker and podman...I would run teh full consoel os (In a VM) per ealier posthttps://forums.unraid.net/topic/147455-support-unifi-controller-unifi-unraid-reborn/page/35/#findComment-1608639Oh wow sorry, I wasn't specifically asking for support. More just replying to the idea that there's not much else to be done but, "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." I mean it isn't anyone's responsibility to keep supporting the community for free, so I wasn't asking that. Just asking out loud about what's possible and why it might/might not be.and also, I think 11notes has done exactly the docker compose concept here: https://github.com/11notes/docker-unifi-network-application or am I wrong?All of THAT said, thank YOU for taking the time to write all that; really I appreciate it!!!
February 24Feb 24 I dont know how to run full docker compose on unraid. Seems like unraid is just single docker deployment. That link to 11notes unifi network application has no benefit over just using the one other people are using here already where you deploy a mongodb docker totally separate and then the network application after separately on unraid. There is already a forum post and videos how to do that on unraid.Ah well that's fair haha. I "think" compose is actually pretty easy especially once the docker compose add-in is installed. I've been using it for Immich for a bit now with success."So do it yourself" you say.Well using immich, and knowing how to set it up from scratch were two difference things. As for the other way setting up mongo separate, I think that's the point of using compose. It packages it all in one for management, dependancies, etc etc. Immich actually runs 4 dockers! but it's all managed from a single compose file (okay and an env file).Anyway, like I said above, I'm not poking or demanding. Was just curious about the art of the possible because "yeah sure that is doable" means I wait. "Yeah naw I tried and it failed" means I really look into a VM or using my spare rpi4. Edited February 24Feb 24 by jumperalex
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.