Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Other [Enterprise Network] Unity hub is unable to get local issuer certificate

Discussion in 'Unity Hub' started by unity_446A6016EBBDAA94D839, May 31, 2023.

  1. unity_446A6016EBBDAA94D839

    unity_446A6016EBBDAA94D839

    Joined:
    May 31, 2023
    Posts:
    1
    Hello!

    My computer is behind a enterprise/business network, it is using a WSS agent instead of a proxy.

    I followed the guide for configuration of package manager.

    • Verify successful access to:
      • Test-NetConnection -Port 443 packages.unity.com
      • Test-NetConnection -Port 443 download.packages.unity.com
      • Test-NetConnection -Port 443 upm-cdn.unity.com
      • Test-NetConnection -Port 80 packages.unity.com
      • Test-NetConnection -Port 80 download.packages.unity.com
      • Test-NetConnection -Port 80 upm-cdn.unity.com
    • Create the "C:\ProgramData\Unity\config\upmconfig.toml" and the "unity_cert.pem".
    But it seems like it doesn't fix it. I still getting the following error:
    Code (JavaScript):
    1. D:\ideSoftware\unity\Unity Hub>
    2. Checking for update
    3. Found version 3.4.2 (url: UnityHubSetup.exe)
    4. Downloading update from UnityHubSetup.exe
    5. updater cache dir: C:\Users\SRT\AppData\Local\unityhub-updater
    6. Update has already been downloaded to C:\Users\SRT\AppData\Local\unityhub-updater\pending\UnityHubSetup.exe).
    7. Error occurred in handler for 'templates/getAllTemplates': [CombinedError: [Network] request to https://live-platform-api.prd.ld.unity3d.com/graphql failed, reason: unable to get local issuer certificate] {
    8.   graphQLErrors: [],
    9.   networkError: FetchError: request to https://live-platform-api.prd.ld.unity3d.com/graphql failed, reason: unable to get local issuer certificate
    10.       at ClientRequest.<anonymous> (D:\ideSoftware\unity\Unity Hub\resources\app.asar\node_modules\node-fetch\lib\index.js:1491:11)
    11.       at ClientRequest.emit (node:events:526:28)
    12.       at ClientRequest.emit (node:domain:475:12)
    13.       at TLSSocket.socketErrorListener (node:_http_client:442:9)
    14.       at TLSSocket.emit (node:events:526:28)
    15.       at TLSSocket.emit (node:domain:475:12)
    16.       at emitErrorNT (node:internal/streams/destroy:157:8)
    17.       at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    18.       at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
    19.     type: 'system',
    20.     errno: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY',
    21.     code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY'
    22.   },
    23.   response: undefined
    24. }
    25. [14512:0530/145915.534:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is disabled, ANGLE is
    26.  
    This is the upm-diagnostic-report
    Code (JavaScript):
    1. Unity Package Manager Diagnostics (v0.2.0)
    2. ============
    3. Ran 6 checks
    4. ============
    5. 2 succeeded
    6. 4 failed
    7. ============
    8. ❌ UPM registry reachable (FAIL)
    9. Make an HTTP request to the UPM package registry
    10. >> Connection error.
    11.  
    12. ❌ Ping UPM registry (FAIL)
    13. Measure the latency of the UPM package registry API
    14. >> No successful pings could be made in 5.184 seconds (22 failed)
    15.  
    16. ❌ Ping UPM download (FAIL)
    17. Measure the latency of the UPM package download endpoint
    18. >> No successful pings could be made in 5.206 seconds (18 failed)
    19.  
    20. ❌ UPM registry download speed (FAIL)
    21. Test the Internet connection using the UPM package registry
    22. >> Connection error.
    23.  
    24. ✅ HTTP proxy environment variables (PASS)
    25. Detect whether proxy-related environment variables are set (HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, NO_PROXY, UNITY_PROXYSERVER, UNITY_NOPROXY)
    26. >> No proxy support has been configured through environment variables.
    27.  
    28. ✅ UPM health check (PASS)
    29. Start the UPM process and call its health endpoint
    30. >> Server start duration: 2458.00 ms
    31. >> Server response duration: 549.40 ms
    32. >> Server response:
    33. >> {"status":"OK","nodeVersion":"v16.13.1","upmVersion":"v5.1.1"}