[Support] Linuxserver.io - Unifi-Controller

[ekim.w]

(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 by ekim.w

[bmartino1]

1 hour ago, ekim.w said:

(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.

 

 

 

when making the unfi docker that file is create once at first setup if it is not the same as you init mong file it will not work with a wuth problem.
 

Please review this post in thi forum that goies over most of the setup:

Otherwise I would recommend you back up your config and move to pete asking version. a all in one solution.

[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.

[Flyinace2000]

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:/# 

 

[PeteAsking]

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. 

[jademonkee]

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!

[Hoopster]

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.

[bmartino1]

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

[johnieutah]

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).

[bmartino1]

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.

[danioj]

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

[bmartino1]

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....

[bmartino1]

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...

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 August 3 by bmartino1

[jowi]

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

[bmartino1]

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]

 

[jowi]

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

 

[bmartino1]

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...

[zeganr]

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":{}}}

[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":{}}}

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 by bmartino1

[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 by bmartino1