The site was switched to HTTPS (secure) a couple of weeks ago, and that went very well. Until today, not a single report of issues with insecure connections had been received from anyone. In fact, not even a comment on the change - maybe most people did not even noticed that little green padlock icon at top left in their browser...
BUT: a member reports today that Avast keeps giving this message;
This site can’t provide a secure connection
www.gt-rider.com uses an unsupported protocol. The client and server don't support a common SSL protocol version or cipher suite. This is likely to be caused when the server needs RC4, which is no longer considered secure.
Virus-free. www.avast.com
Qualsys SSL Labs server tests give us an "A" Grade...
As well as HTTPS/SSL on Gt-Rider, we also serve content via Cloudflare: - SSL set to "Strict"
- so maye that is where Avast get tripped up
Symantic Antivirus/Internet Security reports a correctly installed SSL/TLS certificate.
Bitdefender Internet Security has no issues with the site
AVAST has been known to have issues in accurately processing SSL information in the past, especially when combined with Firefox browser. The 2105 release caused a lot of problems - the solution at that time was;
"Users who experience issues after installing the latest version of Avast 2015 have two options:"
BUT: a member reports today that Avast keeps giving this message;
This site can’t provide a secure connection
www.gt-rider.com uses an unsupported protocol. The client and server don't support a common SSL protocol version or cipher suite. This is likely to be caused when the server needs RC4, which is no longer considered secure.
Virus-free. www.avast.com
Qualsys SSL Labs server tests give us an "A" Grade...
As well as HTTPS/SSL on Gt-Rider, we also serve content via Cloudflare: - SSL set to "Strict"
- so maye that is where Avast get tripped up
Symantic Antivirus/Internet Security reports a correctly installed SSL/TLS certificate.
Bitdefender Internet Security has no issues with the site
AVAST has been known to have issues in accurately processing SSL information in the past, especially when combined with Firefox browser. The 2105 release caused a lot of problems - the solution at that time was;
"Users who experience issues after installing the latest version of Avast 2015 have two options:"
- Disable HTTPS Scanning.
- Uninstall Avast completely.
