SSL configuration issue in Apache 2.4

To enable the module, create a symbolic link pointing to it. As recommended by @ericP, restart your apache, depending on your distribution and configuration. For El Capitan, the file path is specified. In the configuration file, the mentioned line is uncommented by default. To verify, use an SSL analysis site such as Qualys’ SSL server test. The mutex file should use the default mechanism as per the configuration directive.


Solution 1:

Although I lack knowledge of Debian Squeeze, I suggest attempting the following options.

Attempt to establish a connection by employing the

reconnect

flag through openssl, which reuses the identical session five times.

openssl s_client -connect your.server.com:443 -state  -reconnect

Examine the result of your search for

Session-ID

and observe if it shows up as “Reused.

Other things to rule out:

  • Is it possible for you to substitute the genuine path instead of

    ${APACHE_RUN_DIR}

    and verify if it resolves the issue? It’s a long shot, but worth a try.
  • Exclude the possibility of the user running apache having write permissions to the

    ssl_*

    files mentioned earlier, although it is improbable.


Solution 2:


I was able to resolve the issue by mounting tmpfs on /dev/shm and substituting /dev/shm/apache for ${APACHE_RUN_DIR}.

grep shm /etc/apache2/mods-enabled/ssl.conf
#SSLSessionCache        shmcb:${APACHE_RUN_DIR}/ssl_scache(512000)
SSLSessionCache        shmcb:/dev/shm/apache_ssl_scache(512000)


Solution 3:

I’m facing a similar problem.

Upon executing the command, an error message of “unexpected message” appeared during the reconnection process.

However, when executed on the server, the command functions accurately and utilizes the existing sessions.

Currently, I do not possess a resolution for this matter.

Frequently Asked Questions