Unable to sign in: unable to verify the first certificate

[Consequences]

I'm having issues getting the application to connect to our Storage accounts. I added our internal root CA (which is used to MitM intercept HTTPS traffic that passes through our transparent proxy) but I still get the same error when I try to connect.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 06b6cadc-f93d-75de-7611-b1e3d80917e2
• Version Independent ID: bcf194d8-3442-b284-576f-407af9ca1067
• Content
• Content Source
• Service: virtual-machines

[Consequences]

C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\applicationinsig…:20 ApplicationInsights:Sender
[Error: unable to verify the first certificate at TLSSocket. (_tls_wrap.js:1088:38) …]
0
:
Error: unable to verify the first certificate at TLSSocket. (_tls_wrap.js:1088:38) at emitNone (events.js:86:13) at TLSSocket.emit (events.js:188:7) at TLSSocket._finishInit (_tls_wrap.js:610:8) at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
code
:
"UNABLE_TO_VERIFY_LEAF_SIGNATURE"
message
:
"unable to verify the first certificate"
stack
:
"Error: unable to verify the first certificate↵ at TLSSocket. (_tls_wrap.js:1088:38)↵ at emitNone (events.js:86:13)↵ at TLSSocket.emit (events.js:188:7)↵ at TLSSocket._finishInit (_tls_wrap.js:610:8)↵ at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)"
proto
:
Object

[Consequences]

I was able to fix this using the Edit > Certificates > Import drop down. Once I added the root CA, and intermediate CA certificates it worked.

[amanarneja]

Great that you figured it out and are now unblocked!
I am assigning this to the author to see if this will be a good scenario to add to the troubleshooting guide.

[cynthn]

@amanarneja can you remove the virtual-machines label and add storage instead? Thank you!

[sluhn-woodrum]

Using latest build of storage explorer (1.5.0), curious why on Win10 you must install Visual Studio (Azure SDK) to be able to authenticate to AAD and see your storage accounts. Not an issue on Win7. Issue occurs with both MFA and non-MFA AAD accounts. Same user experience as above issue noted on sign-in flow stuck. Install Visual Studio, authenticate to Azure, and then storage explorer works. I'd prefer not to have to roll out VS to users just to access storage explorer. Thanks.