5

I am trying to validate my website on W3C Nu Html Checker but I am getting below error, don't know why?

IO Error: handshake alert: unrecognized_name

IO Error: handshake alert: unrecognized_name

While my website is working fine on SSL.

I tried Handshake alert: unrecognized_name error , but no help.

any guidance how to fix this much helpful. I didn't have that much knowledge of server.

Community
  • 1
  • 1
urfusion
  • 5,528
  • 5
  • 50
  • 87
  • Please add a link to your website. –  Nov 07 '15 at 08:41
  • check the updated `W3C` link – urfusion Nov 07 '15 at 08:45
  • 1
    See [this answer](http://stackoverflow.com/a/14884941/19068) — "certain misconfigured servers send an "Unrecognized Name" warning in the SSL handshake which is ignored by most clients... except for Java" — You would need to fix the misconfiguration of your server. – Quentin Nov 07 '15 at 13:31
  • "AWS EC2" by itself doesn't mean anything. The *web server software* is the crux, not your hosting provider. – deceze Nov 09 '15 at 08:14
  • okay,But my ssl is working fine, and I am not facing any issue. – urfusion Nov 09 '15 at 08:15
  • @urfusion "*... which is ignored by most clients*", which is why it appears to be "working fine". – melpomene Nov 09 '15 at 08:16
  • and as per the above answer link http://stackoverflow.com/a/14884941/19068. this issue is for java : ` "Unrecognized Name" warning in the SSL handshake which is ignored by most clients... except for Java. ` – urfusion Nov 09 '15 at 08:16
  • 2
    To spell it out: Java, and mostly only Java, has a problem with connecting to servers which send an "unrecognised name" in the SSL handshake. The W3C service is likely written in Java. Your web server sends out an "unrecognised name" warning. Result: The W3C service cannot connect to your server. The solution: fix your server to not send this warning/fix its configuration. How to do this we cannot tell you since we know zilch about your web server. – deceze Nov 09 '15 at 08:53
  • I am working on solution second because there is no other option – urfusion Nov 09 '15 at 09:15
  • 1
    any guidance how to fix this much helpful. I didn't have that much knowledge of server. – urfusion Nov 09 '15 at 09:17
  • 1
    Maintainer of the W3C HTML Checker here. The backend of the service is indeed written in Java, using the current Apache Commons HTTP client library. The exception this is coming from is thrown by that code, I don't know of any way to call that code differently that would cause it to be less strict like other clients and ignore the broken non-standard behavior of your server. So I have no way to workaround or prevent this on the W3C service side. – sideshowbarker Dec 12 '15 at 08:27
  • I'm also having same problem, but no useful answer – Kashif Latif Sep 21 '17 at 07:36
  • 1
    @KashifLatif : Check your server configuration and add `servername and serveralias` in your default-ssl – urfusion Sep 21 '17 at 08:40
  • @urfusion: should I contact to hosting provider for it? – Kashif Latif Sep 21 '17 at 09:56
  • you can or you can try https://stackoverflow.com/questions/46068660/images-not-showing-on-twitter-error-fetching-the-page-failed-because-the-requ – urfusion Sep 21 '17 at 10:45

0 Answers0