Hostname provided via SNI and hostname provided via HTTP have no compatible SSL setup

WorkinOnIt

• September 25, 2017 20:30

Hello As the title suggests; [ssl:error] AH02032 Hostname w provided via SNI and hostname example.com provided via HTTP have no compatible SSL setup I am seeing several of these types of errors in Apache error log. What could it mean? I read this link with interest. Should I be worried? Thanks

• 

  cPanelMichael

  • September 26, 2017 16:30

  Hello, The error message shows that the behavior was correctly blocked (thus you should not be concerned). The following third-party URL explains what Apache is protecting against by issuing the error: What kind of attack is prevented by Apache2's error code AH02032 ("Hostname provided via SNI and hostname provided via HTTP are different")? Thank you.

  0
• 

  WorkinOnIt

  • September 28, 2017 04:25

  Thank you Michael that makes sense. Consider this closed.

  0

Please sign in to leave a comment.