socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
toasthawaii
Newbie
Newbie
Posts: 2
Joined: December 10th, 2024, 2:20 pm

socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"

Post 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!!!

Image
User avatar
sander
Release Testers
Release Testers
Posts: 9258
Joined: January 22nd, 2008, 2:22 pm

Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"

Post 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.
User avatar
safihre
Administrator
Administrator
Posts: 5580
Joined: April 30th, 2015, 7:35 am
Contact:

Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"

Post 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.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
toasthawaii
Newbie
Newbie
Posts: 2
Joined: December 10th, 2024, 2:20 pm

Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"

Post 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.
Last edited by toasthawaii on December 12th, 2024, 3:21 pm, edited 1 time in total.
User avatar
sander
Release Testers
Release Testers
Posts: 9258
Joined: January 22nd, 2008, 2:22 pm

Re: socks5 proxy internal ipv4 error (unraid docker): Local IPv4 address Connection failed!"

Post 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.
Post Reply