socioeconomic-forecast2975

So traffic entering the npm docker can't reach my local network? But can it reach other containers?

What's the problem with br0?

Internet->npm->docker As I mentioned I have a few things which need outside acces, like game servers. But I updated the npm docker and it started working again fortunately.

Hi everyone! I have a strange issue with my NPM setup. It was working fine for many months, but since the integration of Tailscale to Docker, I have accessed my services less through it. Yesterday I tried to do it and got an error 504 after the Cloudflare access authentication. (clearification: I use tailscale integration for docker only I acces remotely, but for those which need normal remote acces i have a reverse proxy setup) Looked it up, and found that the issue is between the nginx proxy manager docker and the other docker containers. Tried a lot of troubleshooting, both using the forums, Reddit, and AI. But nothing worked and I feel lost. My setup is: domain through cloudflare Cloudflared docker updating the ip Unraid server running 7.1.4 on .18 ip addreess docker is using the macvlan network type Host access to custom networks disabled NPM container using the official image from the CA store using br0 network with a .11 ip address listening on the default ports of 80 and 443 Router forwarding ports 80, 443 from the wan to the NPM So far I've tried: curl/ping the containers from the npm container with the result of host unreachable changing to ip vlan network type toggling the host access to custom networks option I don't know what else I can try or what might be causing the issue. I also can't pinpoint when the issue started. The only thing I changed recently in my setup was a managed network switch, but that's 1gig and my server sits on the 2.5G one, so I don't think that causes the issue. If anyone has any ideas, I'm all ears!

Thank you! This was the issue. Though I had the bond as an active backup.

Hi I'm trying out Unraid and have a USB NIC which did not show up. So I installed the drivers and rebooted and it showed up. Then I changed it to be eth0 and rebooted again. The onboard NIC is set up as a fall back. When I have the 2.5G nic plugged in I can't acces the server, but when I unplug it I can acces it. (I still can't acces it if I have the onboard NIC unplugged) I'll attach my diagnostics. test-server-diagnostics-20230808-1045.zip