Page 1 of 1
Using local_ranges and Sonarr cannot connect
Posted: October 14th, 2022, 12:29 am
by smcoz
I have set up local_ranges so that I can connect from outside my local lan using a tailscale connection. With local_ranges set I can access the web gui from the tailscale ip but Sonarr and Radarr can no longer connect to sabnzbd. All are running in docker on the same host.
I have local_ranges set as follows:
Code: Select all
192.168.1.0/24, 100.xxx.xxx.xxx/32
with 100.xxx.xxx.xxx being the tailscale IP
The SABnzbd host is set as :: and External internet access is set to "no access"
The error returned in Sonarr and Radarr is:
Code: Select all
Test was aborted due to an error: Unable to connect to SABnzbd, HTTP request failed: [403:Forbidden] [GET] at [http://192.168.1.93:8080/api?mode=get_config&apikey=4031cfd8b9cf4ee6be54a0e2dee8cfe4&output=json]
I've digested as much of the wiki as my knowledge will allow so any advice is greatly appreciated.
Re: Using local_ranges and Sonarr cannot connect
Posted: October 14th, 2022, 2:10 am
by sander
Re: Using local_ranges and Sonarr cannot connect
Posted: October 14th, 2022, 5:12 am
by jcfp
smcoz wrote: ↑October 14th, 2022, 12:29 amThe error returned in Sonarr and Radarr is:
What does the (debug) logging on the sabnzbd end say when doing this?
Re: Using local_ranges and Sonarr cannot connect
Posted: October 14th, 2022, 9:45 pm
by smcoz
Thanks for the replies
Yes, this is a follow-on from my previous post where I was focussed on getting the webui working - wasn't sure whether to start a new thread or continue previous - apologies if I got it wrong.
Extract from the log:
Code: Select all
2022-10-15 12:25:31,432::INFO::[SABnzbd:1437] Starting web-interface on :::8080
2022-10-15 12:25:31,433::INFO::[_cplogging:213] [15/Oct/2022:12:25:31] ENGINE Bus STARTING
2022-10-15 12:25:33,008::INFO::[notifier:122] Sending notification: Warning - Refused connection from: ::ffff:172.20.0.1 [Readarr/0.1.0.1156 (ubuntu 20.04)] (type=warning, job_cat=None)
2022-10-15 12:25:33,008::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Readarr/0.1.0.1156 (ubuntu 20.04)]
2022-10-15 12:25:36,588::INFO::[_cplogging:213] [15/Oct/2022:12:25:36] ENGINE Serving on http://:::8080
2022-10-15 12:25:36,588::INFO::[_cplogging:213] [15/Oct/2022:12:25:36] ENGINE Bus STARTED
2022-10-15 12:25:36,589::INFO::[SABnzbd:1473] Starting SABnzbd.py-3.4.2
2022-10-15 12:25:36,596::INFO::[dirscanner:117] Dirscanner starting up
2022-10-15 12:25:36,597::INFO::[panic:239] Launching browser with http://127.0.0.1:8080/sabnzbd
2022-10-15 12:25:36,597::INFO::[postproc:233] Completed Download Folder /data/usenet is not on FAT
2022-10-15 12:25:36,599::INFO::[notifier:122] Sending notification: SABnzbd - SABnzbd 3.4.2 started (type=startup, job_cat=None)
2022-10-15 12:25:36,851::INFO::[notifier:122] Sending notification: Update Available! - SABnzbd 3.6.1 (type=other, job_cat=None)
2022-10-15 12:26:01,851::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Sonarr/3.0.6.1342 (ubuntu 18.04)]
2022-10-15 12:26:52,990::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Radarr/3.2.2.5080 (ubuntu 20.04)]
2022-10-15 12:27:03,019::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Readarr/0.1.0.1156 (ubuntu 20.04)]
2022-10-15 12:27:31,699::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Sonarr/3.0.6.1342 (ubuntu 18.04)]
2022-10-15 12:28:23,012::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Radarr/3.2.2.5080 (ubuntu 20.04)]
2022-10-15 12:28:33,035::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Readarr/0.1.0.1156 (ubuntu 20.04)]
2022-10-15 12:29:10,815::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Sonarr/3.0.6.1342 (ubuntu 18.04)]
2022-10-15 12:29:10,823::WARNING::[interface:370] Refused connection from: ::ffff:172.20.0.1 [Sonarr/3.0.6.1342 (ubuntu 18.04)]
Log from yesterday's attempt made reference to the tailscale IP (changed to 100.xx.xx.xx below):
Code: Select all
2022-10-14 15:23:29,093::INFO::[notifier:122] Sending notification: Warning - Refused connection from: ::ffff:100.xx.xx.xx [Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36] (type=warning, job_cat=None)
2022-10-14 15:23:29,093::WARNING::[interface:370] Refused connection from: ::ffff:100.xx.xx.xx[Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36]
I hope I've provided enough information.
As a side note, when connecting using a zerotier mesh network everything works as expected without the need for using "local_ranges" I think this is because zerotier adds additional network interfaces for each device which are then acting as a local network. I would rather use tailscale hence my troubleshooting efforts here.
Thanks again for your trouble.
Re: Using local_ranges and Sonarr cannot connect
Posted: October 15th, 2022, 3:27 am
by jcfp
The refusal for the *arr apps makes sense, as their connections come from ::ffff:172.20.0.1 (the weird looking ipv4-mapped ipv6 equivalent of simply '172.20.0.1') which isn't part of the configured local_ranges (192.168.1.0/24, 100.x.x.x/32).
The tailscale ip should work though, provided whatever is set in the local ranges is actually an *exact* match.
Not familiar with zerotier but I suspect it's basically a proprietary vpn app handing out ip addresses in the usual private ranges that are accepted as local in sabnzbd by default.
On a side note: you do want to upgrade to the latest stable release, so we can at least eliminate any bugs fixed since 3.4.2.
Re: Using local_ranges and Sonarr cannot connect
Posted: October 16th, 2022, 9:36 pm
by smcoz
Thanks for the input. After thinking about it for a while I realised that I had overlooked the fact the 'arrs are connecting through 172.20.0.1 and with my knowledge of networking still developing had forgotten that this is a private IP. Adding this to the local ranges fixed the issue.
Also, I have updated to the latest version and confirmed that it wasn't a bug in the old version.
Thanks again for the help.