Page 1 of 1
socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"
Posted: December 10th, 2024, 2:38 pm
by toasthawaii
hi, i am running the binhex repo of sabnzbd as docker in unraid. everything worked like a charm until I enabled socks5 from PIA.
downloads still work, but I get this red error message now and wonder what could be causing it. I pinged my local network from within the docker and vice versa. all good.
what`s up and how can I debug?
please tell me what kind of logs are needed for hopefully more knowledgeable people here in the forums. happy to provide as much info as I can.
thanks a lot!!!
Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"
Posted: December 10th, 2024, 4:10 pm
by sander
Weird. Because the code for determining the Local IPv4 Address does not use any SOCKS stuff. And there should be no SOCKS involved: the local LAN ip address does not need SOCKS.
https://github.com/sabnzbd/sabnzbd/blob ... y#L94-L104
Can you go into the SABnzbd docker, run python3, with the code?
Code: Select all
$ python3
Python 3.12.3 (main, Nov 6 2024, 18:32:19) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> with socket.socket(socket.AF_INET, socket.SOCK_DGRAM) as s_ipv4:
... s_ipv4.connect(("10.255.255.255", 80))
... ipv4 = s_ipv4.getsockname()[0]
...
>>> ipv4
'192.168.1.102'
>>>
Unraid, so #UnraidAlert, although in this case I doubt Unraid is causing the problem.
Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"
Posted: December 11th, 2024, 10:24 am
by safihre
Or maybe just download the logs?
Enable Debug logging in that window and hit the refresh icon.
Click Show Logging to see the logs.
Does the actual downloading work? Because the Internet Bandwidth test seems to work fine.
Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"
Posted: December 12th, 2024, 1:41 pm
by toasthawaii
hi, thanks for the response and sorry for the late reply. it is indeed strange. any help is kindly appreciated!
many thanks in advance
edit: and yes, download works. it is way slower though than expected. also without socks5, but that might be a different issue.
Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"
Posted: December 12th, 2024, 2:59 pm
by sander
@toasthawaii I don't a reply a reply to my request?
@safihre local_ipv4() does not do logging, so what are you looking for?
The "good" news: I found a public socks5 server (socks5://143.244.166.232:26273 ... not too reliable), put it in a plain SABnzbd (no unraid, no docker), and it all works:
SOCKS5 Proxy 143.244.166.232:26273
Local IPv4 address 192.168.1.102
Public IPv4 address 143.244.166.232
The same with SABnzbd LSIO sabnzbd: all good:
SOCKS5 Proxy 143.244.166.232:26273
Local IPv4 address 172.17.0.3
Public IPv4 address 143.244.166.232
With binhex SABnzbd: all good
SOCKS5 Proxy 143.244.166.232:26273
Local IPv4 address 172.17.0.3
Public IPv4 address 143.244.166.232
So: problem specific to OP / Unraid / proxy?
Now the real question to OP: why do you want to use a proxy? With SSL set, a VPN or proxy is not needed.