Stronghold Web Server known bugs

Bugs in Stronghold Web Server 2.4.2 build 2412

On some platforms, there is a problem with the shared memory session cache which can cause Apache's child processes to cause segmentation faults.

Recompilation of Stronghold Web Server can fail for some modules due to a bug in the Apache 'Configure' script. If you experience problems, we suggest that you upgrade to a later release of Stronghold Web Server, where this problem is known to be fixed.
Further information on recompilation is available from this FAQ

Using machine (client) certificates to a remote proxy-passed https server can fail on every other request. This is fixed in Stronghold Web Server 2.4.2.
After a client certificate has been authenticated, a different certificate can be sent on a subsequent request in the same session. This is fixed in Stronghold Web Server 2.4.2, or can be fixed by turning off the session cache.

On some platforms, when you start the installation it says it will install "Stronghold Web Server 2.4 Build Code 2406" rather than build code 2407. Ignore this message, and continue anyway. It will install build code 2407.
In the mod_status output (/stronghold-status) the value from the "SSL" column is missing, meaning that the values to the right of this column do not line up with the headings.
In the mod_status output, using /stronghold-status?help to display the key does not work.

Configuration manager defaults to making all Virtual Hosts use SSL.
CGI scripts do not terminate correctly when transfers are interrupted.
SSL_Require command is too restrictive, not allowing access to client-certificate protected directories when it should.
Some SSL environment variables sent to CGI scripts are sometimes blank.
Installation program does not allow SSL-only installations (for a work-around, select some unused port for non-SSL and then remove it from the configuration file later).