strannik

hey hey! trying to improve my setup at home by adding nginx proxy manager. not interested in ipv6, public access or anything like that. i have most of my containers running on bridge and i have been accessing them on a bunch of different ports. lets take searxng as an example: 192.168.0.5:8082. 192.168.0.5 is my unraid host. i have now npm running on br0 as 192.168.0.6. i have a pihole running on a pi and setup searxng.local to point to 192.168.0.6. works fine, get the greeting page. then i setup in npm the proxy host and point it to 192.168.0.5:8082. but then i get 502 bad gateway. i saw in the first page that containers running on br0 cannot reach host ports. why is that? ok, i understand that its a limitation of macvlan. so i think the easiest option for me would be to get a second nic for server and have npm use that one for itself. then i can target the original ip of my unraid box, right?

having an issue with PIA: DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' [info] 10 retries left [info] Retrying in 10 secs... is this something you’ve seen already?

Would it be possible to add in wireguard vpn support to this image? Thanks!