I can't stand it anymore! secure connection failed

[longernohuman]

"Secure Connection Failed
An error occurred during a connection to vndb.org.
Cannot communicate securely with peer: no common encryption algorithm(s).
(Error code: ssl_error_no_cypher_overlap)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site."

I had this problem for months!
I can only solve it by using browsec,

What causing this? and how to solve it completely?

 

[LittleFlame]

Try asking in the Ask! part of the forum i'm sure that'll gain more traction

 

[raulpica]

Which OS and Web Browser do you use?

 

[rctgamer3]

"Secure Connection Failed
An error occurred during a connection to vndb.org.
Cannot communicate securely with peer: no common encryption algorithm(s).
(Error code: ssl_error_no_cypher_overlap)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site."

I had this problem for months!
I can only solve it by using browsec,

What causing this? and how to solve it completely?

This is clearly a Firefox question although your OS used is still unknown. vndb.org works just fine for me. Have you ever tweaked any of the settings related to TLS/SSL on either the preferences page or about:config?

 

[Veho]

Google says the following:

The site only works for me if I allow Firefox to fallback to TLS 1.0 or otherwise force TLS 1.0 (i.e. set the maximum to 1.0)

In order to change your Firefox Configuration please do the following steps :

• In the Location bar, type about:config and press Enter. The about:config "This might void your warranty!" warning page may appear.
• Click I'll be careful, I promise! to continue to the about:config page.
• Change

security.tls.version.fallback-limit = 1

Alternatively, limit the fallback to only vndb.org:

The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases or may be using a deprecated cipher suite. You can open the about:config page via the location/address bar and use its search bar to locate this pref:
security.tls.insecure_fallback_hosts
You can double-click the line to modify the pref and add the domain (vndb.org) to this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). You should only see domains separated by a comma in the value column.

Also,

https://www.fxsitecompat.com/en-CA/versions/36/


Hope this helps.

 

[rctgamer3]

chunk of text

Hope this helps.

@Veho There's nothing wrong with the site in terms of the certificate and the used SHA2 ciphers thus OP should not downgrade his TLS version and sacrifice security just because he no longer has a cipher that matches. Why this happens, no idea, but i suspect some modified pref and/or an old Firefox version.

 

[longernohuman]

Try asking in the Ask! part of the forum i'm sure that'll gain more traction

Take a look at internet and web questions!

Which OS and Web Browser do you use?

windows 7, firefox.

This is clearly a Firefox question although your OS used is still unknown. vndb.org works just fine for me. Have you ever tweaked any of the settings related to TLS/SSL on either the preferences page or about:config?

no.

Google says the following:



Alternatively, limit the fallback to only vndb.org:



Also,

https://www.fxsitecompat.com/en-CA/versions/36/


Hope this helps.

Thank you.
but there's nothing by the name of: security.tls.version.fallback:

@Veho There's nothing wrong with the site in terms of the certificate and the used SHA2 ciphers thus OP should not downgrade his TLS version and sacrifice security just because he no longer has a cipher that matches. Why this happens, no idea, but i suspect some modified pref and/or an old Firefox version.

Yes, version 12.0

 

[migles]

he, is your date and time correct on your computer device?

 

[Veho]

Thank you.
but there's nothing by the name of: security.tls.version.fallback:

Yeah, the solution is for when the version is too recent, not too old

I suppose updating the browser is out of the question?

 

[longernohuman]

he, is your date and time correct on your computer device?

Yes.

Yeah, the solution is for when the version is too recent, not too old

I suppose updating the browser is out of the question?

You can say that!

But like I said, I can solve it by using google chrome! but what annoys me is that the problem even in tor browser!
I guess tor rely on firefox or something, right? if I upgraded firefox, would the problem solve in tor too?

 

[migles]

I guess tor rely on firefox or something, right? if I upgraded firefox, would the problem solve in tor too?

tor browser is a slightly modified version of firefox.
you can however setup tor and use chrome through tor

 

[rctgamer3]

Yes, version 12.0

There's your problem. Firefox 12 is four years old (why haven't you upgraded yet?) and doesn't seem to support TLSv1.1 and TLSv1.2, hence why it borks on vndb.org which requires a browser that supports TLSv1.2. Also, by using an ancient version you're vulnerable to many vulnerabilities such as Logjam, POODLE and FREAK.
Also, the booleans security.ssl3.dhe_dss_aes_128_sha and security.ssl3.dhe_dss_aes_256_sha are set to false. Having these (set to) disabled is also very insecure.