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
Describe the bug
Under some circumstances (re-config HTTP Proxy), switching to Global/WhiteList mode causes Chrome unable to visit any site while safari works perfectly fine. Chrome can only work in PAC mode in this situation.
To Reproduce
Open "HTTP Proxy Preference", Modify "HTTP Proxy Listen Address" to your outbound IP, and make sure "Follow Global Mode" is checked.
Switch to any other mode then switch back to Global/WhiteList.
Try to visit any website with Chrome, probably not working (But safari is still cool and calm)
Expected behavior
Chrome works in this situation.
System and Shadowsocksx-NG version: (please complete the following information):
OS Version: 10.14.6
Version 1.4.3-R8
Chrome Version: 80.0.3987.149
Root Cause
I Guess its because it uses the default http listen address '127.0.0.1' rather than the user-filled value when switch to global (and when enabled 'Follow Global')
Maybe here L165 (just searching around, didn't dive into it)
Workaround:
Uncheck "Follow Global Mode", then switch back to global
or Modify the System Web Proxy Server to match your outbound IP: (will be overwritten to default when switching mode)
(Probably because Chrome and Safari use different priority order when looking for available system proxies)
Describe the bug
Under some circumstances (re-config HTTP Proxy), switching to Global/WhiteList mode causes Chrome unable to visit any site while safari works perfectly fine. Chrome can only work in PAC mode in this situation.
To Reproduce
Expected behavior
Chrome works in this situation.
System and Shadowsocksx-NG version: (please complete the following information):
Root Cause
I Guess its because it uses the default http listen address '127.0.0.1' rather than the user-filled value when switch to global (and when enabled 'Follow Global')
Maybe here L165 (just searching around, didn't dive into it)
ShadowsocksX-NG/ShadowsocksX-NG/ProxyConfHelper.m
Lines 155 to 176 in 5cb98a1
The text was updated successfully, but these errors were encountered: