31 minutes ago, danioj said:

Hi All,

 

Just upgraded to the new UniFi-network app with the standalone MongoDB instance.

 

I thought it might be a good time to put my wildcard domain cert on the controller. Honestly, I’ve spent twice as much time looking for a solution to do that than it took me to setup Mongo and migrate to the new UniFi application. 

 

There is so much aged content out there on hacks to do this. Also there seems to be a different process dependant on what UniFi device you use. Hopefully one day soon they will integrate cert management into the application itself. 

 

Has anyone managed to do this that can explain or can link me to a guide? 
 

Thanks

 

D

Unifi Support forum would be a better ask.

some of the details out there like:
https://www.namecheap.com/support/knowledgebase/article.aspx/10134/33/installing-an-ssl-certificate-on-ubiquiti-unifi/

You need to run on the physical hardware via ssh into a unfi device such as the udm pro.
The network application itself is a standalone side software. Per other communications I've had on the unifi forum

You could run some form of Json files on the docker/Linux host running the network application.

https://community.ui.com/questions/Unifi-controller-certificate-installation/913451d9-2095-43cd-9e6b-fc1a77807f87

 

https://community.ui.com/questions/UniFi-Controller-SSL-Certificate-installation/2e0bb632-bd9a-406f-b675-651e068de973

I don't see the point of adding the cert to the device nor network application. Unless this is running in the cloud and open to the World....

42 minutes ago, danioj said:

Hi All,

 

Just upgraded to the new UniFi-network app with the standalone MongoDB instance.

 

I thought it might be a good time to put my wildcard domain cert on the controller. Honestly, I’ve spent twice as much time looking for a solution to do that than it took me to setup Mongo and migrate to the new UniFi application. 

 

There is so much aged content out there on hacks to do this. Also there seems to be a different process dependant on what UniFi device you use. Hopefully one day soon they will integrate cert management into the application itself. 

 

Has anyone managed to do this that can explain or can link me to a guide? 
 

Thanks

 

D

I would honestly send you to use a LXC and run lets encrypt. and use lets encrypt for your cert...
VM! ...(with release of unfi os...)

https://community.ui.com/questions/UniFi-Installation-Scripts-or-UniFi-Easy-Update-Script-or-UniFi-Lets-Encrypt-or-UniFi-Easy-Encrypt-/ccbc7530-dd61-40a7-82ec-22b17f027776

https://glennr.nl/s/unifi-lets-encrypt

Edited November 29, 2025Nov 29 by bmartino1

The docker's context menu doesn't show 'web ui' anymore, just 'console'. Why is that?

8 hours ago, jowi said:

The docker's context menu doesn't show 'web ui' anymore, just 'console'. Why is that?

docker tab > in that menu, click edit docker.

Advance toggle>

under webUI:
 

 

https://[IP]:[PORT:8443]

 

That is already there... do i need to change it to my actual ip adress?

 

4 hours ago, jowi said:

That is already there... do i need to change it to my actual ip adress?

 

this is what sets teh web UI. the [IP] should grab the correct IP. but yes i would change it to the corect web link

example:
https://192.168.2.4:8443/manage/default/dashboard

Setting the correct IP the docker is getting.

It is weird if there is something set and not seeing the web ui option under the docekr. This tells me that that data didn't apply with the last do per edit and or change you made when making the docker.

If editing make sure you stop the docker, and hit apply to use these settings

save saves template, done leaves area...

I'm getting this error. What do I do wrong?
I followed this guide:

{"t":{"$date":"2024-08-25T06:34:58.967-07:00"},"s":"I",  "c":"ACCESS",   "id":5286307, "ctx":"conn91","msg":"Failed to authenticate","attr":{"client":"172.17.0.1:45514","isSpeculative":false,"isClusterMember":false,"mechanism":"SCRAM-SHA-1","user":"unifi","db":"admin","error":"UserNotFound: Could not find user \"unifi\" for db \"admin\"","result":11,"metrics":{"conversation_duration":{"micros":669,"summary":{"0":{"step":1,"step_total":2,"duration_micros":631}}}},"extraInfo":{}}}

On 8/25/2024 at 8:43 AM, zeganr said:

I'm getting this error. What do I do wrong?
I followed this guide:

{"t":{"$date":"2024-08-25T06:34:58.967-07:00"},"s":"I",  "c":"ACCESS",   "id":5286307, "ctx":"conn91","msg":"Failed to authenticate","attr":{"client":"172.17.0.1:45514","isSpeculative":false,"isClusterMember":false,"mechanism":"SCRAM-SHA-1","user":"unifi","db":"admin","error":"UserNotFound: Could not find user \"unifi\" for db \"admin\"","result":11,"metrics":{"conversation_duration":{"micros":669,"summary":{"0":{"step":1,"step_total":2,"duration_micros":631}}}},"extraInfo":{}}}

There are many ways to run unfi on unriad...

Take a look at the lxc repo, there I have the command that I run to setup the unifi app in  Debian/Ubuntu environment.
You can run the same sh scripts in the repo to build in your vm/lxc/etc as you desire.

scripts 01-06 should run to get you a working unfi application:
https://github.com/bmartino1/unraid-lxc-unifi/tree/main/build

Unraid also has a app store with a template that can be followed.

it appears that the video goes over the 2 docker method, the unfi app template is username and password apply once..

Please see post earlier in forum, goin over the github maintainer to accomplish this.

and
 

 

Edited August 26, 20241 yr by bmartino1

On 8/25/2024 at 8:43 AM, zeganr said:

I'm getting this error. What do I do wrong?
I followed this guide:

{"t":{"$date":"2024-08-25T06:34:58.967-07:00"},"s":"I",  "c":"ACCESS",   "id":5286307, "ctx":"conn91","msg":"Failed to authenticate","attr":{"client":"172.17.0.1:45514","isSpeculative":false,"isClusterMember":false,"mechanism":"SCRAM-SHA-1","user":"unifi","db":"admin","error":"UserNotFound: Could not find user \"unifi\" for db \"admin\"","result":11,"metrics":{"conversation_duration":{"micros":669,"summary":{"0":{"step":1,"step_total":2,"duration_micros":631}}}},"extraInfo":{}}}

Since your having issues with unifi, i would recmend you move to the all in once docker image.

 

this docekr runs unifi and makes the mongdb image with in the docekr, so no Mongo DB fuss.

be sure to read his forum and set teh repository to use the lattesting unvie controler version and check back to cahnge the repository to upgrade to the next controler version.

 

 

Time of writing the unfi controler version is: 8.3.32
repository is: 11notes/unifi:8.3.32-unraid

see post here regarding runngin a unfif version with pete asking AIO docekr:
 

Otherwise fix your mongodb docker and the linux unfi network application docker to talk to each other.
in which we would need more info then you attempt for the init js that sets and creates the mongdb.

as the copy of your log appears to show a auth issue. With out known other info its hard to assist...

I would need a picture of you 2 dockers, the docker run for both dockers, and potential the diag logs in both docker...

Edited August 26, 20241 yr by bmartino1

Hello,

 

TLDR; Just got this all set up and working but had issues with the auth source in the generated MongoDB connection string.

• I was having issues with the unify-network-application docker not authenticating with a new MongoDB install. Verified by looking at the contents of the logs in /usr/lib/unifi/logs but the logs didn't give the whole picture...
• I added the users via mongosh on the docker (not init script)
• Turns out the issue was caused by the authSource=admin param (default value) in the MongoDB connection string

Solution: removed authSource=admin from /usr/lib/unifi/data/system.properties so that it would fallback to the default auth source.

Thanks @ekim.w for calling out the location of the connection string.

 

the image temple for the MongoDB credential is applied once at first docker run it will not take a changes later in the docker edit when setting the DB file. You must delte the dokcer and image to apply it. sometimes even dletin the unifi appdata folder.

please see earlier post on this page:

or use pete asking version of the docker to have a 1 install and done then 2 separate dockers.

Edited December 11, 20241 yr by bmartino1

The issue I was having was the template was not allowing an empty value for the authSource so I had to manually remove it once the docker was running. I had read much of this thread and knew the file was created on the first docker run but did not come across a solution for a blank authSource.

for security and how it works it can't be blank thats coded in the docker image.
 

On 7/6/2024 at 9:57 PM, jademonkee said:

Unifi Cloud Gateway Ultra

Sorry for up this, but need advice. 

 

I have mikrotik router RB5009 and decided to buy Unifi 6pro AP (now I have grandstream AP and previously had Unifi U6-lite), thinking about buying Cloud Gateway Ultra, previously I had this device, I didn`t like this as the main gateway, I had a few times issues with failover function, but now planning to install after mikrotik just for managing AP and also as DHCP for all my clients at home, I love their informative dashboard and GUI overall.

 

I see here many controversial messages, some people write how great and free to have docker-unifi-network-application on Unraid, but others after some time anyway buy physical device. 

 

It is not big amount of money, but is it worth purchasing separate device or is running in docker fine?

Or maybe run in docker will be painful in long term perspective? 

That`s the question. Thanks. 

1 hour ago, d3m3zs said:

Sorry for up this, but need advice. 

 

I have mikrotik router RB5009 and decided to buy Unifi 6pro AP (now I have grandstream AP and previously had Unifi U6-lite), thinking about buying Cloud Gateway Ultra, previously I had this device, I didn`t like this as the main gateway, I had a few times issues with failover function, but now planning to install after mikrotik just for managing AP and also as DHCP for all my clients at home, I love their informative dashboard and GUI overall.

 

I see here many controversial messages, some people write how great and free to have docker-unifi-network-application on Unraid, but others after some time anyway buy physical device. 

 

It is not big amount of money, but is it worth purchasing separate device or is running in docker fine?

Or maybe run in docker will be painful in long term perspective? 

That`s the question. Thanks. 

I have only ever needed to use the docker. I have only APs and switches. For firewall I use opnsense. People use the unifi gateway to get additional features like layer 7 blocking and so on but you can do the same thing with other firewalls. If you just use their APs and switches then a docker is fine and I dont see a benefit of using a dedicated device to manage just that. 

14 minutes ago, PeteAsking said:

I have only ever needed to use the docker. I have only APs and switches. For firewall I use opnsense. People use the unifi gateway to get additional features like layer 7 blocking and so on but you can do the same thing with other firewalls. If you just use their APs and switches then a docker is fine and I dont see a benefit of using a dedicated device to manage just that. 

@d3m3zs What @PeteAsking said is true (not that he needs my validation 😀).  I have a Cloud Gateway Ultra in the network of one of my homes (the other uses this docker container).  It has a built-in controller which you must use to manage the device and, logically, should use to manage the other UniFi devices in you network as well.  If all you have to manage is Unifi APs and switches, just stick with this Docker-based UniFi Controller.  Functionally, they are virtually identical.

 

Before I bought a Cloud Gateway Ultra, my home network included the UniFi USG router.  Since it had no built-in controller, I was managing a system with 1 USG, 3 UniFi switches and 5 APs all through this Docker-based controller. This is all you need.

Edited January 21, 20251 yr by Hoopster

@PeteAsking
 @Hoopster
Thank you, going to cancel my order, tomorrow will get U6 pro and will try to adopt it.

Already setup containers, according to guide, it seems for one year nothing changed in instruction. 

It even works and recognizes my old unifi account, was able to login and saw "No Access Points Found" what expected:

 

BTW, does it have the same awesome features?

And also if containers are offline wifi will continue working? So, containers are only for setup and monitoring, but don`t affect work? 

 

Edited January 21, 20251 yr by d3m3zs

18 minutes ago, d3m3zs said:

@PeteAsking
 @Hoopster
Thank you, going to cancel my order, tomorrow will get U6 pro and will try to adopt it.

Already setup containers, according to guide, it seems for one year nothing changed in instruction. 

It even works and recognizes my old unifi account, was able to login and saw "No Access Points Found" what expected:

 

BTW, does it have the same awesome features?

And also if containers are offline wifi will continue working? So, containers are only for setup and monitoring, but don`t affect work? 

 

yep, not much has changed outside of the mongbd type you can use...

https://docs.linuxserver.io/images/docker-unifi-network-application/#setting-up-your-external-database

Yes wifi will still work without the controller. With the unifi phone app you don't need the controller. You can setup AP as standalone as well...

The controller give you other access and control features such as status, logs and other networking type configurations...

Features are dependent on the device and controller application your running to manage the device. Network v9 has some nice features...

I'm not sure if Linux IO stopped support this or not... it would be int eh log with a release note if they did...

per PeteAsking with the reborn...

a lxc exist as well...

If moving off either... I've documented a backup and restore here:

As its a mater of preference on how one want to interact with it and what is doing what where...

LXC > Cron auto scripts and updates...
LinuxIO Docker > 2 separate dockers needed (Your Own MongoDB and Linux IO unifi)
Reborn Docker > 1 Docker that installed mondb and unifi per docker tag = unifi network version.

I will galdy help where I can...

Come Feb 1st I plan to update the gihub to network v9...

Edited January 21, 20251 yr by bmartino1

@bmartino1 thank you!  11notes/unifi is a very interesting project, taking into account that it is only one container, I can setup (theoretically) on my mikrotik router, need to try, but later.

 

29 minutes ago, d3m3zs said:

@bmartino1 thank you!  11notes/unifi is a very interesting project, taking into account that it is only one container, I can setup (theoretically) on my mikrotik router, need to try, but later.

 

Yes if mikrotik can run a docker you can just use 11notes directly and not even use unraid. 

Today I received U6 Pro AP and connected it to my network via a PoE switch. My network controller automatically detected and adopted it, even without the 'Inform Host' checkbox enabled.

It worked flawlessly out of the box – incredibly smooth integration! I'm glad I canceled my UCG-Ultra order, as it appears to be unnecessary for my needs. All the necessary configurations can be easily managed within Docker.

 

Thank you all for your advice and support!

On 1/21/2025 at 5:37 PM, d3m3zs said:

Sorry for up this, but need advice. 

 

I have mikrotik router RB5009 and decided to buy Unifi 6pro AP (now I have grandstream AP and previously had Unifi U6-lite), thinking about buying Cloud Gateway Ultra, previously I had this device, I didn`t like this as the main gateway, I had a few times issues with failover function, but now planning to install after mikrotik just for managing AP and also as DHCP for all my clients at home, I love their informative dashboard and GUI overall.

 

I see here many controversial messages, some people write how great and free to have docker-unifi-network-application on Unraid, but others after some time anyway buy physical device. 

 

It is not big amount of money, but is it worth purchasing separate device or is running in docker fine?

Or maybe run in docker will be painful in long term perspective? 

That`s the question. Thanks. 

I'm happy with my Cloud Gateway Ultra. I prefer having the console built in.

I suspected that it wasn't quite as fast as my old USG (it doesn't have hardware offloading), but actually I upgraded my server last week (I'm yet to upgrade my forum sig...) and now my Usenet downloads hit the full 103MB/s that a gigabit connection can handle, so I don't actually know why they dropped when I upgraded to the CGU. Maybe just a coincidence?

 

So, yes. If you are happy with spending the money, and are interested in 'unifying' your Unifi experience, then go for it. There's no messing around with external DBs, and you know that the software has been tested on your hardware.

 

If you have any questions, feel free to ask.

My unifi controller recently began to fail to load.  Attempts to reinstall / restore using AppData backup/restore plugin have resulted in no change.

 

Attached is the container log.

 

Anyone have any suggestions before I completely reset & rebuild my network

 

First line of failure appears to be: Exception in thread "launcher" java.lang.IllegalStateException: Tomcat failed to start up

unraid-network-application_log.txt

On 10/27/2023 at 3:29 PM, wgstarks said:

 

 

This is a summary of the steps I took to migrate to LSIO's unifi-network-application docker now available in CA. The only guarantee here is that this worked for me so USE IT AT YOUR OWN RISK. If you decide to do this and have problems I'll be glad to help solve them but I am far from a docker expert.

 

NOTES

This guide is based on the readme in the Github project page. I would recommend reading that first before proceeding. I use tags for my docker versions for the Unifi dockers rather than running latest. You will see later in the summary that the tag for unifi controller was 7.3.83. This tag isn't available for unifi-network-application so I went ahead and installed the latest version currently available which is 7.5.187. Luckily it worked. I also found that the docker template is missing an entry for the webUI address so I copy/pasted the entry from the unifi controller docker. Before installing the unifi-network-application docker you should stop the unifi controller docker you already have installed. PLEASE DO NOT DELETE IT until you are sure that there aren't any issues with unifi-network-application. There's always a possibility that you may need to switch back.

 

PROCEDURE

1. Create a backup in the unifi controller application and download it to your local computer. This will be needed after the docker install is complete in order to restore the app.

2. Quote from the GitHub project page: 

   In my case I installed the official mongoDB docker available in CA and used this contents in the init-mongo.js file- 

   db.getSiblingDB("unifi").createUser({user: "unifi", pwd: "password", roles: [{role: "dbOwner", db: "unifi"}, {role: "dbOwner", db: "unifi_stat"}]});

   where MONGO_DBNAME=unifi, MONGO_USER=unifi and MONGO_PASS=password. I created a new folder named mongo_init in my appdata share and saved the init-mongo.js file there. You can store this file anywhere you prefer though.

3. Open a terminal window and create a custom docker network with the following command- 

   docker network create <network name>

   Replace <network name> with the name you would like to use. I used unifi for simplicity. You will need to use this network for MongoDB and unifi-network-application so that they can communicate with each other.

4. Go to the CA tab and search for MongoDB. You will see the official docker available in the results. 

5. Install it with the following configuration- 

   docker run
     -d
     --name='MongoDB'
     --net='unifi'
     -e TZ="America/New_York"
     -e HOST_OS="Unraid"
     -e HOST_HOSTNAME="Brunnhilde"
     -e HOST_CONTAINERNAME="MongoDB"
     -l net.unraid.docker.managed=dockerman
     -l net.unraid.docker.icon='https://raw.githubusercontent.com/jason-bean/docker-templates/master/jasonbean-repo/mongo.sh-600x600.png'
     -p '27017:27017/tcp'
     -v '/mnt/user/appdata/mongodb/':'/data/db':'rw'
     -v '/mnt/user/appdata/mongo_init/init-mongo.js':'/docker-entrypoint-initdb.d/init-mongo.js':'ro' 'mongo:4.4.25'
   628975ea8111d6f57c24177ed25533fde878d3acaf0af5f2559d173d5f6c4428
   
   The command finished successfully!

   I had to change the network to my custom unifi network and add the path for the init-mongo.js file. You will need to modify these to fit your system. You can see that I used the tag 4.4.25 for this docker. According to the UNA project page: 

6. Gon to the CA tab and search for LSIO's unifi-network-application docker. 

7. Install this docker with the following configuration: 

   docker run
     -d
     --name='unifi-network-application'
     --net='unifi'
     -e TZ="America/New_York"
     -e HOST_OS="Unraid"
     -e HOST_HOSTNAME="Brunnhilde"
     -e HOST_CONTAINERNAME="unifi-network-application"
     -e 'MONGO_USER'='unifi'
     -e 'MONGO_PASS'='password'
     -e 'MONGO_HOST'='unifi-db'
     -e 'MONGO_PORT'='27017'
     -e 'MONGO_DBNAME'='unifi'
     -e 'MEM_LIMIT'='1024'
     -e 'MEM_STARTUP'='1024'
     -e 'MONGO_TLS'=''
     -e 'MONGO_AUTHSOURCE'=''
     -e 'PUID'='99'
     -e 'PGID'='100'
     -e 'UMASK'='022'
     -l net.unraid.docker.managed=dockerman
     -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
     -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/unifi-network-application-icon.png'
     -p '8443:8443/tcp'
     -p '3478:3478/udp'
     -p '10001:10001/udp'
     -p '8080:8080/tcp'
     -p '1900:1900/udp'
     -p '8843:8843/tcp'
     -p '8880:8880/tcp'
     -p '6789:6789/tcp'
     -p '5514:5514/udp'
     -v '/mnt/cache/appdata/unifi-network-application':'/config':'rw' 'lscr.io/linuxserver/unifi-network-application'
   30a1a947ab3c10273d89c661359d6ad9ab415bcecb9371e2d0c6f339e03ed262
   
   The command finished successfully!

   Again, I had to add the webUI address (https://[IP][PORT:8443]) and change the network to use my custom unifi network. You will also need to enter the values you used for MONGO_PASS and MONGO_USER in the init-mongo.js file earlier. I would also suggest using tagged versions on this docker since running latest has been rather risky in the past with unifi controller.

8. Navigate to the unify webui on port 8443 and run new setup. You will need to login to the Ubiquiti website as part of this process. Once the new setup is complete you can restore the backup file that you downloaded at the beginning of this process. This may take a few minutes but once it's complete the app should have all the same devices and configurations.

 

 

Hopefully I haven't missed anything. I'm sure there are probably a few typos. If anyone has any suggestions for changes please let me know.

Just wanted to say thank you very much for this.

After using your guide, plus a bit of help from chatgpt and also https://www.reddit.com/r/Ubiquiti/comments/v42avk/fix_for_adopting_offline_loop_on_docker_unifi/

I had this very annoying problem that adopting access pointes would never finish.

All i had to do was point to my docker container IP.

This was a few hours battle but I was finally able to migrate from my personal computer to my unraid server as my unifi controller.

Thank you!

made a unriad XML adding to CA now with recommended updates.

https://github.com/bmartino1/unraid-docker-templates/blob/main/unifi-os-server.xml

so os should be avilable latter tonight/tomorrow hopefully.

Its Alive