Avatar for Username

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Secure Connection Failed for Nginx + Comodo PossitiveSSL While SSLlabs Score is A+

  • 4 replies
  • 3 have this problem
  • 26 views
  • Last reply by jcmtnez

jcmtnez
jcmtnez

I own the website https://vzinity.com which is running on Nginx and uses a Comodo PossitiveSSL cert.

I have tested the SSL installation at https://www.ssllabs.com/ssltest/analyze.html?d=vzinity.com and it gets an A+ score.

I have tested opening the site in many browsers but I only see this problem in Firefox. When I visit the website using Firefox 39 (Windows 7, Windows 8.1, Windows 10 and Linux Mint) I get the following error:

Secure Connection Failed

The connection to vzinity.com was interrupted while the page was loading. 

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem.

Any help will be appreciated.

Thanks.

I own the website https://vzinity.com which is running on Nginx and uses a Comodo PossitiveSSL cert. I have tested the SSL installation at https://www.ssllabs.com/ssltest/analyze.html?d=vzinity.com and it gets an A+ score. I have tested opening the site in many browsers but I only see this problem in Firefox. When I visit the website using Firefox 39 (Windows 7, Windows 8.1, Windows 10 and Linux Mint) I get the following error: Secure Connection Failed The connection to vzinity.com was interrupted while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Any help will be appreciated. Thanks.

Chosen solution

That looks like an issue with bad user agent sniffing.

It works for me if I change the 20100101 date in Gecko/20100101 in the user agent to something else (even Gecko/20100102 works, only Gecko/20100101 doesn't work).

  • Mozilla/5.0 (X11; Linux i686; rv:39.0) Gecko/39.0 Firefox/39.0

The server could be hacked to target only a Firefox user agent. You can contact the website and ask them to look into this.

Read this answer in context 👍 0

All Replies (4)

Jhp512
Jhp512

Hello,

I would recommend contacting the company that hosts your domain as well as the company that issues your SSL. This sounds like a DNS issue to me. Try contacting them and let me know what they say!!

Thank you

jcmtnez
jcmtnez Question owner

Thank you for the suggestion. I have contacted both but they don't see anything wrong.

Following your clue about the DNS I switched the nameservers temporarily in order to test with different settings but still Firefox 39 gives the same error.

cor-el
cor-el
  • Top 25 Contributor
  • Moderator

Chosen Solution

That looks like an issue with bad user agent sniffing.

It works for me if I change the 20100101 date in Gecko/20100101 in the user agent to something else (even Gecko/20100102 works, only Gecko/20100101 doesn't work).

  • Mozilla/5.0 (X11; Linux i686; rv:39.0) Gecko/39.0 Firefox/39.0

The server could be hacked to target only a Firefox user agent. You can contact the website and ask them to look into this.

jcmtnez
jcmtnez Question owner

That solved the problem!

A rule had been set in the server to stop temporarily spammers using a specific user agent. After removing the rule all is working well.

Thank you for helping.