57 minutes ago, mailmonster said:

How can i update the unifi Software within the docker? 

Kind regards Chris 

Its on page 1 but essentially you change the tag to a tag of your choosing.

8.3.32 is still being tested

8.3.32-unraid tag is tested and available for home users in production.

also want to throw the warning out there that mongodb 4.4 is EOL. This is not necessary a bad thing.

I'm not sure if/when unifi plans to upgrade into the next gen or current release of mongdb..
https://community.ui.com/questions/Supported-Mongodb-version-is-EOL/6a97712b-2a58-4d96-8733-14b18c3ca063

something to ask 11notes on how we will proceed on this?
https://www.mongodb.com/legal/support-policy/lifecycles

Edited July 31, 20241 yr by bmartino1

On 7/31/2024 at 3:15 PM, bmartino1 said:

also want to throw the warning out there that mongodb 4.4 is EOL

Controller version 8.1 and newer supports up to MongoDB 7.0

On 8/5/2024 at 6:27 AM, fat said:

Controller version 8.1 and newer supports up to MongoDB 7.0

Unfortunately, support vs required and maintaining that software in release cycles is the problem...

unifi support per communications still claimed clients and end devices to run MongoDB 4.4 Which is EOL.. that's the problem...

https://evanmccann.net/blog/ubiquiti/unifi-network-release-notes

With testing from those changes in earlier version of 7.5, we had reports of clients running 7, and it appeared to work, but unifi said that is running a unsupported version... (in the other linux io post for 2 staged docker I used v7 and unfi network 7.5) ...

Trying to find all the unifi specif links to it...
https://community.ui.com/releases/UniFi-Network-Application-8-0-24/43b24781-aea8-48dc-85b2-3fca42f758c9
UniFi Network Application 7.5 and newer requires MongoDB 3.6 (up to 4.4) and Java 17.

While "v8 can support v7 MongoDB support" and "move off of EOL" are 2 different things...


The minimum MongoDB version required for the UniFi Network application is 3.6, and the maximum is 4.4, depending on the version of the application:

Versions 7.5 and newer: Require MongoDB 3.6 and Java 17

Versions 7.5–8.0: Support up to MongoDB 4.4

Version 8.1 and newer: Support up to MongoDB 7.0

Edited August 7, 20241 yr by bmartino1

there's no need to use a separate mongodb on this one?

7 minutes ago, gacpac said:

there's no need to use a separate mongodb on this one?

Correct.

I want to move off a cloudkey Gen1 in a different location. Can I do that with no problem using the docker? 

13 minutes ago, gacpac said:

I want to move off a cloudkey Gen1 in a different location. Can I do that with no problem using the docker? 

Look back in this thread 5 pages and see if the discussion applies. I don't know if a UDM and cloudkey are similar or not, but I suspect moving from Unifi hardware to a software hosted instance may be problematic.

On 8/15/2024 at 8:54 PM, gacpac said:

I want to move off a cloudkey Gen1 in a different location. Can I do that with no problem using the docker? 

yes.

make sure you get a backup with the correct network applications.

I make posts going thoruhg that here:

read on for how to restore as well...

I migrated from the legacy Unifi docker to this a few months ago and all seemed well, but now I'm having trouble adopting devices. (on repo /unifi:8.3.32-unraid)

 

I had a Switch Ultra that started acting up and went into some kind of adoption / offline loop, and though it worked OK , and showed as adopted in logs, I could not access or configure it in the UI.

 

I contacted Unifi support who ultimately requested that I DMA the switch.

 

However, Now I've acquired a USW-Pro-24-PoE and it's doing the exact same thing!!

 

I like running my controller in unRaid, but with the deprecation, migration hassle, and now this nonsense, I'm thinking of abandoning it and getting a Unifi key altogether.

 

Any insights?

8 minutes ago, meep said:

I migrated from the legacy Unifi docker to this a few months ago and all seemed well, but now I'm having trouble adopting devices. (on repo /unifi:8.3.32-unraid)

 

I had a Switch Ultra that started acting up and went into some kind of adoption / offline loop, and though it worked OK , and showed as adopted in logs, I could not access or configure it in the UI.

 

I contacted Unifi support who ultimately requested that I DMA the switch.

 

However, Now I've acquired a USW-Pro-24-PoE and it's doing the exact same thing!!

 

I like running my controller in unRaid, but with the deprecation, migration hassle, and now this nonsense, I'm thinking of abandoning it and getting a Unifi key altogether.

 

Any insights?

 

When you say "into some kind of adoption / offline loop, and though it worked OK , and showed as adopted in logs," can you clarify this? Can you post screenshots or a video of what is happening? Can you also tell us what inform ip you set and what the ip of the docker is?

 

Pete

48 minutes ago, PeteAsking said:

 

When you say "into some kind of adoption / offline loop, and though it worked OK , and showed as adopted in logs," can you clarify this? Can you post screenshots or a video of what is happening? Can you also tell us what inform ip you set and what the ip of the docker is?

 

Pete

 

The device shows as adopting;

 

Then goes offline for a moment;

 

Then repeats on a loop.

 

On the first try, my logs show success;

 

But the adopting / offline loop just keeps going.

 

Docker Inspect shows the docker IP to be 

172.17.0.10

 

When I had the Ultra, I couldn't SSH into it (not supported), but your post just reminded me this was a switch with SSH supported;

 

 

I did a set inform to the IP of my unraid server, et voila, it worked!

 

Though that brings up my next question.......

 

Whenever I have occasion to stop and restart this docker, my USG-Pro-4 'forgets' its inform UL and I need to log in to the device UI and reset it. I suspect I'm going to have the same issue with this switch. Any thoughts on that?

 

 

 

 

 

 

 

6 minutes ago, meep said:

 

The device shows as adopting;

 

Then goes offline for a moment;

 

Then repeats on a loop.

 

On the first try, my logs show success;

 

But the adopting / offline loop just keeps going.

 

Docker Inspect shows the docker IP to be 

172.17.0.10

 

When I had the Ultra, I couldn't SSH into it (not supported), but your post just reminded me this was a switch with SSH supported;

 

 

I did a set inform to the IP of my unraid server, et voila, it worked!

 

Though that brings up my next question.......

 

Whenever I have occasion to stop and restart this docker, my USG-Pro-4 'forgets' its inform UL and I need to log in to the device UI and reset it. I suspect I'm going to have the same issue with this switch. Any thoughts on that?

 

 

 

 

 

 

 

You have to set the inform ip in the settings on the docker controller web ui or it will forget. If you set it correctly in the web interface then it will work if you reboot the switch.

10 minutes ago, PeteAsking said:

You have to set the inform ip in the settings on the docker controller web ui or it will forget. If you set it correctly in the web interface then it will work if you reboot the switch.

 

Ah, something that must not have come through when I migrated, or perhaps something new. Is this what you refer to?
 

 

So maybe my Switch Ultra could have worked after all?

 

Edited August 26, 20241 yr by meep

2 hours ago, meep said:

 

Ah, something that must not have come through when I migrated, or perhaps something new. Is this what you refer to?
 

 

So maybe my Switch Ultra could have worked after all?

 

Yes this has to be set to the correct inform ip to avoid problems.

28 minutes ago, PeteAsking said:

Yes this has to be set to the correct inform ip to avoid problems.

also check that the unifi device is truly factory reset and that your ssh account login data is correct. Factory device should be accessible via user/pwd unifi unifi. After adoptions, the settings are applied. I have experienced similar but that a unfi controller owner issue.

If you adopt an older hardware, change the account auth setting to adopt a new device without pushing the old device will attempt the adoption with the wrong credential when moving controllers... I have seen that a few time when changing account login settings here back in the volo ISP day...

 

Changing the Device ssh auth can cause this loop if pre adopted devices never sync to the controller properly.

Similar issues found on unifi forum:
example: https://community.ui.com/questions/SSH-Mess-Password-not-updating-via-SSO-Local-SSH-not-working/f272ca54-b78e-4346-9e7b-33cd6c15ff9c

 

if you know the old auth credential, you can readopt by login into the device and set then inform ip to readopt and update the credentials.

 

set inform IP:
https://nickschick.com/info/unifi-controller-cli-inform#:~:text=To set the inform URL,with your specific inform URL.

80% of the time, the loop as you described is the controller sending bad login credential to make changes.

Edited August 26, 20241 yr by bmartino1

hi @PeteAsking, thanks for the great work. I have just started using it, so far so good.

 

But there is one thing that caught my attention. The traffic data seem to be off for some of my devices.

 

971 TB is my Unraid home server and 141 TB is my Apple TV. There is no way these devices consumed this much data. Is it a known issue?

 

3 hours ago, st34m said:

hi @PeteAsking, thanks for the great work. I have just started using it, so far so good.

 

But there is one thing that caught my attention. The traffic data seem to be off for some of my devices.

 

971 TB is my Unraid home server and 141 TB is my Apple TV. There is no way these devices consumed this much data. Is it a known issue?

 

Its probably something to do with the controller being a docker and the values being inaccurate as a result. Im not sure how unifi code and calculate this or how to fix it. Its probably not even high on unifis list of issues to look into. When the docker is built it just uses whatever code unifi provides and is not modified in any way. 

Edited August 28, 20241 yr by PeteAsking

Correct this is due to the data record becoming double or being duplicated or record twice. as it traveled to unrad and then on unriad with in the virtual network, it created for docker to run. runing macvlan can help mitigate some of the false traffic data. I have not experienced that on a vm or LXC. In theory the unifi mongodb has a recorded log that taps and records that data and should aslo be affected on a VM/LXC.

I agree with Pete asking here where this is how the technology is host the network application and is a false positive of data on how unraid is handling the traffic and how the unifi network application is seeing the data.

Are the current docker compose files online? i'd liek to see how the images are built.

 

Thanks!

https://github.com/11notes/docker-unifi
 

 

7 hours ago, RackIt said:

Are the current docker compose files online? i'd liek to see how the images are built.

 

Thanks!

Unraid uses a template to build the docker run comad to use docekrs. Note the -l option labels. to use on another platform, you would need to recreate a compse file... https://www.composerize.com/

Example defaults network braidge:

docker run
  -d
  --name='unifi-controller-reborn'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Unraid"
  -e HOST_CONTAINERNAME="unifi-controller-reborn"
  -e 'MEM_LIMIT'='4096'
  -e 'MEM_STARTUP'='2048'
  -e 'UMASK'='002'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8443]'
  -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg'
  -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/user/appdata/unifi-controller-reborn':'/unifi/var':'rw'
  --memory=4G '11notes/unifi:7.5.187-unraid'

example unraid compose file:
(would only work on unraid...)

version: "3"
services:
    unifi:
        container_name: unifi-controller-reborn
        network_mode: bridge
        deploy:
            resources:
                limits:
                    pids: 2048
                    memory: 4G
        environment:
            - TZ=America/Chicago
            - HOST_OS=Unraid
            - HOST_HOSTNAME=Unraid
            - HOST_CONTAINERNAME=unifi-controller-reborn
            - MEM_LIMIT'='4096
            - MEM_STARTUP'='2048
            - UMASK'='002
        labels:
            - net.unraid.docker.managed=dockerman
            - net.unraid.docker.webui='https://[IP]:[PORT:8443]'
            - net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg'
        ports:
            - 8443:8443/tcp
            - 3478:3478/udp
            - 10001:10001/udp
            - 8080:8080/tcp
            - 1900:1900/udp
            - 8843:8843/tcp
            - 8880:8880/tcp
            - 6789:6789/tcp
            - 5514:5514/udp
        volumes:
            - /mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw
        image: "'11notes/unifi:7.5.187-unraid'"

There is quite abit I would do form network creation for a static ip on the lan via macvlan. And other changes such as hostname to unifi...

I would look at the current latest release as well as this will pull network application 7.5.187

Edited August 31, 20241 yr by bmartino1

non unriad compsoe example file:

 

version: "3"
services:
    unifi:
        container_name: unifi
        network_mode: "custom_macvlan"
        deploy:
            resources:
                limits:
                    pids: 2048
                    memory: 4G
        environment:
            - TZ=America/Chicago
            - HOST_CONTAINERNAME=unifi
            - MEM_LIMIT=4096
            - MEM_STARTUP=2048
        ports:
            - 8443:8443/tcp
            - 3478:3478/udp
            - 10001:10001/udp
            - 8080:8080/tcp
            - 1900:1900/udp
            - 8843:8843/tcp
            - 8880:8880/tcp
            - 6789:6789/tcp
            - 5514:5514/udp
        volumes:
            - (path on host)/mnt/user/appdata/unifi-controller-reborn:/unifi/var:rw
        image: "11notes/unifi:8.3.32"  # Verify image and network application
        hostname: "unifi"
        networks:
            custom_macvlan:
                ipv4_address: 192.168.1.2  # Set a static IP

networks:
    custom_macvlan:
        driver: macvlan
        driver_opts:
            parent: eth0  # Set to your host network interface
        ipam:
            config:
                - subnet: 192.168.1.0/24
                  gateway: 192.168.1.1

use at own risk. not tested...

Edited August 31, 20241 yr by bmartino1