Yvan Posted June 24, 2021 Share Posted June 24, 2021 (edited) At present, both unreaid and VM can get the IPv6 address normally, but the docker application can't get the IPv6 address. What settings do i need to make in unraid. At present, I only need nextcloud in docker to get the IPv6 address. Through query, nextcloud supports IPv6 So please confirm what settings need to be made for unraid thanks home-lab-diagnostics-20210624-0908.zip --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.eth0.use_tempaddr=2 Today, through this command, nextcloud can already obtain an IPV6 address through SLAAC, but I hope to obtain an IPV6 address through DHCPv6. Can it be achieved by modifying the above command? If so, how should it be modified? Edited June 24, 2021 by Yvan Quote Link to comment
jonp Posted June 25, 2021 Share Posted June 25, 2021 Can anyone here help @Yvan with this request? My Docker networking expertise isn't as strong as some of you here ;-). Quote Link to comment
bonienl Posted June 25, 2021 Share Posted June 25, 2021 Docker host and docker bridge networks can only operate on IPv4, to use IPv6 you need to configure a custom network. The example below is going to use br0 as custom docker network with both IPv4 and IPv6 (you can disable the bonding part when a single interface is used). First: make sure under network settings both IPv4 and IPv6 is enabled. The preference is to use automatic IPv6 assignment, using either DHCP or SLAAC. Your router must be properly configured to hand-out an IPv6 address and associated DNS server address(es). Second: Under Docker settings enable the necessary br0 networks for both IPv4 and IPv6 Note: - Configure a DHCP pool for IPv4 which hands out IPv4 addresses to containers and does NOT clash with the DHCP range of your router. - Leave the DHCP pool for IPv6 disabled, docker uses an assignment which won't clash with your router Configure a docker container to use custom network br0. The example below shows the Firefox application. Since Firefox is a browser, it can be used to access the Internet on both IPv4 and IPv6 and we can test connectivity... Use ipv6-test.com Note: Certain traffic in my network is inhibited due to the firewall rules I have created on my router (out of scope for this tutorial). 3 Quote Link to comment
jonp Posted June 25, 2021 Share Posted June 25, 2021 Thank you @bonienl! As always you are a rockstar! 1 Quote Link to comment
Yvan Posted June 29, 2021 Author Share Posted June 29, 2021 On 2021/6/26 at AM1点04分, bonienl said: Docker主机和 docker桥接网络只能在 IPv4 上运行，要使用 IPv6，您需要配置自定义网络。 下面的示例将使用 br0 作为具有 IPv4 和 IPv6 的自定义 docker 网络（当使用单个接口时，您可以禁用绑定部分）。 首先：确保在网络设置下启用了 IPv4 和 IPv6。首选是使用自动 IPv6 分配，使用 DHCP 或 SLAAC。您的路由器必须正确配置以分发 IPv6 地址和关联的 DNS 服务器地址。 第二：在 Docker 设置下为 IPv4 和 IPv6 启用必要的 br0 网络 笔记： - 为 IPv4 配置一个 DHCP 池，它将 IPv4 地址分发给容器，并且不会与路由器的 DHCP 范围发生冲突。 - 禁用 IPv6 的 DHCP 池，docker 使用不会与路由器冲突的分配 配置 docker 容器以使用自定义网络 br0。下面的示例显示了 Firefox 应用程序。 由于 Firefox 是一个浏览器，它可以用来访问 IPv4 和 IPv6 上的 Internet，我们可以测试连接性...使用ipv6-test.com 注意：由于我在路由器上创建的防火墙规则（超出本教程的范围），我的网络中的某些流量被禁止。 I have finished steps 1 and 2. I have installed a firebox, but I still can't get the IPv6 address. Then I add this parameter in the docker to get the IPv6 address through SLAAC, but I can't get the IPv6 address through DHCPv6. --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.eth0.use_tempaddr=2 The reason why I want to get the IPv6 address through DHCPv6 is that DHCPv6 will give the application a DUID, which is convenient for me to do DDNS Quote Link to comment
bonienl Posted June 29, 2021 Share Posted June 29, 2021 6 minutes ago, Yvan said: --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.eth0.use_tempaddr=2 No need to do these commands. You can set "IPv6 privacy extensions = Enabled" 8 minutes ago, Yvan said: The reason why I want to get the IPv6 address through DHCPv6 Docker uses its own internal DHCP server, this is true for both IPv4 and IPv6. You can not use an external server (your router) as DHCP server. Quote Link to comment
ken-ji Posted July 2, 2021 Share Posted July 2, 2021 @bonienl I think I've pointed this out before, but some fun points. Containers can use SLAAC (as advertised by a router) instead of DHCPv6 since some routers (Mikrotik ones in particular) do not support DHCPv6 completely - only SLAAC This approach is extremely useful when your ISP doesn't even consider assigning you a static prefix and just delegates an entire /56 to you dynamically and you can configure your router to dynamically advertise the prefix Docker networking in IPv6 wants a static prefix or you will be restarting the docker network whenever you need the prefix to change In order to use SLAAC, the docker custom network does not need to have IPv6 enabled (or the interface for that matter) To configure a container to enable SLAAC, you then need to pass the extra parameters specified --sysctl net.ipv6.conf.all.disable_ipv6=0 The container will then have its own IP address based on what the network is advertising (again SLAAC) [email protected]:~# docker exec nginx ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: [email protected]: <NOARP> mtu 1476 qdisc noop state DOWN qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: [email protected]: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: [email protected]: <BROADCAST,MULTICAST> mtu 1464 qdisc noop state DOWN qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 75: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:c0:a8:5f:0a brd ff:ff:ff:ff:ff:ff inet 192.168.95.10/24 brd 192.168.95.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fd6f:3908:ee39:4001:a170:6031:f3df:e8b/64 scope global secondary dynamic valid_lft 3296sec preferred_lft 1496sec inet6 fd6f:3908:ee39:4001:42:c0ff:fea8:5f0a/64 scope global dynamic valid_lft 3296sec preferred_lft 1496sec inet6 fe80::42:c0ff:fea8:5f0a/64 scope link valid_lft forever preferred_lft forever [email protected]:~# docker exec nginx ip -6 route fd6f:3908:ee39:4001::/64 dev eth0 metric 256 expires 0sec fe80::/64 dev eth0 metric 256 multicast ff00::/8 dev eth0 metric 256 default via fe80::ce2d:e0ff:fe50:e7b0 dev eth0 metric 1024 expires 0sec As I don't have DHCPv6, I think this approach will work for DHCPv6, but only if the container is designed to do DHCPv6, otherwise docker will not do DCHPv6 (it doesn't do DHCPv4 either) and instead has an internal IPAM (IP address management) which will simply assign addresses from the configured pool in the docker network. 2 Quote Link to comment
bonienl Posted July 2, 2021 Share Posted July 2, 2021 @ken-jithanks for the reminder, I forgot about it. SLAAC is enabled too when IPv6 is set in the GUI for the docker network, but your solution gives some interesting simplification. I put this on the radar for a future enhancement. Quote Link to comment
KluthR Posted December 1, 2021 Share Posted December 1, 2021 On 6/25/2021 at 7:04 PM, bonienl said: - Leave the DHCP pool for IPv6 disabled, docker uses an assignment which won't clash with your router I tried that and my router also displayed a ipv6 starting with 2003 - which seems to be a public v6 (my router gets a v6 block). Is this v6 reused every update/edit of the container? or does in change? If it change, how can I assign a static v6 without the prefix? like: br 0: x.x.x.x, ::8 does not work. Quote Link to comment
bonienl Posted December 1, 2021 Share Posted December 1, 2021 Unraid version 6.9 supports IPv6 for custom (macvlan) networks only. A docker container gets an IPv6 address out of the subnet announce by your router on the LAN network. 2003 is indeed a public IPv6 address, and when obtained by SLAAC it stays the same after each container update/edit unless you change the MAC address of the container (which is a manual thing) Unraid version 6.10 also supports IPv6 for the standard bridge network. In this case the container gets a private IPv6 address and NAT is used to connect to the outside world. This is similar to how IPv4 works with private IPv4 addresses on your LAN and NAT to a public address to go outside on the Internet. 1 Quote Link to comment
KluthR Posted December 1, 2021 Share Posted December 1, 2021 You said, 6.9 support v6 via macvlan only. But I got a v6, as said. This seem a docker thing. So, as long as I (or docker) changes the mac, it should be usable? How docker remebers to not change the mac when unraid deletes and recreates a container (during update)? Are you preserving a container specific network (or -setting?) cant wait for 6.10 and all those improvements Quote Link to comment
psychofaktory Posted February 9, 2022 Share Posted February 9, 2022 What does the configuration has to look like if I want to assign a static IPv6 address for the container on a custom network? I have specified a static address, but I cannot reach the container at this address. [email protected]:~# docker exec syncthing ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: [email protected]: <NOARP> mtu 1476 qdisc noop state DOWN qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: [email protected]: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: [email protected]: <BROADCAST,MULTICAST> mtu 1464 qdisc noop state DOWN qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 33: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:0a:0a:0a:0d brd ff:ff:ff:ff:ff:ff inet 10.10.10.13/24 brd 10.10.10.255 scope global eth0 valid_lft forever preferred_lft forever inet6 XXXX:XX:XXXX:1010:0:10:10:13/64 scope global flags 02 valid_lft forever preferred_lft forever inet6 fe80::42:aff:fe0a:a0d/64 scope link valid_lft forever preferred_lft forever Quote Link to comment
ken-ji Posted February 9, 2022 Share Posted February 9, 2022 What are you using to reach the the container over IPV6? Unraid cannot reach anything on br0, as 6.9.2 macvlan system used by docker expressly prohibits the host and container communication over the "shared" interface. Also, does your LAN ipv6 have the same /64 prefix as the container? In my case I don't use static assignments, just SLAAC, which gives me fairly static IPV6 address since the container MAC address is defined by the static IPv4 assigned to it. [email protected]:~# ip addr s dev br0 18: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 70:85:c2:4a:e1:d1 brd ff:ff:ff:ff:ff:ff inet 192.168.2.5/24 scope global br0 valid_lft forever preferred_lft forever inet6 xxxx:xxxx:xxxx:xxxx:7285:c2ff:fe4a:e1d1/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3584sec preferred_lft 1784sec inet6 fd6f:3908:ee39:4001:7285:c2ff:fe4a:e1d1/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3584sec preferred_lft 1784sec inet6 fe80::7285:c2ff:fe4a:e1d1/64 scope link valid_lft forever preferred_lft forever [email protected]:~# docker exec nginx ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: [email protected]: <NOARP> mtu 1476 qdisc noop state DOWN qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: [email protected]: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: [email protected]: <BROADCAST,MULTICAST> mtu 1464 qdisc noop state DOWN qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: [email protected]: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 215: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:c0:a8:5f:0a brd ff:ff:ff:ff:ff:ff inet 192.168.95.10/24 brd 192.168.95.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fd6f:3908:ee39:4002:42:c0ff:fea8:5f0a/64 scope global dynamic flags 100 valid_lft 3435sec preferred_lft 1635sec inet6 xxxx:xxxx:xxxx:xxxx:42:c0ff:fea8:5f0a/64 scope global dynamic flags 100 valid_lft 3435sec preferred_lft 1635sec inet6 fe80::42:c0ff:fea8:5f0a/64 scope link valid_lft forever preferred_lft forever My containers are connected to a different VLAN, hence the /64 is not quite the same. But I have local-only IPV6 prefix for my LAN for intersite VPN traffic, and the fact that my ISP gives out a dynamic IPV6 prefix the dynamic ipv6 prefix makes it hard to run docker with network settings defined, thus making me use SLAAC more efficiently - it doesn't help that my router is a Maikrotik, which has other issues with IPV6 networks (lack of proper DHCPv6) Quote Link to comment
psychofaktory Posted February 9, 2022 Share Posted February 9, 2022 I use OPNsense as router. There DHCPv6 with Router Advertismenents is active. Fortunately, my provider has assigned me a fixed IPv6 prefix. For the Docker I would like to use static addresses. For testing I tried to reach the Docker from the router via ping. The Dockers are also in different VLANs. Here are the settings: Quote Link to comment
ken-ji Posted February 9, 2022 Share Posted February 9, 2022 Its not immediately clear what's wrong. If you do not set a static IPV6 address, Docker should assign one - so for testing, do that and see if the container is able to ping the router and vice-versa? I assume other devices in the VLAN have ipv6 working properly? Quote Link to comment
psychofaktory Posted February 9, 2022 Share Posted February 9, 2022 (edited) Yes, the other devices in the network are working without problems with IPv6 I have now taken out the fixed IP and set the router advertisements of the OPNsense from "Router Only" to "Assisted". The container has then also properly obtained an IPv6 address via DHCPv6 and SLAAC. [email protected]:~# docker exec syncthing ifconfig eth0 Link encap:Ethernet HWaddr 02:42:0A:0A:0A:0D inet addr:10.10.10.13 Bcast:10.10.10.255 Mask:255.255.255.0 inet6 addr: fe80::42:aff:fe0a:a0d/64 Scope:Link inet6 addr: 2a00:XX:XXX:1010::f/64 Scope:Global inet6 addr: 2a00:XX:XXX:1010:42:aff:fe0a:a0d/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2726 errors:0 dropped:0 overruns:0 frame:0 TX packets:2369 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:288585 (281.8 KiB) TX bytes:337658 (329.7 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:103 errors:0 dropped:0 overruns:0 frame:0 TX packets:103 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9928 (9.6 KiB) TX bytes:9928 (9.6 KiB) Pinging from Docker to the router via IPv6 is possible without problems (even with static IPV6 address). However, the other way around is not possible. Could it be that the container is missing the associated route? [email protected]:~# docker exec syncthing ip route default via 10.10.10.1 dev eth0 10.10.10.0/24 dev eth0 scope link src 10.10.10.13 Edited February 9, 2022 by psychofaktory Quote Link to comment
ken-ji Posted February 9, 2022 Share Posted February 9, 2022 the command to see IPv6 routes is "ip -6 route" what's odd is your router not being able to ping the docker. have you tried running a traceroute tool on your router, maybe the router route settings is not correct. or you have firewall rules? not really familiar with OPNsense Quote Link to comment
psychofaktory Posted February 9, 2022 Share Posted February 9, 2022 (edited) Thank You. "ip -6 route" shows [email protected]:~# docker exec syncthing ip -6 route 2a00:XX:XXXX:1010::/64 dev eth0 metric 256 fe80::/64 dev eth0 metric 256 multicast ff00::/8 dev eth0 metric 256 default via 2a00:XX:XXXX:1010::1 dev eth0 metric 1024 default via fe80::a236:9fff:fe21:80ea dev eth0 metric 1024 expires 0sec The ping from OPNsense was sent from the same Interface in which the docker container is. So no firewall should block here. Firewall is set to "Allow anything to anywhere" for testing. Ping6 from router to other clients works. Ping6 from other clients to router works. Ping6 from other clients to other clients works. Ping6 from router to Dockers on OPNsense doesn't work. Ping6 from router to OPNsene-host doesnt't work. Ping4 from router to OPNsense works. Ping4 from router to Dockers on OPNsense works. So it seems to be a problem with Unraid. what else have i missed? is there still a special setting that I need to set somewhere? Edit: I looked at the routing table of the OPNsense and realized that something must have been wrong here. After a restart of the OPNsense everything works now as it should! Edited February 9, 2022 by psychofaktory Solution found Quote Link to comment
HumanTechDesign Posted December 13, 2022 Share Posted December 13, 2022 (edited) I have a problem setting the following up: Instead of GUA (global routable addresses), I want to use ULA (local adresses from the fc00::/7 range as per RFC4193). I use an Opnsense with the docker containers on a separate VLAN (which creates a custom br0 in the format of br0.<VLAN>). For this VLAN, the ULA prefix has been set up in the firewall, advertising a custom IPv6 prefix (from the ULA range). I now want to use that prefix as the base for the IPv6 adresses generated for the containers using SLAAC. I have therefore setup the VLAN to use v4+v6 and v6 mode set to automatic. The network settings and docker manager correctly pick up the ULA range and gateway and the docker settings offer this as an ipv6 configuration for that VLAN (so far so good). However, when I now go to edit the container, the ipv6 range (which is correctly recognized by the settings page) is not shown next to the "Fixed IP address" entry field (different from the screenshot for example in the first post). The line --sysctl net.ipv6.conf.all.disable_ipv6=0 is added as an additional parameter. When starting the container (it is the pihole container with ipv6 activated in the environment variables), my router picks it up correctly but only reports the GUA (2000:... range). Therefore, apparently, no ULA but only a GUA was generated using SLAAC. Is this a container issue or an Unraid issue? Has anybody successfully implemented ULAs for the use by the docker service on Unraid? EDIT: Some screenshots as clarification EDIT: Nevermind - it actually DOES work with this configuration! Somehow, the ULA was just not showing up in my firewall NDP/MAC table. After pinging the container once more, it now picks it up correctly. For everyone looking for a solution to assign static local addresses via SLAAC to their containers on a separate VLAN here is quick walkthrough: Generate an ULA prefix (preferably actually random e.g. via some online tools) Enter the prefix as an advertised route for the interface in your router (in opnsense - and probably pfsense) this is done via a "Virtual IP" Configure Unraid's networking with automatic IPv6 on the VLAN interface with the docker containers (see above) - preferably turn off privacy extensions to generate "truly stable" addresses - however, I believe that this only affects the IPv6 adress of the interface in Unraid, not of the underlying docker containers Activate IPv6 networking in the docker settings for that interface (this should already show the new ULA prefix from your router prefilled!) add the line --sysctl net.ipv6.conf.all.disable_ipv6=0 as an additional parameter to the container add the line --mac-address xx:xx:xx:xx:xx:xx (with a MAC address of your choosing) as an additional parameter to the container (not sure if that is neccessary, but I wasn't sure if an update/restart of a container might generate new MAC address) Start the container Ping the container (or run something like ifconfig in the container) to find out the ULA of the container (should start with something like fc... or fd... - NOT the fe... address) Use that ULA as a stable IPv6 for that container Depending on the container, you might also run more arguments (e.g. environment variable or commands via the container console) to get full IPv6 support (e.g. in the pihole you would need to activate it via environment variables), but this depends on the container. Edited December 16, 2022 by HumanTechDesign Added guide for ULA Quote Link to comment
KluthR Posted December 19, 2022 Share Posted December 19, 2022 Hi I have two IPv6 enabled containers. They are fixed. I initially entered the prefix noted next to the br0 static IP field and added my own suffix. That worked. Until today. I restarted unraud and noticed those 2 containers were down. Starting them resulsts into a 403. Starting via CLI shows an "Address already in use" error. After some minutes, I realized, that my prefix changed and did not match the container fixed IPv6 anymore. Question 1: Any idea how to only set the host address for the v6 for cotainers? Without need to change the prefix anymore (if it changes?). Correcting the IP did not brought the 2 cotainers back to life. I dont have any idea whats going on: docker start npm Error response from daemon: Address already in use Error: failed to start containers: npm But the addresses arent in use: ss -tulpn doesnt show anything. Question 2: How to get further? Any ideas how to bring my containers back to life? I already deleted the container and image - no change. Thanks in advance! nas-diagnostics-20221219-2120.zip Quote Link to comment
KluthR Posted December 22, 2022 Share Posted December 22, 2022 On 12/19/2022 at 9:21 PM, KluthR said: Question 2: How to get further? No one? @mgutt Do you have any ideas/experience in that case? Quote Link to comment
mgutt Posted December 22, 2022 Share Posted December 22, 2022 On 12/19/2022 at 9:21 PM, KluthR said: After some minutes, I realized, that my prefix changed and did not match the container fixed IPv6 anymore. I think this isn't solvable: That's why my Nginx Proxy Manager is using the Host network and unRAID's Port are changed to 5000 and 5001. Quote Link to comment
KluthR Posted December 22, 2022 Share Posted December 22, 2022 Ok, that answers first question. No statement from Limetech about this? But my „Address already im use“ issue still remains. As soon as I enter any v6 IP I get this. Quote Link to comment
Recommended Posts
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.