meep Posted June 11 Share Posted June 11 6 hours ago, PeteAsking said: The issue for him is that a UDM does not support the site export feature you used. Oh sure. This was not a response to anything, just a general interjection. Quote Link to comment
rgreen83 Posted June 12 Share Posted June 12 17 hours ago, meep said: A bit late to the party, but I found the process of migrating from old Unifi-Controller to this a little obtuse with a few speed bumps along the way. I documented my process for my future self, but it may help others. https://mediaserver8.blogspot.com/2024/06/migrating-deprecated-unifi-docker-on.html Is there an advantage to using the site export? I just did a database backup and restore to migrate and it went off without a hitch, but I do this kind of thing for work a lot too so I'm curious what the difference is. Quote Link to comment
PeteAsking Posted June 13 Author Share Posted June 13 On 6/12/2024 at 4:43 AM, rgreen83 said: Is there an advantage to using the site export? I just did a database backup and restore to migrate and it went off without a hitch, but I do this kind of thing for work a lot too so I'm curious what the difference is. Some people have found a normal restore does not work for them. Quote Link to comment
bmartino1 Posted June 15 Share Posted June 15 The problem is the udm is running unfi OS. You want to make sure your getting a backup of the network application only. Site export is a more inclusive backup maintaining other data. for My backups> https://192.168.2.4:8443/manage/default/settings/system Unfi login > Gear bottom left(Settings) > bottom of left list (System) > tabs at top (Backup): For option Backup (configuration File) Download: This opens the backup options: You should choose 30 days to help grab DB data. This File backed up from the UDM-Pro will restore to the UNIFI network application on docker... Quote Link to comment
bmartino1 Posted June 15 Share Posted June 15 (edited) When restoring this backup note the network application and version name you need to match that network version or restore to a newer version of the unifi network application. As you can see I have earlier backups I can download and restore from...: if i download it now I will get a backup for version The version should also cary in the name of the file. it is recommend to keep unifi name scheme... Note the version in the file name: So I would need to run unifi network application version 8.2.93 or newer to use the restore function in this docker with out issue. When runnign this docker see the first post and grab the corect network applicaiotn as a tag # for your docker... ATM the default template still pulls the older version for users who have not switch to keep stability. Wath your docekr tags per first post as of writing: ADVANCED/EXPERIENCED USERS QUICK INFO: Choose your own adventure tag: https://hub.docker.com/r/11notes/unifi/tags Current recommended Home User tag: 11notes/unifi:8.1.127-unraid Current Company/Corporate recommended tag: 11notes/unifi:8.1.127-unraid Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid NORMAL USERS START HERE: The important information at a glance section: --------------------------------------------------------------------------------------------------------------------------------------------------------- Development status of community app: Canary: 31/10/2023 - 04/11/2023 [COMPLETE] Alpha: 04/11/2023 - 23/11/2023 [COMPLETE] Beta: 23/11/2023 - 08/01/2024 [COMPLETE] Delta: 08/01/2024 - Stable: n/a so the repository need to become: 11notes/unifi:8.1.127-unraid As I said earlier the docker is 1 release behind for testing before release and your restore file need to be at or newer to restore... Current unifi release is 8.2.93 .... https://ui.com/download/releases/network-server Edited June 15 by bmartino1 Quote Link to comment
bmartino1 Posted June 15 Share Posted June 15 (edited) Development on this all in one docker is there but slow for this reason if you want to maintain your own. run a lxc. This is why I said earlier to run a lxc. As then, you can downland and run the latest release and restore the same as this docker does... BUT THEN YOU NEED TO CHECK IT EVERY ONCE IN A WHILE... OR Recommened: wait until PeteAsking / 11 notes finishes, then restore and move the latest release. Otherwise, you are recreating it in docker runnign the earlier release and starting fresh... Hopefully you have an older version you can download and restore... Development: https://github.com/11notes/docker-unifi In theory the next tag should be available soonish: 11notes/unifi:8.2.93 Edited June 15 by bmartino1 Quote Link to comment
PeteAsking Posted June 23 Author Share Posted June 23 Tag 8.2.93-unraid for home users is now available 3 Quote Link to comment
furian Posted June 24 Share Posted June 24 17 hours ago, PeteAsking said: Tag 8.2.93-unraid for home users is now available update ran without issues so far. Quote Link to comment
andyd Posted June 26 Share Posted June 26 (edited) Hi, Unifi Reborn is not adopting any devices even though official Unifi app is able to. I tried deleting the appdata folder and reinstalling but still the same issue. I'm not clear on this instruction... Quote Your networking should be the same if coming from an old controller or devices wont re adopt eg: ”I had my networking on the old container set to br0 and a fixed IP - it wouldn't adopt in the new world until I made that match A few months ago I did have Unifi Reborn working correctly but I believe it was on a custom network. I am now trying bridge. Does it need to be custom network? Even if I delete the app data folder? Edited June 26 by andyd Quote Link to comment
PeteAsking Posted June 26 Author Share Posted June 26 Just now, andyd said: Hi, The app is not adopting any devices even though official Unifi device is able to. I tried deleting the appdata and reinstalling but still the same issue. I'm not clear on this instruction... A few months ago I did have Unifi Reborn working correctly but I believe it was on a custom network. I am now trying bridge. Does it need to be custom network? Even if I delete the app data folder? Did you set the correct inform IP? Quote Link to comment
andyd Posted June 26 Share Posted June 26 4 minutes ago, PeteAsking said: Did you set the correct inform IP? that did it...thanks! Quote Link to comment
Oilman Posted June 30 Share Posted June 30 I just installed the unifi-controller-reborn docker after struggling with the unifi-network-application and mongodb stuff for a while. Was able to update from a back-up that included all history from the old unifi controller app docker. I followed advice to install the exact same version from which I was importing my back-up (e.g., use the "11notes/unifi:8.0.24-unraid" tag). Wish I had found this thread from the beginning. It went pretty smooth. All my devices seemed to adopt fine except one (a flex-mini switch)... it is struggling a bit. Note that I have unifi switches and WIfi access points, but do not have a Unifi router. I run Arista Untangle on my own hardware (old desktop computer, not virtualized or piggybacked on my Unraid box). Will soon migrate to OPNSense since Untangle deprecated their Home-Pro version. Just two or three quick questions: 1) how is this "reborn" version dealing with the MongoDB requirement? A separate MongoDB docker didn't appear running alongside. Is it running a "compliant" version of the unifi controller that is somehow running the Mongo DB in the background? 2) How do I upgrade to the latest version of the unifi controller software? Do I now just go in to the docker parameters and update it to a new tag such as: "11notes/unifi:8.1.127-unraid" or "11notes/unifi:8.2.93-unraid" depending on whether I want that latest/newest, or the previous stable version? 3) Will the "reborn" docker app indicate when new unifi controller versions are available? Or will I need to just periodically do what I outlined in #2 above after checking to see what the latest version # is? Thanks for the help!!! Quote Link to comment
Oilman Posted June 30 Share Posted June 30 May have answered my own questions. Regarding whether it is somehow running MongoDB in the background, I found the following out on 11note's github: "This image will provide you a rock solid1 Unifi controller with included MongoDB (no separate image needed, since its EOL (end of life) anyway)." https://github.com/11notes/docker-unifi I did go into the Docker config and change the version to: 11notes/unifi:8.2.93-unraid and it did update to that version. Quote Link to comment
PeteAsking Posted June 30 Author Share Posted June 30 (edited) 8 hours ago, Oilman said: May have answered my own questions. Regarding whether it is somehow running MongoDB in the background, I found the following out on 11note's github: "This image will provide you a rock solid1 Unifi controller with included MongoDB (no separate image needed, since its EOL (end of life) anyway)." https://github.com/11notes/docker-unifi I did go into the Docker config and change the version to: 11notes/unifi:8.2.93-unraid and it did update to that version. Good job. I do want to clarify this: “Is it running a "compliant" version of the unifi controller” No it is not running a sanctioned or compliant version of unifis expected deployment. This is an unsanctioned and unofficial option. Their deployment expects the more complex setup (.deb and native db). This was created as I personally (and some others) do not believe their suggested setup is better/more reliable and believe this is simpler and more reliable and conforms to the industry standard KISS rule. However you certainly do not need to agree and should be aware this setup is not what unifi (linuxserver?) suggest. Also note this container was created to solve an imposed problem that nobody wanted or expected when the (official?) container was suddenly deprecated. Had this never happened this container wouldnt exist. So in some ways this setup has come about by necessity and not to compete or be better than anything else. Personally I needed a solution that resolved a problem for me and its being shared here for others because it affected more people than just me, but I do want to be upfront about what you are getting. Its a creation from a bunch of unaffiliated hobbyists who are all in this together. Edited June 30 by PeteAsking 1 1 Quote Link to comment
fat Posted June 30 Share Posted June 30 20 hours ago, Oilman said: All my devices seemed to adopt fine except one (a flex-mini switch)... it is struggling a bit. These are known to have a few issues with adoption and there is a new EA FW for them that improves adoption resiliency. Reports on the EA thread are good so far so hopefully wont be too long until official release Quote Link to comment
wgstarks Posted July 4 Share Posted July 4 3 hours ago, complementary-flasher1924 said: Hello, I just installled image, every things seems working but i can't adopt a new AP (UAP AC Lite). When i click on "adopt the device", adopting appears but nothing more... stuck on adopting in orange... It's my new and first installation. Before the adopting, the AP a has IP (192.168.1.145), and i can see it on my routeur. Any idea ? I my image log : Thanks for your support.... On 6/26/2024 at 5:48 PM, PeteAsking said: Did you set the correct inform IP? This is set in the controller settings. 1 Quote Link to comment
complementary-flasher1924 Posted July 4 Share Posted July 4 It's ok now... idon't know why but after reboot... reset etc... it's ok. Quote Link to comment
vw-kombi Posted July 12 Share Posted July 12 I just wanted to post a thankyou to PeteAsking....... And likely a goodbye. This container filled a hole for me for a while this year while waiting forever for the Unifi stock to come in for Australia. I am live on my new Cloud Gateway Ultra now which has a built in controller that must be used. Your container is now stopped and moved to the bottom of the list where it will stay in the event I move back to the old USG, which is unlikely is I am also taking advantage of the extra ports in the CGU and have incorporated it fully into my HA plans this way - i.e it is a direct swap for the duplicated config on an EdgeRouterX - just switch the cables port for port and it is up and running. 1 Quote Link to comment
bmartino1 Posted July 13 Share Posted July 13 21 hours ago, vw-kombi said: I just wanted to post a thankyou to PeteAsking....... And likely a goodbye. This container filled a hole for me for a while this year while waiting forever for the Unifi stock to come in for Australia. I am live on my new Cloud Gateway Ultra now which has a built in controller that must be used. Your container is now stopped and moved to the bottom of the list where it will stay in the event I move back to the old USG, which is unlikely is I am also taking advantage of the extra ports in the CGU and have incorporated it fully into my HA plans this way - i.e it is a direct swap for the duplicated config on an EdgeRouterX - just switch the cables port for port and it is up and running. You should still be able to back up and export the container network application config to the official hardware maintaining any rules, adaptions and other previous setups in the Official Hardware. I myself am slowly saving up for a UDM-Pro-SE for unifi protect and network application needs. Quote Link to comment
PeteAsking Posted July 13 Author Share Posted July 13 You guys should just save up for a opnsense box. Its way cheaper and better anyway. 1 Quote Link to comment
vw-kombi Posted July 13 Share Posted July 13 I like the unifi 'unified' approach...... One interface to rule them all. Quote Link to comment
PeteAsking Posted July 13 Author Share Posted July 13 8 minutes ago, vw-kombi said: I like the unifi 'unified' approach...... One interface to rule them all. Yes but that quote was one of dread and warning dont forget. Quote Link to comment
bmartino1 Posted July 14 Share Posted July 14 (edited) 1 hour ago, PeteAsking said: You guys should just save up for a opnsense box. Its way cheaper and better anyway. Funny, you should say that I'm currently testing opnsense software on other hardware. Irony So why not. Having 10 years os ISP tier level 2/3 and otehr backgourd lets talk about opnsense. ATM its satisfying my needs of the experiment. Opnsense has a better IDS/IPS system built-in and in place. A Perfect implementation of DNS via (unbound/dnsmasq) and has integrated the ics dhcp with ikea fairly well. I did have to sideload and break into Freebsd quite a bit to fix some non opnsense things for my needs but it one of the better systems out there. My quick go to for something that just works is still ipfire... Lots of pros and cons with any networking/router os and systems... throw it in a VM and test it sometime... https://opnsense.org/download/ Better to follow some youtbue video to use opnsense... My 4 Major cons with opnsense atm is: Opnsense is freebsd. Was not a easy installer setup...(https://docs.opnsense.org/manual/install.html#installation-images) I would have prefered a better community or supported distro like Debian... alot of documentation is old referencing freebsd 11,12,13 its version 14 with 15 coming soon... *Con Other Personal reasons and issues with bsd / unix... more with community and unpatched CVEs... had to sideload and force a few fixes against cve that should have been default fix out of box... Opnsense will use FreeBSD packages but not maintain the actual distro packages. Hence, the side load of some common apps and other patches... *I would have ran pfSense to keep the underlying distro up to date and more secure knowing what i know now... Opnsesne doesn't have a good system for AP/Wifi...(https://docs.opnsense.org/manual/how-tos/interface_wireless_internal.html) ...https://srobb.net/fbsdquickwireless.html ... I have already submitted a few support and bug fixes... Openness doesn't have a good muti wan setup (https://docs.opnsense.org/manual/how-tos/multiwan.html) *Broken routing with muti wan fail over when it happens... https://www.tspi.at/2020/02/28/wlanethfailoverfreebsd.html --A manual assignment of the wan interface should fix that but doesn't... hence bug reports... added mimugmail(https://www.routerperformance.net/opnsense-repo/) repos to get/try os-unifi The unif 7 is stable and works. unfi 8 is a build behind and is not recommend to run to maintain current network application setups. IMHO BUT yeah... Opnsesne boxes... Sorry from similar comparison of multiple setups, installs and test, Unifi still has a leg up on them. If we are willing to talk true hardware its brocade(foundry) and MikroTik but thats ISP backend stuff. Edited July 14 by bmartino1 Quote Link to comment
PeteAsking Posted July 14 Author Share Posted July 14 22 minutes ago, bmartino1 said: Funny, you should say that I'm currently testing opnsense software on other hardware. Irony So why not. Having 10 years os ISP tier level 2/3 and otehr backgourd lets talk about opnsense. ATM its satisfying my needs of the experiment. Opnsense has a better IDS/IPS system built-in and in place. A Perfect implementation of DNS via (unbound/dnsmasq) and has integrated the ics dhcp with ikea fairly well. I did have to sideload and break into Freebsd quite a bit to fix some non opnsense things for my needs but it one of the better systems out there. My quick go to for something that just works is still ipfire... Lots of pros and cons with any networking/router os and systems... throw it in a VM and test it sometime... https://opnsense.org/download/ Better to follow some youtbue video to use opnsense... My 4 Major cons with opnsense atm is: Opnsense is freebsd. Was not a easy installer setup...(https://docs.opnsense.org/manual/install.html#installation-images) I would have prefered a better community or supported distro like Debian... alot of documentation is old referencing freebsd 11,12,13 its version 14 with 15 coming soon... *Con Other Personal reasons and issues with bsd / unix... more with community and unpatched CVEs... had to sideload and force a few fixes against cve that should have been default fix out of box... Opnsense will use FreeBSD packages but not maintain the actual distro packages. Hence, the side load of some common apps and other patches... *I would have ran pfSense to keep the underlying distro up to date and more secure knowing what i know now... Opnsesne doesn't have a good system for AP/Wifi...(https://docs.opnsense.org/manual/how-tos/interface_wireless_internal.html) ...https://srobb.net/fbsdquickwireless.html ... I have already submitted a few support and bug fixes... Openness doesn't have a good muti wan setup (https://docs.opnsense.org/manual/how-tos/multiwan.html) *Broken routing with muti wan fail over when it happens... https://www.tspi.at/2020/02/28/wlanethfailoverfreebsd.html --A manual assignment of the wan interface should fix that but doesn't... hence bug reports... added mimugmail(https://www.routerperformance.net/opnsense-repo/) repos to get/try os-unifi The unif 7 is stable and works. unfi 8 is a build behind and is not recommend to run to maintain current network application setups. IMHO BUT yeah... Opnsesne boxes... Sorry from similar comparison of multiple setups, installs and test, Unifi still has a leg up on them. If we are willing to talk true hardware its brocade(foundry) and MikroTik but thats ISP backend stuff. You should test zenarmor. Works great as layer 7 filtering. 1 Quote Link to comment
Recommended Posts
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.