How To Fix "SSL Proxy Requested But Not Enabled" Error In Apache?

Adding the SSLProxyEngine directive

To fix the "SSL Proxy Requested But Not Enabled" error, add the SSLProxyEngine directive to your Apache configuration:

1. Open your Apache configuration file, usually at /etc/apache2/sites-available/your-site.conf or /etc/httpd/conf.d/your-site.conf.

2. Add the SSLProxyEngine directive inside the VirtualHost block that handles HTTPS connections:

SSLProxyEngine on

This directive enables SSL/TLS support for proxy connections.

apache2ctl -t -D DUMP_MODULES | grep ssl

Modifying the VirtualHost configuration

After adding the SSLProxyEngine directive, update your ProxyPass and ProxyPassReverse directives to use HTTPS:

1. Change the ProxyPass and ProxyPassReverse directives to use the HTTPS protocol:

ProxyPass /primary/store https://localhost:9443/store/
ProxyPassReverse /primary/store https://localhost:9443/store/

2. Make sure the port number (9443 in this example) matches your backend server's HTTPS port.

3. Your VirtualHost configuration should look like this:

<VirtualHost *:443>
    ServerName your-domain.com
    SSLEngine on
    SSLCertificateFile /path/to/your/certificate.crt
    SSLCertificateKeyFile /path/to/your/private.key

    SSLProxyEngine on
    ProxyPass /primary/store https://localhost:9443/store/
    ProxyPassReverse /primary/store https://localhost:9443/store/
</VirtualHost>

By adding the SSLProxyEngine directive and updating the ProxyPass and ProxyPassReverse directives, you allow Apache to establish secure HTTPS connections with your backend server.

Testing the updated Apache configuration

After updating your Apache configuration, test that the SSL proxy works correctly. Follow these steps:

1. Restart the Apache server: Save your configuration changes and restart Apache to apply them. Use the command for your operating system:

   For Ubuntu/Debian:

   sudo systemctl restart apache2

   For CentOS/RHEL:

   sudo systemctl restart httpd

2. Check for HTTPS connections:

   • Open a web browser and access your website using HTTPS (e.g., https://your-domain.com/primary/store).
   • Check that the page loads without SSL-related errors.
   • Look for the padlock icon in the address bar, showing a secure connection.

3. Review Apache error logs: Check the Apache error logs for SSL-related messages:

   tail -f /var/log/apache2/error.log

   or

   tail -f /var/log/httpd/error_log

4. Use cURL to test the connection: Run this command to test the SSL connection from the command line:

   curl -v https://your-domain.com/primary/store

   This will show details about the SSL handshake and connection process.

5. Check backend server logs: Review the logs of your backend server to confirm that requests are proxied correctly.

If you can make HTTPS connections without SSL-related errors and your backend server receives the proxied requests, your SSL proxy configuration works properly. If you have issues, check your configuration and SSL certificates to make sure they are set up correctly.

openssl s_client -connect your-domain.com:443 -servername your-domain.com