Please login to your SSH console as root / sudo user, cd into your WordPress directory and update the owner group of directory recursively to allow apache / www-data user to create directory within WordPress. You can do so via below command,

sudo chown -R www-data:www-data /var/www/html

Please make sure to replace /var/www/html to your WordPress site folder path.

The post Parse Error Reading JWS Error appeared first on WP Encryption.

Manually trying to add some code snippet into .htaccess or wp-config.php files could sometimes go wrong and even with a minor misplacement or error, your WordPress site would be down showing some weird error which would freak out non-technical users. So most of the time, its better to allow trusted plugins to automate the process on its own.

How to make htaccess writable?

If you are wondering what is this .htaccess file, htaccess rules instruct Apache server to handle certain redirections like HTTP to HTTPS and permalinks accordingly. Please follow the step by step instructions to make htaccess writable:

1. Login to your cPanel / hosting panel.
2. Find & click on the File Manager tool (Some hosts may have it in different places like tools > File Manager).

3. Navigate to File Manager Settings and make sure to enable “show hidden files” option.

4. In the below screenshot, you can notice file permission of .htaccess file is 444. Setting this to 644 would allow plugins to make changes to this file. You can also revert back this file permission after the change if required.

5. Right click on the .htaccess file and click on Change Permissions option

6. Make the file writable for owner and thus setting the permission to 644.

That’s it!.. Your .htaccess file should now be writable. Reloading the plugin page on your wp-admin would detect these changes. Anyhow, on fully restricted servers & custom managed servers like AWS, Digital Ocean, etc., Changing permissions via FTP or File Manager may be restricted and you might have to login via SSH console and change the file permissions.

In order to make wp-config.php file writable, please follow the same instructions > right click on wp-config.php file and change permissions to 644. Now you have learnt how to handle file permissions like a security ninja! 😉

The post Make wp-config.php & .htaccess Writable in WordPress appeared first on WP Encryption.

All our guides are pretty much focused towards non-technical users instead of big theory and we will be following the same approach jumping onto resolving the issue straightaway.

Why ERR_CERT_COMMON_NAME_INVALID error occurs?

Very common scenario is you have an SSL certificate installed for your site which don’t cover either www or non-www version of your domain. You could easily test your SSL at SSLLabs.com to analyze your SSL certificate start & expiry date as well as which exact set of domains it covers.

When Google Chrome shows it as ERR_CERT_COMMON_NAME_INVALID error, You might also notice this as slightly different error message shown on other browsers like Firefox showing SSL_ERROR_BAD_CERT_DOMAIN, Microsoft Edge showing DLG_FLAGS_SEC_CERT_CN_INVALID. At the end, it all refers to the same error.

How to resolve ERR_CERT_COMMON_NAME_INVALID error?

Using Firefox or Edge browser, try testing your www & non-www domain (Ex: www.wpencryption.com and wpencryption.com) and see if the ERR_CERT_COMMON_NAME_INVALID error is shown on only one of it. If so, it clearly indicates that your installed SSL certificate don’t cover that specific domain. You could reach out to your SSL provider and re-generate SSL covering all your domains including the www & non-www version.

Well if you are using our “WP Encryption” free WordPress SSL plugin to generate and install free Let’s Encrypt SSL certificate for your WordPress site, we do have an very easy method of generating SSL covering www & non-www domain – simply follow the instructions, install the newly generated SSL certificate on your cPanel or hosting panel and you are all set!.

Both www & non-www domains are showing same error?

Then the issue is not related to just one variant. Your site must be using default SSL certificate provided by your hosting platform and you haven’t installed SSL certificate yet. You can verify the same by testing your domain on SSLLabs.com. In such a case, all you need to do is buy an SSL certificate for your domain and have it installed OR generate and install free SSL certificate for your WordPress site using WP Encryption WordPress plugin as said earlier.

TIP: You don’t need a separate SSL certificate or Wildcard SSL for your www & non-www domains. A single domain SSL certificate is sufficient to cover both the variants.

The post ERR_CERT_COMMON_NAME_INVALID fix for WordPress in 2021 appeared first on WP Encryption.

ERR_TOO_MANY_REDIRECTS is one the very common error that would panic you when trying to use CDN or reverse proxy service like StackPath, Cloudflare, etc., for your WordPress site. To keep it simple, this redirect loop error is caused because your CDN wants to pull your HTTP only site but your WordPress site already have an HTTP to HTTPS redirect which results in redirect loop.

Nothing to worry, we will jump into the solution right away!.. Please make sure to clear cache on your browser & CDN platform before diving in.

SOLUTION 1

1. Please login to your hosting panel, select FILE MANAGER tool.
2. Choose to show “hidden” files in file manager settings.
3. You will find .htaccess file in root directory of your WordPress site, please take a backup on your local computer and delete it.
4. If HTTPS is enforced via .htaccess, err_too_many_redirects redirect loop should be resolved already (please make sure to clear cache & cookies of your browser before testing your site).

Once after gaining access to your wp-admin, you can go to Settings > Permalinks, choose your preferred permalink structure and save settings to re-generate default .htaccess file.

SOLUTION 2

1. Please login to your hosting panel, select FILE MANAGER tool.
2. Modify wp-config.php file located in the root directory of your WordPress site.
3. Add the below lines of code in a new line above /* That’s all, stop editing! Happy blogging. */

define("WP_HOME", "http://YOUR_SITE_URL");
define("WP_SITEURL", "http://YOUR_SITE_URL");

Please make sure to replace YOUR_SITE_URL with your correct domain Ex: http://wpencryption.com

4. Save the changes, clear your browser cache and check if your site starts working.

SOLUTION 3

If none of the above solutions worked, ERR_TOO_MANY_REDIRECTS redirect loop must be caused by one of the redirect, SSL or similar plugin activated on your WordPress site. Using the FILE MANAGER on your hosting, you can simply go to wp-content/plugins/ directory and start renaming suspected plugin folders to PLUGINNAME-HOLD one by one and view your site to identify the exact plugin that’s causing the redirect loop.

If you are self managing server instance on cloud platforms like AWS, Digital Ocean, etc., HTTPS redirection must be enforced via Apache or Nginx server config file located in /etc/apache2/, /etc/nginx/ respectively. You will need to login via SSH console and remove those redirections to get your site working.

One of the above 3 solutions should absolutely fix ERR_TOO_MANY_REDIRECTS issue on your site. If you still need help, please consider opting for WP Encryption Pro plan and our highly experienced support will resolve it for you ASAP regardless of the complexity.

If you were able to resolve the redirect loop, We highly recommend using “Force HTTPS via HTACCESS” feature of WP Encryption free SSL plugin which auto detects the reverse proxy, CDN you are using and implements appropriate rules to make your HTTPS site work smooth!.

TIP: If you are using reverse proxy services like StackPath, Cloudflare – Please enable HTTPS enforcement on your CDN dashboard too.

The post ERR_TOO_MANY_REDIRECTS WordPress Redirect Loop Fix appeared first on WP Encryption.

1. Login to your OpenLightSpeed webadmin Ex: domain.com:7080
2. Go to Listeners page
3. Edit the SSL listener with port 443
4. Navigate to SSL tab
5. Update private key file and certificate file paths as below

/var/www/html/keys/private.pem
/var/www/html/keys/certificate.crt

6. Click SAVE and do a Graceful Restart once.

The post How to install SSL for OpenLightSpeed server – WordPress appeared first on WP Encryption.

1. Login to your WHM panel via 2087 port. Ex: https://domain.com:2087
2. On WHM homepage, click “SSL/TLS” option
3. On “SSL/TLS” page, please click on “Install an SSL certificate on a Domain” option.
4. Please enter your domain name and copy/paste the downloaded cert, key & ca bundle file contents into appropriate fields.
5. Click “Install” to complete the process.

Your HTTPs site should be perfectly working now!

The post How to install SSL certificate for WordPress on WHM panel appeared first on WP Encryption.

1. Login to your SSH console

If you have Nginx server running on cloud platforms like AWS or Digital Ocean, you might be able to login via SSH using Launch Console option. Otherwise, you can login using SSH key file or password via terminal.

2. Upload SSL certificates to secure folder and merge certs

Download crt, key & ca bundle files via WP Encryption plugin interface, rename them as certificate.crt, private.pem, cabundle.crt accordingly for easier identification and upload them onto a secure folder of your choice. Let’s assume you uploaded them to /etc/ssl/ directory.

cd /etc/ssl/ and merge certificate.crt and cabundle.crt files using below SSH command

cat certificate.crt cabundle.crt >> cert.crt

3. Update Nginx virtual host with correct SSL paths

cd /etc/nginx/sites-enabled/ directory and modify the default file using nano editor. If you don’t find any file here, copy the default file from /etc/nginx/sites-available/ to /etc/nginx/sites-enabled/ using cp command.

Now you need to find lines similar to below:

server {

    listen 443 ssl;    
    
    ssl_certificate        /etc/ssl/certificate.crt; 
    ssl_certificate_key    /etc/ssl/private.key;

ssl_certificate and ssl_certificate_key are the only 2 lines we need to update here. Update these 2 lines with correct paths of merged cert file and key file,

ssl_certificate /etc/ssl/cert.crt;
ssl_certificate_key /etc/ssl/private.pem

Finally, save the config changes.

4. Restart Nginx server for SSL changes to take effect

Nginx server can be restarted using below SSH command

sudo service nginx restart

Once after successful restart, your HTTPs site should be working perfectly!.

The post How to install SSL for WordPress on Nginx server appeared first on WP Encryption.

1. Login to your SSH console

If you have Apache server running on cloud platforms like AWS or Digital Ocean, you might be able to login via SSH using Launch Console option. Otherwise, you can login using SSH key file or password via terminal.

2. Determine your Apache server version

If you are sure about having httpd or apache2 server, please proceed to next step.

Running the below SSH commands will help you identify whether you have httpd or apache2 server.

sudo systemctl is-enabled httpd

sudo systemctl is-enabled apache2

One of these will respond with enabled. Please follow below steps based on which server type is enabled.

3. Install SSL for Apache httpd server

Please run the below SSH command to install SSL module if not already installed:

sudo yum update -y

sudo yum install -y mod_ssl

If you have Linux 2, please run below command instead of above one

sudo yum install -y mod24_ssl

3a. Modify httpd config file with correct SSL paths

Now it’s time to correct the SSL cert, key and ca bundle paths in default config file. CD into /etc/httpd/conf.d/ and edit ssl.conf file

cd /etc/httpd/conf.d/

sudo nano ssl.conf

You need to look for SSLCertificateFile, SSLCertificateKeyFile & SSLCACertificateFile lines. Assuming your site is hosted / stored in /var/www/ directory and SSL certificates generated with WP Encryption WordPress plugin stored in keys directory, modify the 3 lines to look like this:

SSLCertificateFile /var/www/keys/certificate.crt
SSLCertificateKeyFile /var/www/keys/private.pem
SSLCACertificateFile /var/www/wp-content/plugins/wp-letsencrypt-ssl/cabundle/ca.crt

Save the file by pressing CTRL+O and exit editor with CTRL+X. CMD+O and CMD+X on Mac Terminal.

3b. Restart httpd server for SSL changes to take effect

Now we are done with the server config changes, it’s time to restart apache httpd server once for changes to take effect. Please run the below SSH commands to do so:

sudo systemctl restart httpd

OR

sudo service httpd restart

Your HTTPS site should be working perfectly now!.

4. Install SSL for Apache2 server

Enable SSL module using below command if not already enabled

sudo a2enmod ssl

cd /etc/apache2/ and check if sites-available & sites-enabled directory exists. if exists – cd into sites-available and you should find a config file like default-ssl.conf. Using the default file name, Please run the below command to enable it and then modify this file,

sudo a2ensite default-ssl.conf
sudo nano default-ssl.conf

If you don’t find sites-available & sites-enabled directory, You should probably modify apache2.conf file.

You need to look for SSLCertificateFile, SSLCertificateKeyFile & SSLCACertificateFile lines. Assuming your site is hosted / stored in /var/www/html/ directory and SSL certificates generated with WP Encryption WordPress plugin stored in keys directory, modify the 3 lines to look like this:

SSLCertificateFile /var/www/html/keys/certificate.crt
SSLCertificateKeyFile /var/www/html/keys/private.pem
SSLCACertificateFile /var/www/html/wp-content/plugins/wp-letsencrypt-ssl-pro/cabundle/ca.crt

Save the file by pressing CTRL+O and exit editor with CTRL+X. CMD+O and CMD+X on Mac Terminal.

4a. Restart Apache2 server for SSL changes to take effect

Now we are done with the server config changes, it’s time to restart apache2 server once for changes to take effect. Please run the below SSH commands to do so:

sudo systemctl restart apache2

OR

sudo service apache2 restart

Your HTTPS site should be working perfectly now!.

The post How to install SSL for WordPress on Apache server appeared first on WP Encryption.

In this tutorial, We will be installing free SSL certificate provided by Let’s Encrypt® (open certificate authority) , you are free to use SSL certificate from any certificate authority unless you have SSL certificate for each of mapped domain name.

Technical Requirements:

• Linux server
• Apache
• SSH / Command line access with root privileges
• Your server should have SNI support (Server Name Indication)

1. Generate SSL certificate for each mapped domain of multisite network

First of all, you will need SSL certificates generated for each of domain you have mapped. We have a very handy WordPress plugin to make this SSL generate job very easier “WP Encryption“. Buying an SSL certificate for each domain of your network would cost several $$$ each year, if you have large ecommerce sites or membership portals in your multisite network – We would highly recommend purchasing premium standard SSL certificates from one of premium SSL providers out there.

On the other hand, you could make use of free SSL certificates provided by Let’s Encrypt® using WP Encryption plugin as a mechanism to generate and auto renew SSL certificates easily in one click without any need of technical knowledge. Support for mapped domains is offered in “WP Encryption Pro” version (You might need 3 sites / 50 sites license based on number of sites you have). It’s an one time upgrade and lifetime SSL solution.

Upload the WP Encryption Pro plugin via your network -> plugins. Activate the plugin in each individual site (instead of network activation) and enter your license key to activate the premium features. WP Encryption Pro will auto detect your main site & sub-sites and generate SSL certificate accordingly. You will need to open WP Encryption page in your WP-Admin of each site, enter your email address and click on Generate SSL Certificate button.

You will notice a message in response log of WP Encryption saying Certificate for ‘yourdomain.com’ saved. Required SSL certificate files certificate.crt and private.pem will be generated & stored in keys/ folder inside your WordPress directory (in case of main site). For sub sites, it will auto create a separate folder (keys/domain2.com/) inside keys/ folder and store the certificate.crt and private.pem inside it.

2. Install SSL for main site of your multisite network

First, We will go through the process of modifying the apache config file of your server to enable SSL for main site. Note that this config modifications are just one time process & you don’t need to do it again in future. The required certificate.crt and private.pem files for this main site will be stored directly inside keys/ folder as stated above.

Connect via SSH / Command line and navigate to /etc/apache2/sites-enabled/ using below SSH command

cd /etc/apache2/sites-enabled

Run ls -la to see list of files inside this directory. You should notice a file similar to default-ssl.conf, ssl.conf, etc., We will need to modify this config file to set correct SSL paths. Please run the below command to start the editor:

sudo nano default-ssl.conf

Enter root password if prompted. You should notice a <VirtualHost></VirtualHost> config block similar to below one

<VirtualHost _default_:443>
                ServerAdmin webmaster@localhost
                ServerName example.com
                DocumentRoot /var/www/html

                ErrorLog ${APACHE_LOG_DIR}/error.log
                CustomLog ${APACHE_LOG_DIR}/access.log combined

                #   SSL Engine Switch:
                #   Enable/Disable SSL for this virtual host.
                SSLEngine on

                #   SSLCertificateFile directive is needed.
               SSLCertificateFile      /etc/ssl/certs/ssl-cert-snakeoil.pem
               SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
              
                <FilesMatch "\.(cgi|shtml|phtml|php)$">
                                SSLOptions +StdEnvVars
                </FilesMatch>
                <Directory /usr/lib/cgi-bin>
                                SSLOptions +StdEnvVars
                </Directory>
</VirtualHost>

You might find the above VirtualHost block much more bigger & it doesn’t need to be same as above. Out of the above block, you only need to focus on 4 lines i.e., ServerName, DocumentRoot, SSLCertificateFile, SSLCertificateKeyFile. Modify these 4 lines based on below instructions:

• ServerName yourdomain.com
• DocumentRoot should point to your WordPress directory, this will be /var/www/html most of the time on an apache server.
• SSLCertificateFile should point to certificate.crt file inside keys dir Ex: /var/www/html/keys/certificate.crt
• SSLCertificateKeyFile should point to private.pem file inside keys dir Ex: /var/www/html/keys/private.pem

Once after you correct these 4 lines, press CTRL + O to save the changes, CTRL + X to exit file editor and restart apache server once using below command

sudo service apache2 restart

Now open your main site with https:// protocol and you should see Let’s Encrypt valid certificate while clicking on padlock in browser address bar which means you have perfectly configured SSL for your main site.

3. Install SSL for sub sites / mapped domains

This process will be very similar to above changes except minor differences. CD into /etc/apache2/sites-enabled and sudo nano default-ssl.conf again.

Now you will need to replicate the <VirtualHost></VirtualHost> block one below another for each mapped domain and correct the 4 lines as stated above. The only difference is the SSL certificate & key paths will be inside sub-directory inside keys/ folder. An example replication for mapped domain2.com would look like below:

<VirtualHost _default_:443>
                ServerAdmin webmaster@localhost
       ServerName maindomain.com
       DocumentRoot /var/www/html

                ErrorLog ${APACHE_LOG_DIR}/error.log
                CustomLog ${APACHE_LOG_DIR}/access.log combined

                #   SSL Engine Switch:
                #   Enable/Disable SSL for this virtual host.
                SSLEngine on

                #   SSLCertificateFile directive is needed.
       SSLCertificateFile      /var/www/html/keys/certificate.crt
       SSLCertificateKeyFile /var/www/html/keys/private.pem
              
                <FilesMatch "\.(cgi|shtml|phtml|php)$">
                                SSLOptions +StdEnvVars
                </FilesMatch>
                <Directory /usr/lib/cgi-bin>
                                SSLOptions +StdEnvVars
                </Directory>
</VirtualHost>

<VirtualHost _default_:443>
                ServerAdmin webmaster@localhost
      ServerName domain2.com
      DocumentRoot /var/www/html

                ErrorLog ${APACHE_LOG_DIR}/error.log
                CustomLog ${APACHE_LOG_DIR}/access.log combined

                #   SSL Engine Switch:
                #   Enable/Disable SSL for this virtual host.
                SSLEngine on

                #   SSLCertificateFile directive is needed.
      SSLCertificateFile    /var/www/html/keys/domain2.com/certificate.crt
      SSLCertificateKeyFile /var/www/html/keys/domain2.com/private.pem
              
                <FilesMatch "\.(cgi|shtml|phtml|php)$">
                                SSLOptions +StdEnvVars
                </FilesMatch>
                <Directory /usr/lib/cgi-bin>
                                SSLOptions +StdEnvVars
                </Directory>
</VirtualHost>

Finally, You are all set with the config changes and just need to restart server once for config changes to take effect.

sudo service apache2 restart

Now make sure a valid certificate exists for all your mapped domains by accessing the https:// version of them. Once after everything looks perfect, You can change site & admin url of all mapped domains to https:// protocol and enable “Force HTTPS” feature of WP Encryption if you notice any mixed content warnings in browser console.

We tried to be as transparent as possible so please excuse for a lengthy explanation.

The post Easy Install SSL for WordPress Multisite Mapped Domains appeared first on WP Encryption.

Technical Requirements:

• Bitnami WordPress
• SSH / Command line access with root privileges

1. Generate free SSL certificate provided by Let’s Encrypt®

To keep this very simple, We will make use of a WordPress plugin “WP Encryption” to generate free SSL certificate in one click.

All you need to do is just install & activate the plugin on your WordPress Admin, navigate to WP Encryption page, enter your email address and click on Generate SSL Certificate button.

This process will request and retrieve free SSL certificate from Let’s Encrypt authority for your domain. SSL certificates provided by Let’s Encrypt authority will expire in 90 days and you will need to re-generate new certificates again using the same process before the expiry date. SSL certificates cost you several $$$ a year, You could upgrade to “WP Encryption Pro” to avail auto renew feature and lifetime SSL mechanism. The required certificate.crt and private.pem files will be generated and stored in keys/ folder inside your WordPress directory.

2. Configure Bitnami to use SSL certificates by Let’s Encrypt®

Assuming you are on a default setup of Bitnami / AWS Lightsail WordPress, You will need to configure the server config file to use SSL certificate and key from correct path. This is an one time process and you don’t ever need to do it again.

Solution 1

Create a symbolic link from existing / current SSL certificate to new SSL certificates generated & stored by WP Encryption plugin. You can do so by connecting via SSH / Command line to your server and run the below SSH commands,

For Latest Bitnami:

If you are using latest bitnami instance where your WordPress site files are located in /opt/bitnami/wordpress/ folder,

cd /opt/bitnami/apache/conf/bitnami/certs

sudo ln -sf /opt/bitnami/wordpress/keys/certificate.crt server.crt

sudo ln -sf /opt/bitnami/wordpress/keys/private.pem server.key

sudo /opt/bitnami/ctlscript.sh restart apache

For Older Bitnami:

If you are using older bitnami instance where your WordPress site files are located in /opt/bitnami/apps/wordpress/htdocs/ folder, please use below commands instead of above,

cd /opt/bitnami/apache2/conf

sudo ln -sf /opt/bitnami/apps/wordpress/htdocs/keys/certificate.crt server.crt

sudo ln -sf /opt/bitnami/apps/wordpress/htdocs/keys/private.pem server.key

sudo /opt/bitnami/ctlscript.sh restart apache

Finally, Open your site with https:// protocol and check if valid certificate exists as below. If so, you are all set so please skip solution 2.

Solution 2

If the above symlink method fail, We will need to modify WordPress hosts config to use SSL certificates from correct path. Please login via SSH / Command line and follow the below procedure:

Latest Bitnami:

cd /opt/bitnami/apache2/conf/vhosts/

sudo nano wordpress-https-vhost.conf

Older Bitnami:

cd /opt/bitnami/apps/wordpress/conf/

sudo nano httpd-vhosts.conf

You will find a VirtualHost block similar to below

<VirtualHost *:443>
    ServerName yourserverdomain.com
    ServerAlias *.yourserverdomain.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"

    SSLEngine on

  SSLCertificateFile "/opt/bitnami/apps/wordpress/conf/certs/new_server.crt"
  SSLCertificateKeyFile "/opt/bitnami/apps/wordpress/conf/certs/new_server.key"

    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>

All you need to modify here are the SSLCertificateFile and SSLCertificateKeyFile lines as below

Latest Bitnami:

SSLCertificateFile "/opt/bitnami/wordpress/keys/certificate.crt"

SSLCertificateKeyFile "/opt/bitnami/wordpress/keys/private.pem"

Older Bitnami:

SSLCertificateFile "/opt/bitnami/apps/wordpress/htdocs/keys/certificate.crt"

SSLCertificateKeyFile "/opt/bitnami/apps/wordpress/htdocs/keys/private.pem"

After making these changes, press CTRL + O to save the changes and CTRL + X to exit the file editor. Now We will need to include this httpd-vhosts config file in main config file of Bitnami, please run below commands

NOTE: Skip to restart command below if you are on Latest Bitnami server.

cd /opt/bitnami/apache2/conf/bitnami/

sudo nano bitnami-apps-vhosts.conf

This will open Bitnami vhosts file editor, at the very bottom of the file add the below line in a new line

Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"

After making these changes, press CTRL + O to save the changes and CTRL + X to exit the file editor. Lastly, restart Bitnami for changes to take effect using below command

sudo /opt/bitnami/ctlscript.sh restart

Either one of the above two solutions would definitely succeed with the SSL setup for your Bitnami WordPress. Once after you see a valid SSL certificate accessing the https:// version of your site, please change the site & admin url to https:// via Settings -> General of WP-Admin and also enable “Force HTTPS” feature of WP Encryption plugin interface if you notice any mixed content warning in browser console.

3. Resolving Intermediate Cert (CA) issue in Bitnami WordPress

Facebook share debugger and SSLLabs might show your SSL intermediate certificate is missing. Please follow the below commands to resolve the issue:

Latest Bitnami:

cd /opt/bitnami/apache2/conf/bitnami
sudo nano bitnami-ssl.conf

Older Bitnami:

cd /opt/bitnami/apache2/conf/bitnami
sudo nano bitnami.conf

Add below line just after SSLCertificateKeyFile line

Latest Bitnami:

SSLCACertificateFile "/opt/bitnami/wordpress/keys/cabundle.crt"

Older Bitnami:

SSLCACertificateFile "/opt/bitnami/apps/wordpress/htdocs/keys/cabundle.crt"

After making these changes, press CTRL + O to save the changes and CTRL + X to exit the file editor. Lastly, restart Bitnami Apache for changes to take effect using below command

sudo /opt/bitnami/ctlscript.sh restart apache

The post How to Install SSL for AWS Lightsail Bitnami WordPress appeared first on WP Encryption.