Apache SSL error, requires Apache restart

[STek]

Hello,

I recently, within the past couple of weeks, ran into an issue that is taking down my website randomly/frequently. Upon restarting Apache, everything goes back to normal. This is now happening 2-3 times a day and I am not sure how I can go about tackling this issue.

Example URL:
https://mydomain.mydomain.com

Steps to reproduce the problem:
Random, looking for the cause

What is the expected behavior?
I should see the web site/login screen

What went wrong?
Timed out, cannot connect, potential cause in error log shown below

Did this work before?
Yes, has been working for years. There have been random occurrences that required Apache reboot, but they have been few and far between until recently.

OS Version: Windoss Server 2008
XAAMP: 3.2.1

Error Logs:
After research, the below SSL error seems to be a viable cause of these issues. There have been a few instances where this error did not occur prior to the issue, but it is with the vast majority. I found no other criteria matching with each failure, so it seems to point to this:
[ssl:error] [pid 2340:tid 1564] AH02032: Hostname 111.111.11.11 provided via SNI and hostname mydomain.com provided via HTTP are different.

Any and all input would be great!

Thanks!
-Michael

[STek]

Also, I am using Apache version 2.4

[STek]

Well I had a system lapse again that was resolved by restarting Apache. This time, however, there was nothing at all in the error log prior to it. Any ideas as to where I can begin my investigation? Doesn't seem to point to any single thing in the error log, including the http error as stated in my first post.

I do not see any trending or consistencies in the apache logs.

[JJ_Tagy]

Is your XAMPP server exposed to the internet? You should also look at your access log. Perhaps you are getting many scanning bots or others trying to find vulnerabilities.

[gsmith]

[ssl:error] [pid 2340:tid 1564] AH02032: Hostname 111.111.11.11 provided via SNI and hostname mydomain.com provided via HTTP are different.

This should only give out a 421 error (looking in the Apache source), not bring down Apache.

About that error, there's good info about the attack here
http://security.stackexchange.com/quest ... tname-prov

When Apache does not respond to https://mydomain.mydomain.com, try accessing it with the IP from the machine Apache's running on ie: https://127.0.0.1 (you should get a message from your browser about non matching certificate name).

If it responds when you access it this way, try looking again in your error log. Look for line/s stating something like "Asynchronous AcceptEx Failed" and "Network name no longer available".