8 hours ago, NeuroDoc said:

Ok, this seemed to work now.  I was also able to restart my other containers, and it's still working.

 

My only concern is that I had to set this container up on the bridge network.  For the old UniFi controller, I set it up under br0 and assigned it a unique IP.  I did this to maintain the AP adoption during software updates.  Going back to the bridge network now, I'm concerned that I will have to go through the adopt process each time the software updates...

It sounds like one of the other dockers is using that port and if it starts first gets it. You will likely continue to have sporadic problems until you identify the conflicting docker. 
 

So far users found plex and jellyfin dockers both try to steal that port but there may be others. 

Edited March 5, 20242 yr by PeteAsking

11 minutes ago, PeteAsking said:

My only concern is that I had to set this container up on the bridge network.  For the old UniFi controller, I set it up under br0 and assigned it a unique IP

This is how I had to set mine up, for this very reason. Another docker was using port 8080.

If you want to know which it is, just open the Unifi template, scroll to the bottom, and expand the "show docker allocations" section.

It'll show you everything that is using ports, and which ones.

2 hours ago, Elmojo said:

It'll show you everything that is using ports, and which ones.

It shows bridge mode allocations.

Host mode containers open a whole can of worms, they have free reign to use whatever ports they want.

 

Don't use host if you can at all help it.

 

Do whatever it takes to figure out what ports are needed and use bridge mode.

14 minutes ago, JonathanM said:

It shows bridge mode allocations.

Host mode containers open a whole can of worms, they have free reign to use whatever ports they want.

How about that, I learned something new!

Thanks @JonathanM 

20 minutes ago, JonathanM said:

Don't use host if you can at all help it.

 

Do whatever it takes to figure out what ports are needed and use bridge mode.

So having my Network type set to "Custom: br0" is host mode, and that's bad?

I have another (vital) container that is using port 8080, and I don't think there's any way around that.

What would be the solution?

 

EDIT: Sorry for the 2 msgs, it wouldn't let me edit in a 2nd quote.

Edited March 5, 20242 yr by Elmojo
apology.

1 minute ago, Elmojo said:

So having my Network type set to "Custom: br0" is host mode, and that's bad?

If you have a different IP assigned to the container that's not host mode. A unique IP can open any and all ports without conflict.

 

Host mode uses the Unraid main IP and can conflict with Unraid's native services. Bridge mode is more like giving the containers their own router and setting up port forwarding where needed.

Most of the issues here are people having no clue what networking decisions they are making and how networking works which is unrelated to this docker. 

49 minutes ago, JonathanM said:

If you have a different IP assigned to the container that's not host mode. A unique IP can open any and all ports without conflict.

 

Host mode uses the Unraid main IP and can conflict with Unraid's native services

Okay, now I'm actually more confused. lol

At least my setup is working, so I'm gonna leave it alone...

25 minutes ago, PeteAsking said:

Most of the issues here are people having no clue what networking decisions they are making and how networking works...

Yep, that would be me!

2 hours ago, PeteAsking said:

Most of the issues here are people having no clue what networking decisions they are making and how networking works which is unrelated to this docker. 

Could be me, but I'm always learning thanks to the great support on forums like this one!

 

...Now, if you need help understanding how to run international clinical trials in rare diseases, I'm your guy!

35 minutes ago, bmartino1 said:

Let's run through some basic networking and docker settings.
 

What are your unraids network settings?

I'm more interested in the setting for bridging and bonding...

Mine looks like this...

 

I feel like your post contains excellent, and extremely useful information, I'm just too ignorant to make use of it. lol

On 3/7/2024 at 5:36 PM, Elmojo said:

Mine looks like this...

...pictures...

I feel like your post contains excellent, and extremely useful information, I'm just too ignorant to make use of it. lol

No worries. It look like you are running multiple nics via a blade server. I recommend using a macvlan drive in your case. I would always recommend to use macvlan over ipvlan unless you require vlan network separations.

 

Per maclvan setup release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.4/

 

I also recommend installing the plugin Tips and tweaks:

 

Goes over information about the settings.

 

Your system atm is using bridge mode and ipvlan for docker access. This should be fine. Surprised to see more than 5 nics on 1 box. 

 

However, bonding is similar to bridging in this case. We get a vhost@interface to act as a gateway between network interfaces. I would recommend you using bonding over bridging to maintain your network.
 

To do this, you will need to have some downtime to turn off some services of that box to edit these settings.

unriad webUI > settings> VM > disable

unriad webUI > turn off auto start of all docker (as there may be some template edits to fix networking...)

unriad webUI > settings> Docker > disable

unriad webUI > settings> NetworkSettings

 

I'd recommend turning off bridging and turning on bonding.

bond eth0 and eth1 as your past configuration for bridging the 2 interfaces.

bonding will also open up more setting for you for fail over , backup if one goes down etc...

 

Then we need to check and fix some docker settings.

unriad webUI > settings> Docker > advance switch

 

its fine to continue to use ipvlan docker driver. you should enable "Preserve user defined networks" and Host access to custom networks.

click apply with docker still off to make changes.

 

-?There may be a reboot required.

Then enable VM and Docker.

Confirm dockers by edit the docker template and fix network if needed. Br0 should be bond0 now.

7 hours ago, bmartino1 said:

It look like you are running multiple nics via a blade server

Yes and no.  Yes, multiple NICs.  No, not a blade server.  It's a PowerEdge T630.  It came to me that way.  I've actually removed 2 NICs to free up slots for other things.  No idea why they had/need so many.  I'm currently only using 1 port on a single NIC, but I'd love to be able to "gang" multiple connections to increase overall speed, kinda like we used to do with the old shotgun modems.  Is that what bonding does, or is it just for failover/redundancy?

 

7 hours ago, bmartino1 said:

Per maclvan setup release notes:

So I read this before upgrading, and understood about 10% of it. lol
What's a call trace?  I assume it's bad, but there's no explanation.  I've never seen anything like it as an error or in my logs, so I assume I don't have that issue?  You say you recommend using macvlan, but later you say that using ipvlan is fine.  I'm confused.  Can you give an example of what difference it would make either way, and what sort of consequences it would have leaving things as they are?  I'm firmly in the "if it ain't broke..." camp.    However, I'm also a believer in tweaking things if they can be improved.  Yes, I hear the irony... lol

7 hours ago, bmartino1 said:

However, bonding is similar to bridging in this case....

I'm sorry to report that I comprehended essentially nothing below this line.

I can certainly follow the steps outlined, but... why?  What would be the benefit?

I'm not doubting your skill or knowledge at all, I'm just wondering, what shortcoming is this addressing, or what positive feature would I be enabling by monkeying with settings that (as best as my ignorant self can tell) are working fairly okay at the moment?

ELI5, por favor? lol

 

EDIT:  So I did install the Tips and tweaks plugin, thanks!   Are there specific changes I should be making, using that plugin?

Edited March 10, 20242 yr by Elmojo
plugin Q

1 hour ago, bmartino1 said:

Your docker settings are trying to use a macvlan setup per your settings. But there is a known issue with macvlan and bridging on. Yes a call trace is bad, it's a system crash / freeze.

Okay, got it, thanks.  I'll see about switching over to ipvlan.

 

1 hour ago, bmartino1 said:

I apologize if that was not clear. I don't know how to be any clearer.

The failure was entirely mine, not yours. I've always had difficulty understanding networking of all types. I'm not sure why, since other computer concepts I find easy to grasp, but networking is like black magic to me.

1 hour ago, bmartino1 said:

Yes, bonding is what you could do to "shotgun" your connection. bonding is more for fail over. Read the tips and tricks for each bonding option type in the picture I sent

Will do.  Not totally sure I'll grasp the implications, but I'll certainly make the effort.

1 hour ago, bmartino1 said:

 I would also recommend these plugins:

if running latest 6.12.8   I am indeed
the Docker.patch2   Got it ✔️

 

CA Auto Update Applications   no thanks, auto update has bitten me more than once (looking at you, Plex!) lol
Docker Compose   not sure I'd need this one...
Dynamix File manager    Got it ✔️
Dynamix System information   looks useful, thanks
Enhanced log viewer   ooh, this looks nice, will be installing soon.
Fix Common Problems  Got it ✔️
Tips and Tweaks    Got it ✔️
User Scripts   Got it ✔️

 

Thanks for all the info.  I'll wade through it as I can, and make corrections to my setup as you've outlined.

I appreciate all your time in putting this together for me!

Just moved to this docker from the unsupported one. Thanks it seems to have worked without any issues.

 

I did change port 1900 to 1901 to match my old docker settings. Also had to backup from v7.3.83 and do the restore on v7.5.187 which seemed to work fine as well.

Tag 8.1.113-unraid is currently being tested. Please do not use this tag unless you are prepared to be part of the testing process. 

On 2/23/2024 at 3:10 AM, yverde said:

Hi,

I'm trying to restore a backup from the official desktop controller app.

When I use this container instead my AP shows as adopting then goes to Offline then back to adopting, but never succeed.

 

 

 

The AP is not offline though as all my devices are not connected to it. 

I'm using the new version 8.0.28

 

Should I be able to restore from a backup made in the official controller?

 

Thanks!

 

 

I just dealt with a similar issues since I just started using this Docker and switched from TP-Link Omada to Ubiquiti UniFi to use the U7-Pro

So in my case yes the reason why it wasnt adopting was not because of this docker but a number of other things.

 

Need to be on controller 8.0.26 which is not default for the Docker from App

 

If your like me and are using a non-Ubiquiti gateway you need to be on U7-Pro Firmware 7.0.35 or newer, it was a known issue.

 

Following this reddit post use SSH to tell the U7-Pro where the inform server is
https://www.reddit.com/r/Ubiquiti/comments/19fgmzl/u7_pro_stuck_in_adopting_on_unifi_network/

 

Last thing also mentioned in the reddit post that I needed to look into further was was setting Inform Host Override. Once I had that set to the IP of my unraid box everything adopted. Previously the Omada Docker was in Host host mode so the equivalent wasnt needed.

Edited March 26, 20242 yr by TheProfosist

No problem here with new update 8.1.113-unraid, so far

14 hours ago, PeteAsking said:

Tag 8.1.113-unraid is currently being tested. Please do not use this tag unless you are prepared to be part of the testing process. 

cheers, I thought I'd give it a go, its installed no problem, but got this message in the output:

 

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.

 

 

54 minutes ago, rorton said:

cheers, I thought I'd give it a go, its installed no problem, but got this message in the output:

 

WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.

 

 

This message is normal, unraid does not support SWAP by default. It is an unraid limitation.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
    
██████╗░███████╗██████╗░░█████╗░██████╗░███╗░░██╗
██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔══██╗████╗░██║
██████╔╝█████╗░░██████╦╝██║░░██║██████╔╝██╔██╗██║
██╔══██╗██╔══╝░░██╔══██╗██║░░██║██╔══██╗██║╚████║
██║░░██║███████╗██████╦╝╚█████╔╝██║░░██║██║░╚███║
╚═╝░░╚═╝╚══════╝╚═════╝░░╚════╝░╚═╝░░╚═╝╚═╝░░╚══╝

            ░█████╗░██████╗░███████╗░██╗░░░░░░░██╗
            ██╔══██╗██╔══██╗██╔════╝░██║░░██╗░░██║
            ██║░░╚═╝██████╔╝█████╗░░░╚██╗████╗██╔╝
            ██║░░██╗██╔══██╗██╔══╝░░░░████╔═████║░
            ╚█████╔╝██║░░██║███████╗░░╚██╔╝░╚██╔╝░
            ░╚════╝░╚═╝░░╚═╝╚══════╝░░░╚═╝░░░╚═╝░░

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
                            🅟🅡🅞🅤🅓🅛🅨 🅟🅡🅔🅢🅔🅝🅣🅢

 

Docker tag: 8.1.113-unraid

 

NEW: Current recommended Home User tag: 11notes/unifi:8.1.113-unraid

 

NEW: Current Company/Corporate recommended tag: 11notes/unifi:8.1.113-unraid

 

Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid

Edited March 25, 20242 yr by PeteAsking

11 hours ago, PeteAsking said:

This message is normal, unraid does not support SWAP by default. It is an unraid limitation.

 

To fix swap messages. You can install the plugin:

The swap file doesn't need to be used, but does need to exist. a reboot may be required after setup.

I recommend making a 2 GB file on the cached drive:

 

This has been the only fix I have found for some dockers that may show error for swap.

By default, disk configuration, 3 disk min for proper setup

2x disk array disk 1 and parity

1x ?ssd/nvme disk for cache

by default, unraid cached disk is btrfs unless you changed it earlier.

You must have a disk attached to unraid and the disk has to be formatted as btrfs to use the swap plugin.

Edited March 26, 20242 yr by bmartino1

Thanks for creating this image. I ported over with no problems.

 

One thing I noticed in the browser console is that font files are failing to load. I'm not sure if this expected:

 

 

26 minutes ago, veeco said:

Thanks for creating this image. I ported over with no problems.

 

One thing I noticed in the browser console is that font files are failing to load. I'm not sure if this expected:

 

 

I can check but I doubt it is important 

34 minutes ago, PeteAsking said:

I can check but I doubt it is important 

 

EDIT: I'll follow up on UI forums, looks like someone else spotted it as well:

https://community.ui.com/releases/UniFi-Network-Application-8-0-24/43b24781-aea8-48dc-85b2-3fca42f758c9#comment/87c8b4cc-3b0e-4927-a271-fc61aedaff24

 

Looking in the container, I found the files at:

`/usr/lib/unifi/webapps/ROOT/app-unifi/react/fonts/`

 

I see that js i properly loading, for example:

`https://192.168.3.152:8443/manage/react/js/5869.2f02b1d33b809f53b77e.js`

 

But the path to the fonts is missing the `manage/react` prefix:

`https://192.168.3.152:8443/fonts/UI_Sans_v8_Regular.eb36d6ff9c768a1639ca397b4dd84137.woff2`

 

It looks like a Unifi problem with the wrong paths, unless there is some configuration option. You can see the inline style loading the wrong path:

 

Edited March 29, 20242 yr by veeco

46 minutes ago, veeco said:

 

EDIT: I'll follow up on UI forums, looks like someone else spotted it as well:

https://community.ui.com/releases/UniFi-Network-Application-8-0-24/43b24781-aea8-48dc-85b2-3fca42f758c9#comment/87c8b4cc-3b0e-4927-a271-fc61aedaff24

 

Looking in the container, I found the files at:

`/usr/lib/unifi/webapps/ROOT/app-unifi/react/fonts/`

 

I see that js i properly loading, for example:

`https://192.168.3.152:8443/manage/react/js/5869.2f02b1d33b809f53b77e.js`

 

But the path to the fonts is missing the `manage/react` prefix:

`https://192.168.3.152:8443/fonts/UI_Sans_v8_Regular.eb36d6ff9c768a1639ca397b4dd84137.woff2`

 

It looks like a Unifi problem with the wrong paths, unless there is some configuration option. You can see the inline style loading the wrong path:

 

Thanks. Will just let unifi resolve it then.