Open koedx opened 11 months ago
Just a wild guess, try it with --no-tcp-fastopen
. Because wget2 tries to connect to that IP and sees this General error
. On the other hand side, TFO didn't change in a long time.
Btw, what version of wget2 are you using?
Maybe you can help me to reproduce. Currently, proxychain4 on Debian testing doesn't seem to work. I tried a bunch of proxies, adding with http ip port
to /etc/proxychains4.conf
.
All I ever get is a timeout
[proxychains] Strict chain ... <ip>:<port> ... timeout
wget2 -V
:
GNU Wget2 2.1.0 - multithreaded metalink/file/website downloader
+digest +https +ssl/gnutls +ipv6 +iri +large-file -nls -ntlm -opie -psl -hsts +iconv +idn2 +zlib -lzma +brotlidec +zstd -bzip2 -lzip +http2 +gpgme
I tried running w/ --no-tcp-fast-open & the general error persists.
Regarding proxychains4 issues you mention, the "original" proxychains4 (although still in the repos) is unmaintained. The maintained version/package should be installed via apt-get proxychains-ng
(v. 4.16, the GitHub repo for that package is linked below). Is this the proxychains4 you are running? (if not, installing the -ng package should address the timeout issues you experienced). I can confirm that the -ng package proxifies current versions of curl & wget w/o issue (for me).
I am trying to understand why wget2 fails to connect when being run through proxychains-ng. Prior versions of wget2 (& current versions of curl & wget) work as expected.
Running
proxychains4 wget2 -d --no-dns-cache --no-local-db --no-check-certificate --progress=none -O - "http://google.com"
produces:wget2 acquires the "dummy" ip from proxychains-ng (the 224.x.x x address) as expected (the "has" output above). At this point things seem to go wrong with wget2 (wget or curl connect to that ip & successfully download the requested page; wget2 always fails... I am using google in the posted example, but the issue exists no matter what url I attempt to connect to).
When I use wget2 w/o proxychains, after the provided host url is resolved to an IP ("has" x.x.x.x), wget2 connects to said ip (& outputs "try" x.x.x.x to indicate this).
Why isn't wget2
try
ing to connect to the provided ip when invoked thru proxychains-ng??Any guidance in troubleshooting this issue would be much appreciated 🙏