Jump to content

Error: unable to verify the first certificate Help?


mrsmoore4u

Recommended Posts

every time i open the application it says failed to get access key


Details:



Error: unable to verify the first certificate

at TLSSocket.<anonymous> (_tls_wrap.js:1103:38)

at emitNone (events.js:106:13)

at TLSSocket.emit (events.js:208:7)

at TLSSocket._finishInit (_tls_wrap.js:637:8 )

at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:467:38)

Link to comment
Share on other sites

Where are you and what version Vortex are you running?

Any firewalls or VPN?

What antivirus?

First thing I would try is download a current Vortex installer package and reinstall it.

i just got vortex today not even an hour ago. my firewall is not blocking it and my antivirus isn't either as far as i am aware but i will try re-installing it

 

Edit: did not help im still getting the same error

Link to comment
Share on other sites

Could be of more help if we knew where you downloaded it from and what version it is.

Some certificate errors are temporary. Might try again tomorrow.

Google Certificate Error - it will give you some background on what is happening - and why.

 

 

i got it from nexus, version 0.17.11 (One-click installer)

Link to comment
Share on other sites

"unable to verify the first certificate" indicates a windows setup error.
What it's telling you is that the "chain of trust", which validates the api (or github) is actually the server they claim they are, is compromised.

The chain of trust is a series of certificates that vouch for each other and then windows contains a list of certificate authorities they say are trustworthy.
So you have trusted CAs vouching for intermediate certificates vouching for the certificate used to sign connections to the server.

And I can assure you: all servers Vortex connects to (our own api and github) have proper certificates that your system should be able to validate.

So there are a few things that could be happening here:
a) Your windows hasn't been updated in years and doesn't contain current CAs (I don't actually know how old it would have to be)
b) You have broken security software (AV, firewall, proxies or similar) that redirect the network connection without proper certification or they change the certification itself
c) You have manually modified the CA list
d) You have malware that redirects network connections Vortex tries to establish
e) You have malware that changed/removed certificate authorities

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...