Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2019.3.0a4
Issue ID
1165762
Regression
No
[Windows][Networking] Unity doesn't acknowledge the proxy exclusion list
Steps to reproduce:
1. Make sure your Windows PC is not on VPN
2. Go to proxy settings and set up everything like it is shown in "proxySettings.png"
3. Verify that proxy is working correctly by going to google chrome and typing following domains:
a) www.google.com - should work as expected because we added it to exclusion list
b) www.unity.com - should throw an error in chrome "There is something wrong with the proxy server, or the address is incorrect."
If your results are the same as above, then the proxy is set up correctly and you can proceed to step 4
If your results are not the same, read edit section
4. Open attached project "NoProxyIssue.zip"
5. Open "SampleScene" scene
6. Press Play
- Both requests fail ("www.google.com: Error: Cannot connect to destination host" & "www.unity.com: Error: Cannot connect to destination host")
Actual result: Unity doesn't acknowledge the exclusion list set up in Windows 10 proxy settings which results in both requests failing
Expected result: Unity should acknowledge the exclusion list and allow connection without a proxy to www.google.com (in this specific example)
Reproduced on: 2017.4.28f1, 2018.4.4f1, 2019.3.0a9
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2019.3):
The libCurl implementation for Windows was updated to pipe the proxy "Bypass List" from Windows IE configuration into Curl's "NOPROXY" option.
This functionality never existed for Unity's libCurl implementation, but apparently did exist way back when OpenSSL was being used.