May 23, 20251 yr Hello All,I would like to know if this is possible. I am trying to run all my containers a specific VLAN in unifi. I have Eth03 set to BR03 and I place NGINX Proxy Manager and also Jellyfin. I also tried without BR03 and just straight ETH03 but nothing. I see the two containers in Unifi controller but using the url for Jellyfin it does not work. However, when I place both containers back to a custom network in Unraid, I now am able to go to the domain. When both containers are placed in either Eth03 or BR03 the port in Unraid is set to ALL instead of the ip address and the port that are setup on the container.I have change the port forwarding in Unifi to the new IP Address given by DHCP. I also changed the forward address to the new one in NGINX Proxy Manager and nothing. Does anyone have any ideas on what I am missing. I change the ip addresses in both containers for the new one given by the Unifi controller. I also went from IPVLAN to Macvlan on the docket container settings and nothing works. Any help or guide is greatly appreciated.Thank you.
May 27, 20251 yr I'm not sure if this is what you're asking, but i've had many containers setup like this and they'll just get an IP address on the network/VLAN and then setting up the port forwarding is just like any other IP on the network.I solved this by enabling vlans in the network settings on the interface, and then in the docker settings i enabled the network. Then when chose the VLAN network when creating the docker container.
May 27, 20251 yr Author I don’t recall if I tried that or not. I will check later and see if I can get it to work.
May 27, 20251 yr 21 minutes ago, cparman said:I solved this by enabling vlans in the network settings on the interface, and then in the docker settings i enabled the network. Then when chose the VLAN network when creating the docker container.Exactly what I did. I created a Docker VLAN in Unraid (br0.3) and a Docker VLAN in Unifi network. I assigned docker containers an ip address manually in the range of 192.168.3.100 - 192.168.3.150. I did not use DHCP in Unraid VLAN.For setting things up I followed this old post
May 30, 20251 yr Author I tried it again but it did not work. Here is my configuration in Unifi for port forwarding. What I'm I missing?This is the setting in NGINX Proxy Manager for the host domain.NGINX Proxy manager Docker template. IP Address 10.10.60.2JellyFin Docker Template. IP Address 10.10.60.3Network Settings.Docker settings.
May 31, 20251 yr Community Expert Unriad add Vlan...https://www.youtube.com/watch?v=0xk7LsWwp2Ihttps://www.youtube.com/watch?v=9Ta9e09KyYwFirst build your vlans... unifi setups: Edited May 31, 20251 yr by bmartino1
May 31, 20251 yr Author 49 minutes ago, bmartino1 said:Unriad add Vlan...https://www.youtube.com/watch?v=0xk7LsWwp2Ihttps://www.youtube.com/watch?v=9Ta9e09KyYwFirst build your vlans... unifi setups:I have already tried this and the NGINX Proxy Manager does not forward to the correct container.
May 31, 20251 yr Community Expert I run unifi i run unraid, and run nginx as a docker, lxc, vm and other all are usable with unraid and vlans....what are you trying to accomplish?a single docker via NPM? over a vlan to xyz network...???I can only assume network misconfiguration and docker network misconfigurations...nginx is in what docker network as this is possible...Would need unraid vlan network layout and unriad network setting layout to further assist...Since Vlan.. I would suggest making your own custom vlan docker network at br0.vlanID# and assigning nginx a custom ip via the docker network vlan creation...not enoth info to assist. can only give generic info then...
May 31, 20251 yr Community Expert this is becasue your npn docker netowrk is sill using vlan 1 as you passed br3 to the continerwhen you need to make a docker netowrk (preferable macvlan...) and use the bridge interface and valn id nubmer npm shoudl be using something like br3.2 whcih uses vlan 2 as example...
May 31, 20251 yr Author 2 minutes ago, bmartino1 said:I run unifi i run unraid, and run nginx as a docker, lxc, vm and other all are usable with unraid and vlans....what are you trying to accomplish?a single docker via NPM? over a vlan to xyz network...???I can only assume network misconfiguration and docker network misconfigurations...nginx is in what docker network as this is possible...Would need unraid vlan network layout and unriad network setting layout to further assist...Since Vlan.. I would suggest making your own custom vlan docker network at br0.vlanID# and assigning nginx a custom ip via the docker network vlan creation...not enoth info to assist. can only give generic info then...All I want to do is have my containers in a vlan in UniFi so I can control the traffic. I want nginx proxy manager so I can deploy services out on the internet. I hope that makes sense.
May 31, 20251 yr Community Expert with all dockers off i need the output of ip aI need to know the vlan IDs that you have setup (so I can give you the corect comands and docker network on how to get it working...I need to know what vlan and IP npm needs to be set toothen I will glady infomr you where and what settings where broke and how to fix
May 31, 20251 yr Author 11 minutes ago, bmartino1 said:with all dockers off i need the output of ip aI need to know the vlan IDs that you have setup (so I can give you the corect comands and docker network on how to get it working...I need to know what vlan and IP npm needs to be set toothen I will glady infomr you where and what settings where broke and how to fixNPM needs to be in 10.10.60.0/26 network.ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000link/ipip 0.0.0.0 brd 0.0.0.07: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000link/ether 48:f1:7f:9f:ff:8d brd ff:ff:ff:ff:ff:ff8: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff9: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 70:85:c2:bf:38:08 brd ff:ff:ff:ff:ff:ffinet 10.10.80.4/24 metric 1 scope global eth1valid_lft forever preferred_lft forever10: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br3 state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff11: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether a0:36:9f:89:2c:5e brd ff:ff:ff:ff:ff:ffinet 10.10.50.10/28 brd 10.10.50.15 scope global dynamic noprefixroute eth2valid_lft 85692sec preferred_lft 71247sec12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff13: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ffinet 10.10.1.43/24 brd 10.10.1.255 scope global dynamic noprefixroute br0valid_lft 53606sec preferred_lft 40295sec14: vhost1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500link/ether 02:31:e6:8a:b7:d7 brd ff:ff:ff:ff:ff:ff15: vhost2@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500link/ether 02:36:b6:e0:a5:57 brd ff:ff:ff:ff:ff:ff17: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000link/noneinet 10.253.0.1/32 scope global wg0valid_lft forever preferred_lft forever19: br-afd014fe03db: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group defaultlink/ether 02:42:d3:3b:7b:39 brd ff:ff:ff:ff:ff:ffinet 172.20.0.1/16 brd 172.20.255.255 scope global br-afd014fe03dbvalid_lft forever preferred_lft foreverinet6 fe80::42:d3ff:fe3b:7b39/64 scope link proto kernel_llvalid_lft forever preferred_lft forever138: eth3.60@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br3.60 state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff139: br3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ffinet 10.10.60.11/26 brd 10.10.60.63 scope global dynamic noprefixroute br3valid_lft 71300sec preferred_lft 59343sec140: br3.60: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff Edited May 31, 20251 yr by Tucubanito07
May 31, 20251 yr Community Expert 6 minutes ago, Tucubanito07 said:NPM needs to be in 10.10.60.0/26 network.ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000link/ipip 0.0.0.0 brd 0.0.0.07: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000link/ether 48:f1:7f:9f:ff:8d brd ff:ff:ff:ff:ff:ff8: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff9: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether 70:85:c2:bf:38:08 brd ff:ff:ff:ff:ff:ffinet 10.10.80.4/24 metric 1 scope global eth1valid_lft forever preferred_lft forever10: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br3 state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff11: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000link/ether a0:36:9f:89:2c:5e brd ff:ff:ff:ff:ff:ffinet 10.10.50.10/28 brd 10.10.50.15 scope global dynamic noprefixroute eth2valid_lft 85692sec preferred_lft 71247sec12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ff13: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether 70:85:c2:bf:38:06 brd ff:ff:ff:ff:ff:ffinet 10.10.1.43/24 brd 10.10.1.255 scope global dynamic noprefixroute br0valid_lft 53606sec preferred_lft 40295sec14: vhost1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500link/ether 02:31:e6:8a:b7:d7 brd ff:ff:ff:ff:ff:ff15: vhost2@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 500link/ether 02:36:b6:e0:a5:57 brd ff:ff:ff:ff:ff:ff17: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000link/noneinet 10.253.0.1/32 scope global wg0valid_lft forever preferred_lft forever19: br-afd014fe03db: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group defaultlink/ether 02:42:d3:3b:7b:39 brd ff:ff:ff:ff:ff:ffinet 172.20.0.1/16 brd 172.20.255.255 scope global br-afd014fe03dbvalid_lft forever preferred_lft foreverinet6 fe80::42:d3ff:fe3b:7b39/64 scope link proto kernel_llvalid_lft forever preferred_lft forever138: eth3.60@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br3.60 state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ff139: br3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ffinet 10.10.60.11/26 brd 10.10.60.63 scope global dynamic noprefixroute br3valid_lft 71300sec preferred_lft 59343sec140: br3.60: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether a0:36:9f:89:2c:5c brd ff:ff:ff:ff:ff:ffThank you. example pulled form unifi settigns overview I need to knwo the vlan ID and subnet-As you can see I use the subnet to also help inform the valn so vlan 42 will be 192.168.42.xIn your case, I need the VLAN ID that is subnet 10.10.60.0/26ok and what ip of the docker that npm can also access to be a Reverse prxy in what vlan ID that in unraid.as npm will need to be able to talk to xyz dockers on unraid or on lan to be a RP over the vlan.This will dictate docker nework setting for nginx and others.
May 31, 20251 yr Author 1 minute ago, bmartino1 said:Thank you.example pulled form unifi settigns overview I need to knwo the vlan ID and subnet-As you can see I use the subnet to also help inform the valn so vlan 42 will be 192.168.42.xIn your case, I need the VLAN ID that is subnet 10.10.60.0/26ok and what ip of the docker that npm can also access to be a Reverse prxy in what vlan ID that in unraid.as npm will need to be able to talk to xyz dockers on unraid or on lan to be a RP over the vlan.This will dictate docker nework setting for nginx and others.The VLAN id is 60. The NPM and JellyFin are both in the same network 10.10.60.0/26.
May 31, 20251 yr Community Expert Just now, Tucubanito07 said:Does this setting needs to be setup to Automatic?It can I would to allow unifi the abilty to assgin a dhcp ip over that vlan on unraid. no not techanly necessary.What unraid version are you running?general basic guide setup. Pre-setup instructions...Docker settings areDocker network > macvlanhost enable access to custom enabledpreserver custom networks enable:Macvlan is needed for mac address latter... due to vlan intreractions. -while posbble I ahve issues with ipvlan docker netowrk and teh use of vlan them selves...in VM settings make sure it is not virbr0 this adjust are docker vhost0 / shim-brdge network that we will be using...and under Unriad network setting you have enabled vlans.Please make sure these settings are set I now have enother info to generate teh needed infor for termainl comands to make the necessary docker netowrs to use with npm
June 1, 20251 yr Author 8 minutes ago, bmartino1 said:It can I would to allow unifi the abilty to assgin a dhcp ip over that vlan on unraid. no not techanly necessary.What unraid version are you running?general basic guide setup. Pre-setup instructions...Docker settings areDocker network > macvlanhost enable access to custom enabledpreserver custom networks enable:Macvlan is needed for mac address latter... due to vlan intreractions.-while posbble I ahve issues with ipvlan docker netowrk and teh use of vlan them selves...in VM settings make sure it is not virbr0 this adjust are docker vhost0 / shim-brdge network that we will be using...and under Unriad network setting you have enabled vlans.Please make sure these settings are set I now have enother info to generate teh needed infor for termainl comands to make the necessary docker netowrs to use with npmI changed the settings to MacVLAN and host access to enable and also the preserve was set to yes. Now I see that br3.60 is getting the 169.254 ip address.
June 1, 20251 yr Community Expert OK Here is what I understand form the post overall interactions:Goal Summary:VLAN 60 is on interface br3.60 (associated with eth3.60)Subnet: 10.10.60.0/26 (range: 10.10.60.1 to 10.10.60.62)br3 already has IP 10.10.60.11 in that rangeYou want NPM and Jellyfin to be accessible within that VLAN (ideally NPM reverse-proxies Jellyfin)Containers need to be attached to a macvlan network on br3.60What is your current docker networks?docker network lsWe need a vlan60 Docker macvlan network creation command:This will make docker netwrok vlan60_macvlandocker network create -d macvlan \ --subnet=10.10.60.0/26 \ --gateway=10.10.60.1 \ -o parent=br3.60 \ --ip-range=10.10.60.32/27 \ vlan60_macvlanI will use compose. docker unraid teamptle is fine just somethgin to review for easy setting explinatiaons... GuideUpdate/Deploy Jellyfin & NPM on this networkWhen setting up Jellyfin and NPM containers (via Unraid's Docker GUI or a Docker Compose stack), assign them to vlan60_macvlan and assign static IPs if desired:Example for docker-compose.yml:compose reference to explain network settigns latter. you will make theses edits to your pre existing docker tempatlesversion: '3.8'networks: vlan60_macvlan: external: trueservices: jellyfin: image: jellyfin/jellyfin container_name: jellyfin networks: vlan60_macvlan: ipv4_address: 10.10.60.20 volumes: - /path/to/config:/config - /path/to/media:/media restart: unless-stopped npm: image: jc21/nginx-proxy-manager:latest container_name: npm networks: vlan60_macvlan: ipv4_address: 10.10.60.21 volumes: - /path/to/npm/data:/data - /path/to/npm/letsencrypt:/etc/letsencrypt ports: - "80:80" - "443:443" - "81:81" # NPM UI restart: unless-stoppedThis means with the unraid setings pre set, and a docker network exist you need to edit npm docekr network and set it to macvlan60the same for jelly fin!*Should be good per pictures above Guide notes:Double check and Configure NPM to Reverse Proxy Jellyfin:Once NPM is up:Go to http://10.10.60.21:81 (NPM UI)Log in → “Proxy Hosts” → “Add Proxy Host”Set:Domain Names: (e.g. jellyfin.local or real FQDN)Forward Hostname/IP: 10.10.60.20Forward Port: 8096 (Jellyfin default)Enable SSL (if needed)Optionally add access lists or cache settings4 double check unraid ip routes:Make Sure Routes Are ReachableEnsure:The 10.10.60.1 gateway (your router or Unifi/managed switch?) knows how to route to these container IPs.If needed, add a static route to your network so you can reach Jellyfin/NPM from outside Unraid.secondary notes for unraid:Optional: Disable Host-Network ConflictsUnraid sometimes blocks communication between the host and macvlan containers. To work around this:Create a macvlan bridge instead of macvlan:docker network create -d macvlan \ --subnet=10.10.60.0/26 \ --gateway=10.10.60.1 \ -o parent=br3.60 \ --ip-range=10.10.60.32/27 \ --aux-address="host=10.10.60.2" \ vlan60_macvlanAdd a "macvlan workaround" interface to Unraidip link add mac0 link br3.60 type macvlan mode bridgeip addr add 10.10.60.2/26 dev mac0ip link set mac0 up-This lets the host (Unraid) talk to containers on the macvlan. Making or own netowrtk brdige for cross talk...you should now see jellyfin and npm on vlan 60 of your unraid...
June 1, 20251 yr Community Expert 2 minutes ago, Tucubanito07 said:I changed the settings to MacVLAN and host access to enable and also the preserve was set to yes. Now I see that br3.60 is getting the 169.254 ip address.we may need to flush br3 interface IP and run comands to set teh ip to br3.60example scripthttps://forums.unraid.net/topic/190273-712-docker-no-shim-network/#findComment-1554564
June 1, 20251 yr Author Here is my docker network.root@Tower:~# docker network lsNETWORK ID NAME DRIVER SCOPEed036bb9b6d1 br0 macvlan local6323836f8922 br3 macvlan local065a67fd4699 bridge bridge local4a0546e90094 eth1 macvlan localbfa58ee9ccb5 host host locale2b5c5604762 none null localafd014fe03db proxy-network bridge local Edited June 1, 20251 yr by Tucubanito07
June 1, 20251 yr Author This is what I get when I tried to create the mtacvlan command from above.root@Tower:~# docker network create -d macvlan \--subnet=10.10.60.0/26 \--gateway=10.10.60.1 \-o parent=br3.60 \--ip-range=10.10.60.32/27 \vlan60_macvlanError response from daemon: failed to allocate gateway (10.10.60.1): Address already in use
June 1, 20251 yr Community Expert Just now, Tucubanito07 said:This is what I get when I tried to create the mtacvlan command from above.root@Tower:~# docker network create -d macvlan \--subnet=10.10.60.0/26 \--gateway=10.10.60.1 \-o parent=br3.60 \--ip-range=10.10.60.32/27 \vlan60_macvlanError response from daemon: failed to allocate gateway (10.10.60.1): Address already in usethis was expected as it already exist as br3we need to delete the br3 docker network firstthis will permenatly delete vr3 docker netwrokdocker network rm br3
June 1, 20251 yr Author 1 minute ago, bmartino1 said:this was expected as it already exist as br3we need to delete the br3 docker network firstthis will permenatly delete vr3 docker netwrokdocker network rm br3Okay now I got this. root@Tower:~# docker network lsNETWORK ID NAME DRIVER SCOPEed036bb9b6d1 br0 macvlan local065a67fd4699 bridge bridge local4a0546e90094 eth1 macvlan localbfa58ee9ccb5 host host locale2b5c5604762 none null localafd014fe03db proxy-network bridge local2c0d737c23b6 vlan60_macvlan macvlan local
June 1, 20251 yr Community Expert perfect this tells me that you have a unraid docker network that is using and on vlan 60Assuming you ran:docker network create -d macvlan \--subnet=10.10.60.0/26 \--gateway=10.10.60.1 \-o parent=br3.60 \--ip-range=10.10.60.32/27 \vlan60_macvlanNow its on to editing the dockers tempalte to the new docker network in the drop-down list.Please edit npm and select custom vlan60_maclanyou will need to set a ip statical here as wellyou will need to set the same for jellyfin
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.