On 1/25/2024 at 7:54 PM, daninet said:

Now the container log is telling me the following:

*** Waiting for MONGO_HOST unifi-db to be reachable. ***
*** Defined MONGO_HOST unifi-db is not reachable, cannot proceed. ***

 

I'm getting the same error and cannot figure out why either.

 

My Unraid Server is at 192.168.0.25, using bridge for MongoDB and br0 for the UniFi Network Application but I don't believe that should be an issue. I've tried moving MongoDB to the same network (using br0) and it didn't change anything.

MongoDb:

 

docker run
  -d
  --name='MongoDB'
  --net='bridge'
  -e TZ="Australia/Sydney"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -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' 'mongo:4.4'

0f7783e566a2de9b4d39d316d114ed69b88110c2e8abb76078e130bad6178db5

 

I create the user etc. by connecting to the console of that MongoDB container and running the 2 commands:
 

db.getSiblingDB("UniFi").createUser({ user: "UniFi", pwd: "xxxxx", roles: [{ role: "dbOwner", db: "UniFi" }] });
db.getSiblingDB("UniFi_stat").createUser({ user: "UniFi", pwd: "xxxxx", roles: [{ role: "dbOwner", db: "UniFi_stat" }] });

unifi-network-application:

 

 docker run
  -d
  --name='unifi-network-application'
  --net='br0'
  --ip='192.168.0.99'
  -e TZ="Australia/Sydney"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="unifi-network-application"
  -e 'TCP_PORT_8443'='8443'
  -e 'UDP_PORT_3478'='3478'
  -e 'UDP_PORT_10001'='10001'
  -e 'TCP_PORT_8080'='8080'
  -e 'UDP_PORT_1900'='1900'
  -e 'TCP_PORT_8843'='8843'
  -e 'TCP_PORT_8880'='8880'
  -e 'TCP_PORT_6789'='6789'
  -e 'UDP_PORT_5514'='5514'
  -e 'MONGO_USER'='UniFi'
  -e 'MONGO_PASS'='xxxxx'
  -e 'MONGO_HOST'='192.168.0.25'
  -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.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/unifi-network-application-icon.png'
  -v '/mnt/user/appdata/unifi-network-application':'/config':'rw' 'lscr.io/linuxserver/unifi-network-application'

fe2fadf61cd8f3ff452dd6be5484be2a5f54a6a6edf1e516ed925155958431fb

I just get this in the UniFi logs:
 

*** Waiting for MONGO_HOST 192.168.0.25 to be reachable. ***
*** Defined MONGO_HOST 192.168.0.25 is not reachable, cannot proceed. ***

Any help would be much appreciated.

EDIT:
Got it working, I had to go to Settings > Docker and make sure 'Host access to custom networks' was set to Enabled.

Edited January 29, 20242 yr by MattFaz
Resolved

Good Morning Everyone 

 

I'm looking for some help and guidance with getting the new unifi container working with MongoDB.

 

I have followed the instructions to the tee but I'm getting no success at all.

 

I have created my init-mongo.js file and put it in the following path //mnt/user/appdata/mongodb/unifi

 

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

 

Within MongoDB i have changed the repository to install version - mongo:7.0-rc, I have changed the network to Host and i have created the path to the .js file. Then started the container within unraid. 

 

Installed the new version of the unifi controller and matched the details from my .js file to the variables within the unifi container installing wizard. Applied and started the container. Within the few seconds i see the .js file being read in the logs on mongoDB but its just full of errors. Which i have attached a picture of within this thread.

 

i did see someone else within this thread have the same issue as me and he resolved by enabling allow host network to see custom networks. I have enabled this and i still have the same issue.

Any help would be greatly appreciated

Edited February 1, 20242 yr by Dialatech2303

Anyone have any advice how to get this working please?

40 minutes ago, Dialatech2303 said:

Anyone have any advice how to get this working please?

Unsure but you can try the other docker container (the reborn one) and see if thats easier for your use case and setup. 

24 minutes ago, PeteAsking said:

Unsure but you can try the other docker container (the reborn one) and see if thats easier for your use case and setup. 

 

Unfortunately i cant use that one. I have tried. When i try to restore from the backup file. It says the backup file is from a newer version of the controller. 

35 minutes ago, Dialatech2303 said:

 

Unfortunately i cant use that one. I have tried. When i try to restore from the backup file. It says the backup file is from a newer version of the controller. 

Yes when you restore it make sure you have changed the tag to be the same version you are coming from, that is normal.

18 minutes ago, PeteAsking said:

Yes when you restore it make sure you have changed the tag to be the same version you are coming from, that is normal.

Sorry i will give this ago 

Anyone else have issue with the app not detecting release candidate firmware updates?

I enabled the release candidate option and signed into my Unifi account but it wont show any release candidate firmware and drop down only shows official channel under updates.

Im confused on what I should put in for a tag. Should I not use :latest? I see people using 7.0-rc which I can do but does that mean that mongo will stay at the 7.0-rc version and never upgrade when updates come out?

On 2/17/2024 at 10:13 AM, jhabers said:

Should I not use :latest?

https://forums.unraid.net/topic/78060-support-linuxserverio-unifi-controller/?do=findComment&comment=1025103

 

This setup was working great for me until about a week ago and now I get a 404 error. No errors showing in the logs. Anyone else getting this error in the last week? Wondering what could have caused it to stop. Hadn’t made any changes to either Unifi or mongo. 

Honestly, I got this docker running just to see if I could but I have deleted it a switched to peteasking version.

I got this up and running yesterday after a lot of fiddling, but now when I am looking at my topology page I dont see my unraid server listed, but I see a device called 'unifi' using the same IP address. I initially had an error message saying that two devices were using the same IP address, but after switching the containers to bridge mode I am still only seeing the 'unifi' device. The 'unifi' device had a unique MAC address, but when I try to lookup the vendor it comes back as invalid. It also says no data is being used even though the actual unraid server with the same IP is downloading something. 

 

Has anyone else seen this?

Anybody experience browser tab freeze after login to the gui?

I just did a complete re-install of mongodb and unifi-network-app only to find out that the issue was the browser.

Brave tab ran out of memory after being frozen for some time, chrome is just working fine.

On 3/3/2024 at 5:38 PM, bmartino1 said:

As this is a network tool. I think this may be better off used as a LXC:

(I assume you have already made a backup of your unifi controller via the controller settings...)
To use unifi network as a LXC:
LXC may be a bit more advance than a docker point and click solution. But give you more control and a full linux environment to do other necessary things. Essentially, this is what's running in pete asking version of the docker...

 

If you want more granular control, you can install the unifi application in a debian/ubuntu lxc container.

Please see the support form for lxc: Be sure to visit the support form for LXC. 

So let's take a look at the LXC option first we need to install the plugin: 

 

set up your lxc path options. I chose to put them under the appdata where docker data is stored.

 

run to fix an issue with unraid /var and lxc path Thanks LXC support team and ICH777 for their assistance:

 

Go to setting LXC set your options:

*My options are set up to use the unraid VM network for an IP address. Your network setting and access to the web server may differ!

You may want to use bond0

 

run script (4th pin) to be able to use lxc on unraid:

*OPTIONAL! - This May or May not be required! Only run if you are unable to make a container form template!

 

LXC_PATH=$(cat /boot/config/plugins/lxc/lxc.conf | grep "lxc.lxcpath=" | cut -d '=' -f2 | head -1)
rm -rf /var/cache/lxc ${LXC_PATH}/cache
mkdir -p ${LXC_PATH}/cache
ln -s ${LXC_PATH}/cache /var/cache/lxc

 

Now go to LXC tab similar to VM and add a container:

 

In my setup for this LXC container, I chose Ubuntu (jammy template). There is a good tutorial here to follow. It may be recommended to use the bionic template at this time. https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux

 

I chose to use jammy and had to go after the deb file individual...

Now let's activate our container and run some commands for setup:

 

First some necessary settings and installs:

 

update packages in container:
 

apt-get update && apt-get upgrade -y

 

Be sure to set up your timezone (fix date and time) by running 

 

dpkg-reconfigure tzdata

 

set a root password:

 

passwd

 

Optional Package that are nifty to have:
 

apt-get install mc nano vim openssh-server nfs-common cifs-utils -y

 

Install some dependency packages:

apt-get install openjdk-17-jre-headless curl libcurl4 ca-certificates apt-transport-https

 

for Ubuntu jammy download the required debs and server to install:

we will be grabing a missing lib for mongdb 4.4, mogodb, and the unfi application:

cd /root/
wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2_amd64.deb
wget https://repo.mongodb.org/apt/ubuntu/dists/focal/mongodb-org/4.4/multiverse/binary-amd64/mongodb-org-server_4.4.29_amd64.deb
wget https://dl.ui.com/unifi/8.0.28/unifi_sysvinit_all.deb

 

Download locations sources:

Lib - ubuntu archive form bionic

mongodb: https://www.mongodb.com/try/download/community-kubernetes-operator

unifi applications: https://ui.com/download/releases/network-server

^ watch for 4.4 updates and unifi updates...

now install the deb files.

#root@Unifi:~# ls
#libssl1.1_1.1.1f-1ubuntu2_amd64.deb  mongodb-org-server_4.4.29_amd64.deb  unifi_sysvinit_all.deb
 

cd /root/
dpkg -i libssl1.1_1.1.1f-1ubuntu2_amd64.deb 
dpkg -i mongodb-org-server_4.4.29_amd64.deb 
dpkg -i unifi_sysvinit_all.deb

 

Congrats, that's it, unifi will auto make the db in mongo. 

service unifi status

 

Remember the https port is set to 8443

https://192.168.1.4:8443/

At the web UI restore from backup.

 

Type to get ip address of lxc container and unifi web UI should be accessible.

ip a

 

I also recommend following the tutorial from here to install:
https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux

 

After the deb files have installed in Jammy we can run the tutorial command to use apt-get update and upgrade to install necessary packages when updates available.

 

Jammy optional add to source list for updates latter:

echo 'deb [ arch=amd64,arm64 ] https://www.ui.com/downloads/unifi/debian stable ubiquiti' | sudo tee /etc/apt/sources.list.d/100-ubnt-unifi.list

sudo wget -O /etc/apt/trusted.gpg.d/unifi-repo.gpg https://dl.ui.com/unifi/unifi-repo.gpg

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50

wget -qO - https://www.mongodb.org/static/pgp/server-3.6.asc | sudo apt-key add -
echo "deb [trusted=yes] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.6.list
sudo apt-get update

sudo apt-get update && sudo apt-get install unifi -y

 

 

Now that we can use apt-get update commands to update the packages / server, lets have the lxc auto do that:

sudo apt install unattended-upgrades -y
sudo dpkg-reconfigure --priority=low unattended-upgrades

 

I recommend running jammy as it is the current Ubuntu LTS.

 

BUT I would recommend use PeteAsking docker as he is doing a great job at maintaining it.

#Edit:
apt-get update --allow-releaseinfo-change

with the update to the network controller some settings here for jammy install may differed form client to client. There may need to be a source file edit to enable repository access to install some packages for mongo db outside what was listed.

Sadly unattended updates didn't auto update to next release actual repository errors with a change order had to run the command "apt-get update --allow-releaseinfo-change" multiple times and then apt-get upgrade.

the unify upgrade install will require you to make a backup first before preceding to next release. If you don't have a backup and hit no, it will not make one and stop unifi. However (as i do have a backup in event of error. You can hit yes, and the system should be fine but do at your own risk!.

LXC is great and I have not had any issues but would still need checking to the Linux environment over a docker image, its best to use pet asking version and move tags when ready.

This worked great.  Gave my DHCP server the generated MAC for the container and it got the same IP as my old controller (docker).  Imported all the settings and up and running.  Thanks!

(Sry for my english. Not a native speaker)

 

Hy guys,

here's what i found out. i had same issuse with the authentiction problems. nothings works. i did everthing as describe in the post earlier. I setup the init script, setup the username and password in the docker variables etc

 

then i had a hunch. in the container unifi-network-application there this file "system.properties" at "/usr/lib/unifi/data". You can access this via console and read the content via cat command.

 

in there, it seems is the mongodb connection string

"db.mongo.uri=mongodb\://unifi\:<PW>@<IP>\:27017/unifi?tls\=false"

 

And it seems that not all variables from the docker config in unraid get passthrough to the contianer. Especially: dbname and password. Because in there is the default password: 12345678 and DB-Name: unifi

 

So no wonder, there is autentication errors. my authentication data which i setup up in the init script and dbname, which i also set in the docker config, got never used.

Dont know what else is not getting through. But i set the values in my initscript to these from the system.properties and it works!

 

I guess the problem is somewhere in the process where the variable should be set in the container, what do you guys thinks?

 

Hope this helps somebody.

 

 

 

Edited May 5, 20242 yr by ekim.w

I already knew thses post, but thank you.

 

For me it looks like it does not take over the values which I set for DB name and Mongo user PW in the MongoDB (via init script) and in the Docker Config.  Only when I took the default values from the container and transferred them to the DB did it work.

On 3/3/2024 at 5:38 PM, bmartino1 said:

As this is a network tool. I think this may be better off used as a LXC:

(I assume you have already made a backup of your unifi controller via the controller settings...)
To use unifi network as a LXC:
LXC may be a bit more advance than a docker point and click solution. But give you more control and a full linux environment to do other necessary things. Essentially, this is what's running in pete asking version of the docker...

 

If you want more granular control, you can install the unifi application in a debian/ubuntu lxc container.

Please see the support form for lxc: Be sure to visit the support form for LXC. 

So let's take a look at the LXC option first we need to install the plugin: 

 

set up your lxc path options. I chose to put them under the appdata where docker data is stored.

 

run to fix an issue with unraid /var and lxc path Thanks LXC support team and ICH777 for their assistance:

 

Go to setting LXC set your options:

*My options are set up to use the unraid VM network for an IP address. Your network setting and access to the web server may differ!

You may want to use bond0

 

run script (4th pin) to be able to use lxc on unraid:

*OPTIONAL! - This May or May not be required! Only run if you are unable to make a container form template!

 

LXC_PATH=$(cat /boot/config/plugins/lxc/lxc.conf | grep "lxc.lxcpath=" | cut -d '=' -f2 | head -1)
rm -rf /var/cache/lxc ${LXC_PATH}/cache
mkdir -p ${LXC_PATH}/cache
ln -s ${LXC_PATH}/cache /var/cache/lxc

 

Now go to LXC tab similar to VM and add a container:

 

In my setup for this LXC container, I chose Ubuntu (jammy template). There is a good tutorial here to follow. It may be recommended to use the bionic template at this time. https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux

 

I chose to use jammy and had to go after the deb file individual...

Now let's activate our container and run some commands for setup:

 

First some necessary settings and installs:

 

update packages in container:
 

apt-get update && apt-get upgrade -y

 

Be sure to set up your timezone (fix date and time) by running 

 

dpkg-reconfigure tzdata

 

set a root password:

 

passwd

 

Optional Package that are nifty to have:
 

apt-get install mc nano vim openssh-server nfs-common cifs-utils -y

 

Install some dependency packages:

apt-get install openjdk-17-jre-headless curl libcurl4 ca-certificates apt-transport-https

 

for Ubuntu jammy download the required debs and server to install:

we will be grabing a missing lib for mongdb 4.4, mogodb, and the unfi application:

cd /root/
wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2_amd64.deb
wget https://repo.mongodb.org/apt/ubuntu/dists/focal/mongodb-org/4.4/multiverse/binary-amd64/mongodb-org-server_4.4.29_amd64.deb
wget https://dl.ui.com/unifi/8.0.28/unifi_sysvinit_all.deb

 

Download locations sources:

Lib - ubuntu archive form bionic

mongodb: https://www.mongodb.com/try/download/community-kubernetes-operator

unifi applications: https://ui.com/download/releases/network-server

^ watch for 4.4 updates and unifi updates...

now install the deb files.

#root@Unifi:~# ls
#libssl1.1_1.1.1f-1ubuntu2_amd64.deb  mongodb-org-server_4.4.29_amd64.deb  unifi_sysvinit_all.deb
 

cd /root/
dpkg -i libssl1.1_1.1.1f-1ubuntu2_amd64.deb 
dpkg -i mongodb-org-server_4.4.29_amd64.deb 
dpkg -i unifi_sysvinit_all.deb

 

Congrats, that's it, unifi will auto make the db in mongo. 

service unifi status

 

Remember the https port is set to 8443

https://192.168.1.4:8443/

At the web UI restore from backup.

 

Type to get ip address of lxc container and unifi web UI should be accessible.

ip a

 

I also recommend following the tutorial from here to install:
https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux

 

After the deb files have installed in Jammy we can run the tutorial command to use apt-get update and upgrade to install necessary packages when updates available.

 

Jammy optional add to source list for updates latter:

echo 'deb [ arch=amd64,arm64 ] https://www.ui.com/downloads/unifi/debian stable ubiquiti' | sudo tee /etc/apt/sources.list.d/100-ubnt-unifi.list

sudo wget -O /etc/apt/trusted.gpg.d/unifi-repo.gpg https://dl.ui.com/unifi/unifi-repo.gpg

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 06E85760C0A52C50

wget -qO - https://www.mongodb.org/static/pgp/server-3.6.asc | sudo apt-key add -
echo "deb [trusted=yes] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.6.list
sudo apt-get update

sudo apt-get update && sudo apt-get install unifi -y

 

 

Now that we can use apt-get update commands to update the packages / server, lets have the lxc auto do that:

sudo apt install unattended-upgrades -y
sudo dpkg-reconfigure --priority=low unattended-upgrades

 

I recommend running jammy as it is the current Ubuntu LTS.

 

BUT I would recommend use PeteAsking docker as he is doing a great job at maintaining it.

#Edit:
apt-get update --allow-releaseinfo-change

with the update to the network controller some settings here for jammy install may differed form client to client. There may need to be a source file edit to enable repository access to install some packages for mongo db outside what was listed.

Sadly unattended updates didn't auto update to next release actual repository errors with a change order had to run the command "apt-get update --allow-releaseinfo-change" multiple times and then apt-get upgrade.

the unify upgrade install will require you to make a backup first before preceding to next release. If you don't have a backup and hit no, it will not make one and stop unifi. However (as i do have a backup in event of error. You can hit yes, and the system should be fine but do at your own risk!.

LXC is great and I have not had any issues but would still need checking to the Linux environment over a docker image, its best to use pet asking version and move tags when ready.

 

Running the update command but get the following error:

 

oot@UniFiController:/# sudo apt-get update && sudo apt-get install unifi -y
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                          
Ign:4 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 InRelease                                                      
Hit:5 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg [801 B]
Ign:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg                  
Get:3 https://dl.ui.com/unifi/debian stable InRelease [2,292 B]              
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,791 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,100 kB]
Reading package lists... Done                         
W: https://repo.mongodb.org/apt/ubuntu/dists/bionic/mongodb-org/3.6/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release: The following signatures were invalid: EXPKEYSIG 58712A2291FA4AD5 MongoDB 3.6 Release Signing Key <packaging@mongodb.com>
E: Repository 'https://dl.ui.com/unifi/debian stable InRelease' changed its 'Codename' value from 'unifi-8.1' to 'unifi-8.2'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
root@UniFiController:/# 

 

29 minutes ago, Flyinace2000 said:

 

Running the update command but get the following error:

 

oot@UniFiController:/# sudo apt-get update && sudo apt-get install unifi -y
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                          
Ign:4 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 InRelease                                                      
Hit:5 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg [801 B]
Ign:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg                  
Get:3 https://dl.ui.com/unifi/debian stable InRelease [2,292 B]              
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,791 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,100 kB]
Reading package lists... Done                         
W: https://repo.mongodb.org/apt/ubuntu/dists/bionic/mongodb-org/3.6/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release: The following signatures were invalid: EXPKEYSIG 58712A2291FA4AD5 MongoDB 3.6 Release Signing Key <packaging@mongodb.com>
E: Repository 'https://dl.ui.com/unifi/debian stable InRelease' changed its 'Codename' value from 'unifi-8.1' to 'unifi-8.2'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
root@UniFiController:/# 

 

Edit your sources.list and change it I guess. Doesnt seem like an unraid wuestion to be fair. 

Hi all.

FWIW, I upgraded from a USG to the Unifi Cloud Gateway Ultra last week, which contains its own Unifi Network application.

The switch over was really easy, and I'm grateful to have simplified the management of the Unifi Network software. 

The device was about the same cost as the old Cloud Key v2 (£106 inc shipping), but also includes a gigabit compatible router (my USG needed to have IPS/IDS disabled to handle gigabit internet speeds), and a 4 port gigabit switch.

It's a great device!

1 hour ago, jademonkee said:

I upgraded from a USG to the Unifi Cloud Gateway Ultra

I did the same a couple of months ago.  I did not mind running the controller as a docker container on Unraid, but, yes, it is nice that it is built in to the Cloud Gateway Ultra.  You have no choice but to run it there and the extra four Ethernet switch ports are nice.

 

Still needed the docker-based controller when I briefly tried the UXG-Lite.  Same price as the Cloud Gateway Ultra so the latter was a no-brainer.

12 hours ago, Flyinace2000 said:

 

Running the update command but get the following error:

 

oot@UniFiController:/# sudo apt-get update && sudo apt-get install unifi -y
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                          
Ign:4 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 InRelease                                                      
Hit:5 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg [801 B]
Ign:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg                  
Get:3 https://dl.ui.com/unifi/debian stable InRelease [2,292 B]              
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,791 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,100 kB]
Reading package lists... Done                         
W: https://repo.mongodb.org/apt/ubuntu/dists/bionic/mongodb-org/3.6/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release: The following signatures were invalid: EXPKEYSIG 58712A2291FA4AD5 MongoDB 3.6 Release Signing Key <packaging@mongodb.com>
E: Repository 'https://dl.ui.com/unifi/debian stable InRelease' changed its 'Codename' value from 'unifi-8.1' to 'unifi-8.2'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
root@UniFiController:/# 

 

 review:
 

You have to fix your source list. and grab the gpg key and sign/secure it.

https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux

 

This was my end script to maintain and use mongo db 4.4:
https://repo.mongodb.org/apt/ubuntu

#older 3.6
#deb [trusted=yes] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 multiverse

deb [trusted=yes arch=amd64 signed-by=/etc/apt/trusted.gpg] https://repo.mongodb.org/apt/ubuntu/ bionic/mongodb-org/4.4 multiverse 

#Depricated key?
deb [trusted=yes arch=amd64 signed-by=/etc/apt/trusted.gpg] https://repo.mongodb.org/apt/ubuntu/ jammy/mongodb-org/4.4 multiverse

Sometime to get unifi to update:
apt-get update --allow-releaseinfo-change

Just did the same and got everything installed yesterday. Replaced my USG and the need to run this docker container on unraid… that no longer has to be running 24/7 to manage my network. Nice bit of kit and surprisingly affordable (I managed to get one for €90).

So Unifi is still wanting MongoDB 4.4 with is now EOL....

While it shouldn't be a problem as the new unfi docker system is a 2 part, run your own mongdb and unfi Linux IO docker.

I wanted to throw out there taht we now have a stable working LXC version of the unifi netwrok application.
 

Otherwise, user who are having issues with running this 2 docker version but wish to stay with docker. Please use Pete asking, unifi reborn docker.

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