You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SOCKS5 Proxies are not supported at the moment. In addition Wired Client 2.5 (56) does not respect the macOS system proxy setting.
Steps to Reproduce
Create a Bookmark that requires the use of a SOCKS5 proxy to be reached.
Try connecting to the bookmark's connection.
The connection fails.
Expected Results
I'd like to see SOCKS5 proxy support with a per-bookmark scope. (Allowing different proxy settings for different connections.)
Actual Results
The connection can fail for different reasons:
Wired is not able to resolve the hostname since the DNS request is sent to the system resolver, which does no know about the private hostname, instead of going through the proxy.
The private hostname can be resolved but cannot be reached because the actual connection is not made through the SOCKS5 proxy.
Regression
n/a
Notes:
Bypassing the macOS system proxy settings is unexpected behaviour.
Version Information:
Wired Client 2.5 (56)
macOS 10.13.6
The text was updated successfully, but these errors were encountered:
Summary
SOCKS5 Proxies are not supported at the moment. In addition Wired Client 2.5 (56) does not respect the macOS system proxy setting.
Steps to Reproduce
Expected Results
I'd like to see SOCKS5 proxy support with a per-bookmark scope. (Allowing different proxy settings for different connections.)
Actual Results
The connection can fail for different reasons:
Wired is not able to resolve the hostname since the DNS request is sent to the system resolver, which does no know about the private hostname, instead of going through the proxy.
The private hostname can be resolved but cannot be reached because the actual connection is not made through the SOCKS5 proxy.
Regression
n/a
Notes:
Bypassing the macOS system proxy settings is unexpected behaviour.
Version Information:
The text was updated successfully, but these errors were encountered: