Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2021.3.23f1
2023.1.0b13
2023.2.0a11
Issue ID
UUM-34399
Regression
No
“Curl error 56: Recv failure: Connection was reset“ connection error occurs arbitrarily when using UnityWebRequest.SendWebRequest
Reproduction steps:
1. Open the “CurlErrorStripped.zip” project
2. Open Test Runner and click “PlayMode”
3. Run the “UnityRestOperatorTests” test a few times
Expected result: The test passes every time
Actual result: The test fails sometimes with “Curl error 56: Recv failure: Connection was reset“ in Console
Reproduced in: 2021.3.23f1, 2023.1.0b13, 2023.2.0a11
Could not test in: 2020.3.47f1, 2022.2.16f1 (dependency errors)
Reproduced using: Windows 10 (by reporter), Windows 11
Not reproduced using: macOS 13.2.1 (Intel)
Notes:
1. Test fails more often in 2021.3 (~50%) than in 2023.2 (~10%)
2. Also reproduced in a test Player
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:
I was only able to reproduce it once despite a lot of attempts using latest 2021.3.
This error mean an issue in the connection between server and Unity. It occasionally happens, network is not 100% reliable. Without a repro that gives a high failure rate, I don't see an issue here.
For testing purposes it is advised to run test server on the same machine, so that networking problems don't affect the tests.
Resolution Note (2023.2.X):
I was only able to reproduce it once despite a lot of attempts using latest 2021.3.
This error mean an issue in the connection between server and Unity. It occasionally happens, network is not 100% reliable. Without a repro that gives a high failure rate, I don't see an issue here.
For testing purposes it is advised to run test server on the same machine, so that networking problems don't affect the tests.