Apache 2 SSL input read failed

Posted January 31, 2014 24.5k views
Hello everyone, I have configured in my Debian 7 droplet the Apache 2 web server with a SSL enabled virtual host. The host seems to serve the content properly (it's a small sample HTML) but I keep getting these errors in error-ssl.log: [info] [client] Connection to child 8 established (server :443) [info] Seeding PRNG with 656 bytes of entropy [info] Initial (No.1) HTTPS request received for child 8 (server :443) [info] [client] (70007)The timeout specified has expired: SSL input filter read failed. [info] [client] Connection closed to child 8 with standard shutdown (server :443) Anyone knows how is "The timeout specified has expired: SSL input filter read failed." message caused? I have been searching all over the place for this, and it seems that people have a totally different configuration than mine. Any ideas?
1 comment
  • Thanks for posting! Possibly you have since found a solution that you wish to share?

    This problem has been encountered by others, including myself. Though the referenced log entries are of the “[info]” type, and not “warn” or “error”, they DO NOT appear to be “Clean” log entries. If you turn up the log level, there are probably more!

    Hopefully someone will offer more information, and if a significant problem, provide a solution. If these log entries are common to all, and somehow “normal”, I would like to hear that too. My other servers do not generate these messages.

    It seems that many aspects of SSL (ssl_module/“SSL Module”) are buggy? Especially if a load balancer or some other proxy is involved.

    It is exceedingly difficult to find quality information and tutorials regarding the virtual hosting configuration, especially “named” hosting. Most examples are far too minimal, and have been provided by laypersons. What’s greatly needed is a well developed set of coordinated server configs developed by Apache or some other authoritative source, which include: http-vhost.conf; https-vhost.conf; hosts; and ports.conf files.

    The problems associated with the log entries posted above probably involve these configurations files. If not, then there is a deeper problem!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
3 answers
"I have configured ... the Apache 2 web server with a SSL ...."

Did you follow a guide, when you did that? If so, which one?
I haven't followed a specific guide. I just enabled the SSL virtualhost and setup my Certificates according to standard procedure. The next steps was to strengthen SSL security by following this guide:

Has anyone stumbled in this message before? It is categorized under info, but it is clear that something is wrong.

We are facing the same issue. We have configured apache with Ssl as a proxy to backend services, The timeout issue occurs randomly without any specific pattern and the configuration of KeepAlive is also of no help (MaxKeepAliveRequests etc).

Has anyone found the solution to it ?