Page 1 of 1

Problem with local ranges when using Wireguard

Posted: September 30th, 2023, 10:00 am
by palim
Hello,
I am running Sabnzbd in version 4.1.0 in a docker container without any issues.

For easy access I configured local ranges to my network: 192.168.0.0/24. When I want to access the web UI I do not have to enter login credentials. Fine :)

Now I am away from home and want to connect me with a Wireguard VPN connection to the web UI. I had modified my local ranges to 192.168.0.0/24, 10.8.0.0/32 before and recreated the Sabnzbd container. The second IP range is for my Wireguard network.

But when I now try to access the UI I have to enter login credentials. What I am doing wrong? ???

Thanks in advance :)

Regards,
palim

Re: Problem with local ranges when using Wireguard

Posted: September 30th, 2023, 11:33 am
by jcfp
palim wrote: September 30th, 2023, 10:00 amNow I am away from home and want to connect me with a Wireguard VPN connection to the web UI. I had modified my local ranges to 192.168.0.0/24, 10.8.0.0/32 before and recreated the Sabnzbd container. The second IP range is for my Wireguard network.
For starters, that 10.8.0.0/32 seems unlikely in this case as that entire range contains only a single IP address. Either fix that (you probably intended a /24 there?), or clear out the local ranges setting altogether to revert back to the default that allows all typical local area network address ranges.