unfortunately I’m unable to Sign-in to my account using UnityHub v3.0.1.
I’m online in a company network where internet access is handled through a proxy server which repacks incoming HTTPS data with their own certificate.
I already added the certificates for the Proxy CA to my global configuration file (as described here: Unity - Manual: Solving network issues (unity3d.com))
In the Unity Hub log file I get the following error message:
Error: unable to get local issuer certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1497:34) at TLSSocket.emit (events.js:315:20) at TLSSocket.EventEmitter.emit (domain.js:467:12) at TLSSocket._finishInit (_tls_wrap.js:932:8) at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)
Were you able to solve this condition? We’re running into the same thing. We have been using the unity hub launch script to set the http_proxy and https_proxy environment variables before launching and tcpview confirms the application is reaching out through our proxy.
Adding onto this but may start a different thread discussing what I’ve found.
Hub 3.3.0 still works in our environment. Using the set proxy batch file to kick off Unity Hub, everything works Hub and Editor.
Once Hub updates to 3.4.1 it breaks. Seems no way to stop hub from updating and something definitely changed in the version that is affecting this SSL item.
This was fantastic and lead me to finding that it isn’t this value but rather NODE_TLS_REJECT_UNAUTHORIZED that you set to 0 or false.
Turns out the caFile Unity documents will replace the entire CA tree or so that’s what I’m reading on Node/NPM forums and posts. Using the environment variable to add Extra CA Certs into the chain doesn’t seem to have an impact or its being ignored.
Oops sorry, I made a typo when pasting the environment variable. Yeah, it’s NODE_TLS_REJECT_UNAUTHORIZED that’ll do the trick. Fixed. Glad it worked for you.
3.4.1 had a lot of changes in it so it is hard to say what might have caused this to break. In 3.3.0 we added a more robust support for using the Hub behind a proxy with self-signed certificates.
Could I get you to follow this guide and let me know if it works for you ?
Apologies from the hub team for the inconvenience.
Hi.
“Automated Proxy Detection” feature was added, but still downloads are happening without respecting proxy. So when proxy is specified there is still no way to download Unity editor.
After spending over 2 hours with my local network support team I created IN-56874 for this issue.
I seems that downloader (I suspect it is “node-downloader-helper” tool used by UnityHub - base on entry in info-log.json) goes directly to Akamai server (download.unity3d.com resolved to 2.21.22.162) and is not respecting defined proxy settings.
Unfortunately, it doesn’t work for Windows. I have the certificate authorities imported into Certificates (Local Computer)\Trusted Root Ceritfication Authorities\Certificates and starting Unity Hub 3.12.1 still produces “SELF_SIGNED_CERT_IN_CHAIN” errors.
I have also tried NODE_EXTRA_CA_CERTS=C:\ProgramData\Unity\config\cert.pem (the same file used by UPM as configured in upmconfig.toml) and that doesn’t work either
The only thing it respects is NODE_TLS_REJECT_UNAUTHORIZED=0