Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.39f1
2022.3.33f1
6000.0.4f1
Issue ID
UUM-73839
Regression
No
[Android] Error "Curl error 60: Cert verify failed. Certificate is not correctly signed by a trusted CA. UnityTls error code: 7" when using UnityWebRequest to connect to the server with a self-signed certificate
Reproduction steps:
1. Extract the attached folder “ReproSetUp“
2. Open the Git Bash and navigate to the “\RepoSetUp\NodeServ\Certs“
3. Enter “openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes”
4. Fill in the fields as instructed and make sure to put your machine’s local IP in Common Name
5. Run “NodeServ\Launch.bat”
6. Open the [https://localhost:8000/|https://localhost:8000/] in browser (you should get a privacy error warning)
7. Open the attached project “\RepoSetUp\TestUWP2021”
8. Open the “Test.cs“ script
9. At line 18, enter your IP address (StartCoroutine(GetRequest("[https://<put-ip-here>:8000|https://192.168.8.122:8000]"));)
10. Install “cert.pem” on an Android device
11. In Editor, switch to Android Platform
12. Build and Run on an Android device
13. Open the Android LogCat window
14. Put two fingers on the screen to trigger the UnityWebRequest
15. Observe the Android LogCat
Expected result: No Errors exist
Actual result: Error “Curl error 60: Cert verify failed. Certificate is not correctly signed by a trusted CA. UnityTls error code: 7“ is present
Reproducible with: 2021.3.39f1, 2022.3.33f1, 6000.0.4f1
Reproducible on:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
- Crash on Object::GetCachedScriptingObject when entering Play Mode
Add comment