Solved: Invalid command ‘SSLEngine

Problem

Apache refuses to start prompting Invalid command 'SSLEngine'Error'

Cause of the problem

This frequently happens on fresh Apache servers. When Apache starts it reads through the configuration files. When it encounters SSLEngine directive, it considers it as unknown. This is caused by the fact that the server’s basic configuration does not have mod_ssl module installed or enabled.

Solution

On CentOS/RedHat systems

Run the following command to install mod_ssl

sudo yum install mod_ssl

On Ubuntu/Debian systems

Run the following command to enable the module:

sudo a2enmod ssl

SSL module should be enabled by now.

Got an article suggestion? Let us know

How to generate a private key for the existing .crt file on Nginx?

Unfortunately, this is not possible. You cannot generate a private key out of an existing certificate. If it would be possible, you would be able to impersonate virtually any HTTPS webserver.

Questions

Where to keep SSL certificates and private keys on Ubuntu and Debian?

To list all available CA SSL certificates run the following lines of code:

Questions

Solved: SSL_Error_rx_record_too_long

The usual cause is that the implementation of SSL on your server is not correct. The error is usually caused by a server-side problem which the server administrator will need to investigate.

Questions

How to verify SSL certificates on the command line?

To validate an SSL certificate you can use one of the following approaches, depending on the type of the certificate.

Questions

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.