Still Seeing "Your Connection is Not Private" Despite Let’s Encrypt Certificate on Bitnami WordPress (Lightsail)

It seems like you've taken many of the correct steps to set up your Let's Encrypt certificate on your Bitnami WordPress stack in Amazon Lightsail. However, there are a few additional things you can check and try to resolve the issue:

1. Certificate file paths: Ensure that you're using the correct file paths for your Let's Encrypt certificates. On newer Bitnami installations, the correct paths might be:

   /opt/bitnami/apache2/conf/bitnami/certs/server.crt /opt/bitnami/apache2/conf/bitnami/certs/server.key

   Double-check these paths and update your copy commands if necessary.

2. Full certificate chain: Make sure you're using the full certificate chain. Instead of copying just the .crt file, try using the fullchain.pem file:

   sudo cp /opt/bitnami/letsencrypt/certificates/saboricoa.com.fullchain.pem /opt/bitnami/apache2/conf/bitnami/certs/server.crt

3. Apache configuration: Verify that your Apache configuration is correctly referencing the SSL certificate files. Check the following files for the correct paths:

   /opt/bitnami/apache2/conf/bitnami/bitnami-ssl.conf /opt/bitnami/apache2/conf/bitnami/bitnami.conf

4. Permissions: Ensure that the Apache user has read permissions for the certificate files.

5. Firewall settings: Check your Lightsail instance's firewall settings to make sure that port 443 (HTTPS) is open.

6. Clear browser cache: Sometimes, browsers can cache SSL certificate information. Try clearing your browser cache or testing with a different browser or device.

7. SSL configuration: Use an online SSL checker tool to verify your SSL configuration and identify any issues.

If you've verified all of these points and are still experiencing issues, you may want to check the Apache error logs for any specific error messages related to SSL:

sudo tail -f /opt/bitnami/apache2/logs/error_log

Remember to restart Apache after making any changes:

sudo /opt/bitnami/ctlscript.sh restart apache

If the issue persists, you might want to consider removing the existing SSL configuration and setting it up again from scratch using the Bitnami SSL configuration script:

sudo /opt/bitnami/bncert-tool

This tool can help you set up a new Let's Encrypt certificate and configure Apache correctly.
Sources
Secure your Lightsail WordPress instance with free Let's Encrypt SSL certificates - Amazon Lightsail
Secure your Lightsail LAMP instance with Let's Encrypt SSL certificates - Amazon Lightsail
Can't get HTTPS to work on Lightsail ubuntu instances - [..] the authenticity of the received data could not be verified | AWS re:Post