asa666

This happened to me (on 7.2.4). Something had killed the docker network (check with docker network list). When I created another wg tunnel device (say wg1) it was then visible in the docker network list( via CLI and in the Edit page for docker containers). So try either creating a new one or deleting and recreating your wg0. Or recreate the docker network using docker network create. Good luck!

Thanks. It doesnt seem to be the same connectivity issues others are seeing, though. It's just that the macvlan shim seems to have stopped working

Hi there, After updating Unraid to 7.1.3 I cannot access the Unraid host address from a Docker container on br0. The shim-br0 link is up as normal: root@unraid:/boot# ifconfig shim-br0 shim-br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.250 netmask 255.255.255.0 broadcast 0.0.0.0 ether b6:3a:f4:e2:4d:78 txqueuelen 1000 (Ethernet) RX packets 206 bytes 20697 (20.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13 bytes 546 (546.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 For example, my Swag container runs on the custom: br0 network. It can no longer proxy to containers on the bridge network (returning 502). From within Swag (the 'console'), I cannot ping the host's IP address: root@unraid:/boot# docker exec -ti swag ping -c 2 192.168.0.250 PING 192.168.0.250 (192.168.0.250): 56 data bytes --- 192.168.0.250 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss Any ideas or advice would be greatly appreciated :) Thanks for reading! Unraid Diagnostics Jun 09 2025.zip