I ran a scan last week on one of our webservers and got an A- report. I then tweaked the protocols/ciphers slightly and now when I run a scan I get the above error. Is this due to a misconfiguration on the server, or a problem with SSL Scan?
Thanks for the hostname. I fixed a bug in SSL Labs earlier today and, from what I can see, that fixed your problem. I will have the new version installed on the development server tomorrow for you to check it out.
I've only seen this once, and it was when I mangled the cipher list and hosed it up. I always check my cipher list *on the server the changes are being made on* using the openssl command, ala:
openssl ciphers -v 'ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4'
I can't tell you without knowing the hostname. Unexpected errors are a sign of unexpected/unusual behaviour that needs to be explicitly handled.
Thanks Ivan, is there any way to PM you the hostname for you to check it?
Great, thanks v much
Retrieving data ...