Henzyme

Hi, Thank you for filing a report. I was tempted to update to the beta to see if this has been resolved, but I haven't had the time to test things out recently. Currently on 7.0.1 and everything works fine there.

Hello, I had Downgraded down to 7.0.1 and the issue was fixed immediately, but then I recently just upgraded to 7.1.4 and the problem returned. Has anyone experienced this? I can't be the only person.

@eirizarry @Curtis777 @dgwharrison @feins I got mine to work. set AKAUNTING_SETUP=false I think because the container has setup variables, it's expecting setup to be false... Maybe not. But it worked for me.

Hello, I am experiencing a network connectivity issue when connecting to my Unraid server via WireGuard VPN. While I can successfully access the Unraid server itself (192.168.86.246), I cannot reach any other devices or Docker containers on my local network (e.g., 192.168.86.2:3000 for AdGuard, 192.168.86.3 for NGINX Proxy Manager, or other Docker containers with custom IPs). This issue started occurring after updating Unraid to version 7.1.2. My WireGuard VPN Manager is configured with "Local server uses NAT: No," and my router has a static route configured to direct traffic for the WireGuard subnet to the Unraid server. One thing I noticed in VPN manager is that the Remark for static routing doesn't recognize my Unraid address. I am pretty confident this needs to say Remark: configure your router with a static route of 10.253.0.0/24 to 192.168.86.246. I tried using AI to troubleshoot this and Gemini seems to think there's some monkey business going on with MASQUERADE, where the NAT setting is not working at all. Also same issue with NAT on: