3 Adds blog post link
source | link

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

I should writeHere is a blog post I've written about this trickyvery setup / configuration within a few days, I'd report back a link to it here if so: link.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.


TL;DR

Try adding SetEnv nokeepalive ssl-unclean-shutdown to your VHOST configuration.

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

I should write a blog post about this tricky setup / configuration within a few days, I'd report back a link to it here if so.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.


TL;DR

Try adding SetEnv nokeepalive ssl-unclean-shutdown to your VHOST configuration.

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

Here is a blog post I've written about this very setup : link.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.


TL;DR

Try adding SetEnv nokeepalive ssl-unclean-shutdown to your VHOST configuration.

    Post Undeleted by Michael Hampton
2 sum it up
source | link

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

I should write a blog post about this tricky setup / configuration within a few days, I'd report back a link to it here if so.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.


TL;DR

Try adding SetEnv nokeepalive ssl-unclean-shutdown to your VHOST configuration.

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

I should write a blog post about this tricky setup / configuration within a few days, I'd report back a link to it here if so.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

I should write a blog post about this tricky setup / configuration within a few days, I'd report back a link to it here if so.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.


TL;DR

Try adding SetEnv nokeepalive ssl-unclean-shutdown to your VHOST configuration.

    Post Deleted by Michael Hampton
1
source | link

I've (finally) joined the StackExchange community to help you, as nobody has answered yet.
I was facing the same issue today, and it looked definitely related to the Apache SSL info we could notice within verbose logs :

[ssl:info] [...] The timeout specified has expired: [...] SSL input filter read failed.

So a "solution" (mostly a "workaround" IMHO) is proposed here.

I should write a blog post about this tricky setup / configuration within a few days, I'd report back a link to it here if so.

Bye 👋

PS : In my specific case, SetEnv nokeepalive sufficed.