Unable to establish a connection with SOCKS5 proxy using a IPv6 address using command line switches.
Reported by
cenda...@gmail.com,
Feb 27 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Start chrome using the SOCKS5 flags e.g chrome --proxy-server=socks5://[ip::v6]:1080 --host-resolver-rules="MAP * ~NOTFOUND, EXCLUDE [ip::v6]" 2. Browse to any website What is the expected behavior? Chrome should be able to successfully connect to and utilize the SOCKS5 proxy. What went wrong? I receive ERR_PROXY_CONNECTION_FAILED in response. Did this work before? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: 10.0 Flash Version: I have verified that my SOCKS5 setup is functional, that authentication is turned off, and tested that other extensions & clients can connect to and use the IPv6 SOCKS5 server. (e.g https://chrome.google.com/webstore/detail/proxy-helper/mnloefcpaepkpmhaoipjkpikbnkmbnic?hl=en works fine)
,
Feb 27 2018
,
Feb 27 2018
IPv6 literal brackets strike again! I suspect the problem is that instead of: --proxy-server=socks5://[ip::v6]:1080 --host-resolver-rules="MAP * ~NOTFOUND, EXCLUDE [ip::v6]" You want: --proxy-server=socks5://[ip::v6]:1080 --host-resolver-rules="MAP * ~NOTFOUND, EXCLUDE ip::v6" Since when applying the exclusion rules, it interprets it as a hostname (not a hostname:port).
,
Feb 28 2018
cendamos: Can you confirm if that fixed your issue?
,
Mar 8 2018
cendamos: friendly ping, can you respond to comment #4?
,
Mar 23 2018
Network triager here. Archiving this issue due to no activity in this thread. @report: feel free to reopen this issue if comment #3 doesn't fix your issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by susan.boorgula@chromium.org
, Feb 27 2018