<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Apache Archives - WP Encryption</title>
	<atom:link href="https://wpencryption.com/category/apache/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>WordPress SSL Plugin</description>
	<lastBuildDate>Wed, 11 Jun 2025 11:22:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://wpencryption.com/wp-content/uploads/2020/04/cropped-icon-512-32x32.png</url>
	<title>Apache Archives - WP Encryption</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Permit WordPress to Reload Apache2 Server Gracefully</title>
		<link>https://wpencryption.com/permit-wordpress-to-reload-apache/</link>
		
		<dc:creator><![CDATA[wp_encryption]]></dc:creator>
		<pubDate>Sun, 17 Dec 2023 10:47:40 +0000</pubDate>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Linux]]></category>
		<guid isPermaLink="false">https://wpencryption.com/?p=1601</guid>

					<description><![CDATA[<p>Whenever a new SSL certificate is generated by WP Encryption WordPress plugin, your Server must be restarted / reloaded once for newly created SSL certificate to load onto front-end site. This requires you to login via SSH console as root / sudo user and perform the restart or you could restart the server altogether via [&#8230;]</p>
<p>The post <a href="https://wpencryption.com/permit-wordpress-to-reload-apache/">Permit WordPress to Reload Apache2 Server Gracefully</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Whenever a new SSL certificate is generated by WP Encryption WordPress plugin, your Server must be restarted / reloaded once for newly created SSL certificate to load onto front-end site. This requires you to login via SSH console as root / sudo user and perform the restart or you could restart the server altogether via your hosting panel.</p>



<p>To avoid manual restarting of Apache server whenever a renewal of SSL certificate is completed, you can permit WordPress directory user, which is probably <strong>www-data</strong> on most servers to reload apache by modifying your sudoers file as explained below:</p>



<ol class="wp-block-list">
<li>Login to your SSH console as <strong>sudo</strong> / <strong>root</strong> user</li>



<li>CD into your WordPress directory to check username of directory owner Ex: www-data, ubuntu, admin</li>
</ol>



<figure class="wp-block-image size-full"><img fetchpriority="high" decoding="async" width="591" height="401" src="https://wpencryption.com/wp-content/uploads/2023/12/owner-username.png" alt="" class="wp-image-1602" srcset="https://wpencryption.com/wp-content/uploads/2023/12/owner-username.png 591w, https://wpencryption.com/wp-content/uploads/2023/12/owner-username-300x204.png 300w" sizes="(max-width: 591px) 100vw, 591px" /></figure>



<p></p>



<p>3. Modify sudoers file using below command</p>



<pre class="wp-block-code"><code>nano /etc/sudoers</code></pre>



<p>4. Add the below line of code in &#8220;user privilege specification&#8221; section replacing <strong>www-data</strong> with the correct username if its different for your WordPress directory</p>



<pre class="wp-block-code"><code>www-data ALL=NOPASSWD:/usr/sbin/service apache2 reload</code></pre>



<p>as shown in below screenshot,</p>



<figure class="wp-block-image size-full"><img decoding="async" width="587" height="346" src="https://wpencryption.com/wp-content/uploads/2023/12/user-privilege.png" alt="" class="wp-image-1603" srcset="https://wpencryption.com/wp-content/uploads/2023/12/user-privilege.png 587w, https://wpencryption.com/wp-content/uploads/2023/12/user-privilege-300x177.png 300w" sizes="(max-width: 587px) 100vw, 587px" /></figure>



<p>Press <strong>CTRL + O</strong> to save the file and <strong>CTRL + X</strong> to exit nano editor.</p>



<p></p>



<p>That&#8217;s it!. WP Encryption Premium plugin will automatically reload apache and load the renewed fresh SSL certificate on your frontend HTTPS site without requiring you to manually restart apache.</p>



<p>If you are on Nginx or Bitnami server, please contact our support team at <strong>support.wpencryption.com</strong> for guidance.</p>
<p>The post <a href="https://wpencryption.com/permit-wordpress-to-reload-apache/">Permit WordPress to Reload Apache2 Server Gracefully</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Fix Let&#8217;s Encrypt &#8220;R3&#8221; Root Certificate Expired or SSL Not Trusted Issue</title>
		<link>https://wpencryption.com/r3-root-expired-not-trusted/</link>
					<comments>https://wpencryption.com/r3-root-expired-not-trusted/#respond</comments>
		
		<dc:creator><![CDATA[wp_encryption]]></dc:creator>
		<pubDate>Sat, 02 Oct 2021 11:43:19 +0000</pubDate>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Bitnami]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[SSL Error]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[Digital Ocean]]></category>
		<category><![CDATA[HTTPS]]></category>
		<guid isPermaLink="false">https://wpencryption.com/?p=1035</guid>

					<description><![CDATA[<p>Is your HTTPS site powered by Let's Encrypt SSL certificate showing INSECURE all of a sudden since September 30, 2021?</p>
<p>The post <a href="https://wpencryption.com/r3-root-expired-not-trusted/">Fix Let&#8217;s Encrypt &#8220;R3&#8221; Root Certificate Expired or SSL Not Trusted Issue</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Is your HTTPS site powered by <a href="https://letsencrypt.org" target="_blank" rel="noreferrer noopener nofollow"><strong>Let&#8217;s Encrypt</strong> </a>(Open certificate authority) SSL certificate showing INSECURE, &#8220;Your connection is not private&#8221;, &#8220;ERR_CERT_AUTHORITY_INVALID&#8221; or similar SSL issue all of a sudden since <strong>September 30, 2021</strong>?. This is due to recent expiration of <strong>DST cross-signed root certificate</strong>. Likewise, you are not alone as huge number of HTTPS sites using Let&#8217;s Encrypt are impacted by this expiration.</p>



<p>In our previous post, we explained <strong><a href="https://wpencryption.com/err_cert_authority_invalid/">how to resolve the SSL not trusted / root certificate expired issue for WordPress users and WP Encryption plugin</a></strong> users. Whereas, this guide is focused towards anyone using <strong>Let&#8217;s Encrypt SSL</strong> on their website using Apache, Nginx, Bitnami, Lightsail, Certbot or any server/platform.</p>



<h2 class="wp-block-heading">Fixing root certificate expired issue on shared hosting platforms </h2>



<p>If you are using SSL provided by <strong>AutoSSL </strong>or your shared hosting platform, all you need to do is just<strong> re-install</strong> the SSL certificate or <strong>re-run</strong> the autossl to fix the issue, hoping that almost all hosting platforms have updated the root certificate on their platform already. If that doesn&#8217;t resolve your issue, you could manually <strong><a href="https://wordpress.org/plugins/wp-letsencrypt-ssl/" target="_blank" rel="noreferrer noopener">generate new SSL certificate</a></strong> and install it manually on your hosting platform with <strong>new active intermediate certificate (cabundle) </strong>provided at the <strong>bottom of this post</strong>.</p>



<p>If you manually generated Let&#8217;s Encrypt SSL certificate using <strong><a href="https://wordpress.org/plugins/wp-letsencrypt-ssl/" target="_blank" rel="noreferrer noopener">WP Encryption WordPress plugin </a></strong>or with any other service which helps generate free Let&#8217;s Encrypt SSL certificate,  simply re-installing the <strong>existing</strong> certificate &amp; private key with the<strong> new intermediate certificate </strong>provided at the bottom of this post would resolve the issue. If you have updated to latest release <strong>v5.7.1 </strong>of WP Encryption plugin, the new intermediate certificate is already updated so you could easily re-generate fresh SSL certificate with correct root / intermediate or you could easily download / copy the new intermediate certificate to use from the &#8220;<strong>Download SSL Certificates</strong>&#8221; page of WP Encryption.</p>



<h2 class="wp-block-heading">Fixing root certificate expired issue on AWS, Digital Ocean, Self managed server</h2>



<p>Websites hosted on self managed servers with <strong>Apache</strong>,<strong> Nginx </strong>or <strong>Bitnami</strong> needs to follow a slightly different suit. Please modify your Apache / Nginx <strong>server config file</strong> via SSH console, check for file path of <strong><a href="https://wpencryption.com/install-ssl-for-apache-server/" target="_blank" rel="noreferrer noopener">SSLCACertificateFile</a></strong> in case of Apache (<em>which points to your intermediate certificate file</em>) and<strong> <a href="https://wpencryption.com/install-ssl-for-nginx-server/" target="_blank" rel="noreferrer noopener">ssl_certificate </a></strong>in case of Nginx (<em>which points to a concatenated certificate + intermediate cert file</em>).</p>



<h3 class="wp-block-heading">Apache Server:-</h3>



<p>Please update your <strong>intermediate cert file</strong> content with the new intermediate cert provided at the bottom of this article, save the file and restart apache server to fix the HTTPS issue.</p>



<h3 class="wp-block-heading">Nginx Server:-</h3>



<p>You will notice <strong>2</strong> cert blocks within your <strong>ssl_certificate</strong> file and you only need to <strong>replace the bottom one </strong>with the new intermediate cert provided at the bottom of this article. Once after updating, please save the server config file and restart nginx server once to fix the HTTPS issue.</p>



<p></p>



<p>Finally, the new rise of this SSL issue only requires updating of your <strong>intermediate certificate</strong> and you don&#8217;t really need to worry about your active certificate or key file.</p>



<p></p>



<h2 class="wp-block-heading">Let&#8217;s Encrypt Active Intermediate Certificate to Use:</h2>



<pre class="wp-block-code"><code>-----BEGIN CERTIFICATE-----
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjAwOTA0MDAwMDAw
WhcNMjUwOTE1MTYwMDAwWjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCUjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7AhUozPaglNMPEuyNVZLD+ILxmaZ6QoinXSaqtSu5xUyxr45r+XXIo9cP
R5QUVTVXjJ6oojkZ9YI8QqlObvU7wy7bjcCwXPNZOOftz2nwWgsbvsCUJCWH+jdx
sxPnHKzhm+/b5DtFUkWWqcFTzjTIUu61ru2P3mBw4qVUq7ZtDpelQDRrK9O8Zutm
NHz6a4uPVymZ+DAXXbpyb/uBxa3Shlg9F8fnCbvxK/eG3MHacV3URuPMrSXBiLxg
Z3Vms/EY96Jc5lP/Ooi2R6X/ExjqmAl3P51T+c8B5fWmcBcUr2Ok/5mzk53cU6cG
/kiFHaFpriV1uxPMUgP17VGhi9sVAgMBAAGjggEIMIIBBDAOBgNVHQ8BAf8EBAMC
AYYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMBIGA1UdEwEB/wQIMAYB
Af8CAQAwHQYDVR0OBBYEFBQusxe3WFbLrlAJQOYfr52LFMLGMB8GA1UdIwQYMBaA
FHm0WeZ7tuXkAXOACIjIGlj26ZtuMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcw
AoYWaHR0cDovL3gxLmkubGVuY3Iub3JnLzAnBgNVHR8EIDAeMBygGqAYhhZodHRw
Oi8veDEuYy5sZW5jci5vcmcvMCIGA1UdIAQbMBkwCAYGZ4EMAQIBMA0GCysGAQQB
gt8TAQEBMA0GCSqGSIb3DQEBCwUAA4ICAQCFyk5HPqP3hUSFvNVneLKYY611TR6W
PTNlclQtgaDqw+34IL9fzLdwALduO/ZelN7kIJ+m74uyA+eitRY8kc607TkC53wl
ikfmZW4/RvTZ8M6UK+5UzhK8jCdLuMGYL6KvzXGRSgi3yLgjewQtCPkIVz6D2QQz
CkcheAmCJ8MqyJu5zlzyZMjAvnnAT45tRAxekrsu94sQ4egdRCnbWSDtY7kh+BIm
lJNXoB1lBMEKIq4QDUOXoRgffuDghje1WrG9ML+Hbisq/yFOGwXD9RiX8F6sw6W4
avAuvDszue5L3sz85K+EC4Y/wFVDNvZo4TYXao6Z0f+lQKc0t8DQYzk1OXVu8rp2
yJMC6alLbBfODALZvYH7n7do1AZls4I9d1P4jnkDrQoxB3UqQ9hVl3LEKQ73xF1O
yK5GhDDX8oVfGKF5u+decIsH4YaTw7mP3GFxJSqv3+0lUFJoi5Lc5da149p90Ids
hCExroL1+7mryIkXPeFM5TgO9r0rvZaBFOvV2z0gp35Z0+L4WPlbuEjN/lxPFin+
HlUjr8gRsI3qfJOQFy/9rKIJR0Y/8Omwt/8oTWgy1mdeHmmjk7j1nYsvC9JSQ6Zv
MldlTTKB3zhThV1+XWYp6rjd5JW1zbVWEkLNxE7GJThEUG3szgBVGP7pSWTUTsqX
nLRbwHOoq7hHwg==
-----END CERTIFICATE-----</code></pre>
<p>The post <a href="https://wpencryption.com/r3-root-expired-not-trusted/">Fix Let&#8217;s Encrypt &#8220;R3&#8221; Root Certificate Expired or SSL Not Trusted Issue</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://wpencryption.com/r3-root-expired-not-trusted/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Setup CRON Job to Restart Server Monthly Once</title>
		<link>https://wpencryption.com/restart-server-via-cronjob/</link>
		
		<dc:creator><![CDATA[wp_encryption]]></dc:creator>
		<pubDate>Mon, 03 May 2021 09:29:19 +0000</pubDate>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Bitnami]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[OpenLightSpeed]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<guid isPermaLink="false">https://wpencryption.com/?p=839</guid>

					<description><![CDATA[<p>This guide is focused towards step by step instructions on setting up a cron job on server to restart Apache/Nginx/Bitnami monthly once</p>
<p>The post <a href="https://wpencryption.com/restart-server-via-cronjob/">Setup CRON Job to Restart Server Monthly Once</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>This guide is focused towards step by step instructions on setting up a cron job on server to restart Apache/Nginx/Bitnami monthly once so your latest SSL certificate is always loaded up automatically on frontend site without having to manually restart server.</p>



<p>First of all, You need to have<strong> root SSH</strong> <strong>access</strong> to your server. Otherwise, this method would not be possible as server restart requires <strong>sudo</strong> privileges and not something possible with your basic / jailed SSH access offered on shared hosting environments.</p>



<p>Further steps explained below:</p>



<p>1.  Login to your SSH console as <strong>root</strong> user.</p>



<p>2.  In case of <strong>Apache</strong> or <strong>Nginx</strong> server, please run the below command to identify your <strong>service</strong> path and make note of the path.</p>



<pre class="wp-block-code"><code>which service</code></pre>



<p>It will be something like <strong>/usr/sbin/service</strong></p>



<p>3. Run the below command to see which cron jobs you are already running.</p>



<pre class="wp-block-code"><code>crontab -l</code></pre>



<p>4. Start editing the crontab with <strong>nano</strong> editor using below command</p>



<pre class="wp-block-code"><code>crontab -e</code></pre>



<p>5. Using the service path you have noted, add a new monthly cron job line (runs on date 1 of each month) at the bottom of crontab editor in a new line as below</p>



<pre class="wp-block-code"><code>0 0 1 * * /usr/sbin/service apache2 restart > /monthlycron.log 2>&amp;1</code></pre>



<p>If you are using <strong>Nginx</strong> server, the above line should be,</p>



<pre class="wp-block-code"><code>0 0 1 * * /usr/sbin/service nginx restart > /monthlycron.log 2>&amp;1</code></pre>



<p>If you are using <strong>Bitnami server / Apache Lightsail</strong>, the above line should be,</p>



<pre class="wp-block-code"><code>0 0 1 * * /opt/bitnami/ctlscript.sh restart apache > /monthlycron.log 2>&amp;1</code></pre>



<p><strong>Note: </strong>Both success &amp; errors are logged in <strong>monthlycron.log</strong> file of root directory which will be helpful for debugging if server restart fails.</p>



<p>Press <strong>CTRL + O</strong> to save the crontab &amp; you are all set!. You can run <strong>crontab -l</strong> command to see the saved cron job.</p>



<p><strong>CAUTION:</strong> </p>



<p>In rare cases, If there is any error / typo in your server config file or if <strong>certificate.crt</strong>, <strong>private.pem</strong>, <strong>cabundle.crt</strong> files don&#8217;t exists in <strong>keys/</strong> directory of your WordPress directory, your server restart could fail and your site may become inaccessible on <strong>day 1 of month</strong>. In such case, you need to correct any error logged in <strong>monthlycron.log</strong> file, fix missing cert files in <strong>keys/</strong> directory and restart server once manually.</p>
<p>The post <a href="https://wpencryption.com/restart-server-via-cronjob/">Setup CRON Job to Restart Server Monthly Once</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to install SSL for WordPress on Apache server</title>
		<link>https://wpencryption.com/install-ssl-for-apache-server/</link>
		
		<dc:creator><![CDATA[wp_encryption]]></dc:creator>
		<pubDate>Thu, 03 Sep 2020 10:58:44 +0000</pubDate>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[DOCS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[Digital Ocean]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[SSL]]></category>
		<guid isPermaLink="false">https://wpencryption.com/?p=492</guid>

					<description><![CDATA[<p>Enable SSL module and install SSL for your Apache httpd or Apache2 server easily with step by step instructions</p>
<p>The post <a href="https://wpencryption.com/install-ssl-for-apache-server/">How to install SSL for WordPress on Apache server</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>This tutorial assumes your site is running on an Apache server and you have sufficient SSH knowledge. You will need to have root SSH access to complete these changes.</p>



<h2 class="wp-block-heading">1. Login to your SSH console</h2>



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



<h2 class="wp-block-heading">2. Determine your Apache server version</h2>



<p>If you are sure about having <strong>httpd</strong> or <strong>apache2</strong> server, please proceed to next step.</p>



<p>Running the below SSH commands will help you identify whether you have <strong>httpd</strong> or <strong>apache2</strong> server.</p>



<pre class="wp-block-code"><code>sudo systemctl is-enabled httpd</code></pre>



<pre class="wp-block-code"><code>sudo systemctl is-enabled apache2</code></pre>



<p>One of these will respond with <strong>enabled</strong>. Please follow below steps based on which server type is enabled.</p>



<h2 class="wp-block-heading">3. Install SSL for Apache httpd server</h2>



<p>Please run the below SSH command to install SSL module if not already installed:</p>



<pre class="wp-block-code"><code>sudo yum update -y</code></pre>



<pre class="wp-block-code"><code>sudo yum install -y mod_ssl</code></pre>



<p>If you have Linux 2, please run below command instead of above one</p>



<pre class="wp-block-code"><code>sudo yum install -y mod24_ssl</code></pre>



<h3 class="wp-block-heading">3a. Modify httpd config file with correct SSL paths</h3>



<p>Now it&#8217;s time to correct the SSL cert, key and ca bundle paths in default config file. CD into <strong>/etc/httpd/conf.d/</strong> and edit <strong>ssl.conf</strong> file</p>



<pre class="wp-block-code"><code>cd /etc/httpd/conf.d/</code></pre>



<pre class="wp-block-code"><code>sudo nano ssl.conf</code></pre>



<p>You need to look for <strong>SSLCertificateFile</strong>, <strong>SSLCertificateKeyFile</strong> &amp; <strong>SSLCACertificateFile</strong> lines. Assuming your site is hosted / stored in <strong>/var/www/</strong> directory and SSL certificates generated with <strong><a href="https://wordpress.org/plugins/wp-letsencrypt-ssl/" target="_blank" rel="noreferrer noopener">WP Encryption</a></strong> WordPress plugin stored in <strong>keys</strong> directory, modify the 3 lines to look like this:</p>



<pre class="wp-block-code"><code>SSLCertificateFile /var/www/keys/certificate.crt
SSLCertificateKeyFile /var/www/keys/private.pem
SSLCACertificateFile /var/www/wp-content/plugins/wp-letsencrypt-ssl/cabundle/ca.crt</code></pre>



<p>Save the file by pressing <strong>CTRL+O</strong> and exit editor with <strong>CTRL+X</strong>. <strong>CMD+O</strong> and <strong>CMD+X</strong> on Mac Terminal.</p>



<h3 class="wp-block-heading">3b. Restart httpd server for SSL changes to take effect</h3>



<p>Now we are done with the server config changes, it&#8217;s time to restart apache httpd server once for changes to take effect. Please run the below SSH commands to do so:</p>



<pre class="wp-block-code"><code>sudo systemctl restart httpd</code></pre>



<p>OR</p>



<pre class="wp-block-code"><code>sudo service httpd restart</code></pre>



<p>Your HTTPS site should be working perfectly now!.</p>



<h2 class="wp-block-heading">4. Install SSL for Apache2 server</h2>



<p>Enable SSL module using below command if not already enabled</p>



<pre class="wp-block-code"><code>sudo a2enmod ssl</code></pre>



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



<pre class="wp-block-code"><code>sudo a2ensite default-ssl.conf
sudo nano default-ssl.conf</code></pre>



<p>If you don&#8217;t find <strong>sites-available</strong> &amp;<strong> sites-enabled</strong> directory, You should probably modify <strong>apache2.conf</strong> file.</p>



<p>You need to look for <strong>SSLCertificateFile</strong>, <strong>SSLCertificateKeyFile</strong> &amp; <strong>SSLCACertificateFile</strong> lines. Assuming your site is hosted / stored in <strong>/var/www</strong>/<strong>html/</strong> directory and SSL certificates generated with <strong><a href="https://wordpress.org/plugins/wp-letsencrypt-ssl/" target="_blank" rel="noreferrer noopener">WP Encryption</a></strong> WordPress plugin stored in <strong>keys</strong> directory, modify the 3 lines to look like this:</p>



<pre class="wp-block-code"><code>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</code></pre>



<p>Save the file by pressing <strong>CTRL+O</strong> and exit editor with <strong>CTRL+X</strong>. <strong>CMD+O</strong> and <strong>CMD+X</strong> on Mac Terminal.</p>



<h3 class="wp-block-heading">4a. Restart Apache2 server for SSL changes to take effect</h3>



<p>Now we are done with the server config changes, it&#8217;s time to restart apache2 server once for changes to take effect. Please run the below SSH commands to do so:</p>



<pre class="wp-block-code"><code>sudo systemctl restart apache2</code></pre>



<p>OR</p>



<pre class="wp-block-code"><code>sudo service apache2 restart</code></pre>



<p>Your HTTPS site should be working perfectly now!.</p>
<p>The post <a href="https://wpencryption.com/install-ssl-for-apache-server/">How to install SSL for WordPress on Apache server</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Easy Install SSL for WordPress Multisite Mapped Domains</title>
		<link>https://wpencryption.com/ssl-for-wordpress-multisite-mapped-domains/</link>
		
		<dc:creator><![CDATA[wp_encryption]]></dc:creator>
		<pubDate>Tue, 25 Aug 2020 11:47:38 +0000</pubDate>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[DOCS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[Mapped Domains]]></category>
		<category><![CDATA[Multisite]]></category>
		<category><![CDATA[SSL]]></category>
		<guid isPermaLink="false">https://wpencryption.com/?p=461</guid>

					<description><![CDATA[<p>Install free lets encrypt SSL for mapped domains of wordpress multisite network within minutes. step by step tutorial on apache SSL configuration</p>
<p>The post <a href="https://wpencryption.com/ssl-for-wordpress-multisite-mapped-domains/">Easy Install SSL for WordPress Multisite Mapped Domains</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>This tutorial assumes that you already have a multisite setup with mapped domains (<strong>domain1.com</strong>, <strong>domain2.com</strong>, etc.,) using <strong><a href="https://wordpress.org/plugins/wordpress-mu-domain-mapping/" target="_blank" rel="noreferrer noopener nofollow">WordPress MU domain mapping plugin</a></strong>. To make it much more clear, WordPress Multisite allows <strong>sub-domain</strong> or <strong>sub-directory</strong> based network sites setup, however mapping of domains refers to pointing of different domain names to each sub site of multisite network using domain mapping plugin.</p>



<p>In this tutorial, We will be installing free SSL certificate provided by <strong><a href="https://letsencrypt.org" target="_blank" rel="noreferrer noopener nofollow">Let&#8217;s Encrypt®</a></strong> (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.</p>



<p><strong>Technical Requirements:</strong></p>



<ul class="wp-block-list"><li>Linux server</li><li>Apache</li><li>SSH / Command line access with root privileges</li><li>Your server should have SNI support (Server Name Indication)</li></ul>



<p></p>



<h2 class="wp-block-heading">1. Generate SSL certificate for each mapped domain of multisite network</h2>



<p>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 &#8220;<strong><a rel="noreferrer noopener" href="https://gowebsmarty.com/product/wp-encryption-pro/" target="_blank">WP Encryption</a></strong>&#8220;. Buying an SSL certificate for each domain of your network would cost several <strong>$$$</strong> each year, if you have large ecommerce sites or membership portals in your multisite network &#8211; We would highly recommend purchasing premium standard SSL certificates from one of premium SSL providers out there.</p>



<p>On the other hand, you could make use of free SSL certificates provided by Let&#8217;s Encrypt<strong>®</strong> 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 &#8220;<a rel="noreferrer noopener" href="https://gowebsmarty.com/product/wp-encryption-pro/" target="_blank">WP Encryption Pro</a>&#8221; version (You might need 3 sites / 50 sites license based on number of sites you have). It&#8217;s an one time upgrade and lifetime SSL solution.</p>



<p>Upload the <strong>WP Encryption Pro</strong> plugin via your <strong>network -&gt; plugins</strong>. 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 &amp; sub-sites and generate SSL certificate accordingly. You will need to open <strong>WP Encryption</strong> page in your <strong>WP-Admin</strong> of each site, enter your email address and click on <strong>Generate SSL Certificate</strong> button.</p>



<figure class="wp-block-image size-large"><img decoding="async" src="https://gowebsmarty.com/wp-content/uploads/2020/04/wp-encryption-page.png" alt="" class="wp-image-379"/><figcaption>WP Encryption</figcaption></figure>



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



<h2 class="wp-block-heading">2. Install SSL for main site of your multisite network</h2>



<p>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 &amp; you don&#8217;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.</p>



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



<pre class="wp-block-code"><code>cd /etc/apache2/sites-enabled</code></pre>



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



<pre class="wp-block-code"><code>sudo nano default-ssl.conf</code></pre>



<p>Enter root password if prompted. You should notice a <strong>&lt;VirtualHost&gt;&lt;/VirtualHost&gt;</strong> config block similar to below one</p>



<pre class="wp-block-code"><code>&lt;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
              
                &lt;FilesMatch "\.(cgi|shtml|phtml|php)$">
                                SSLOptions +StdEnvVars
                &lt;/FilesMatch>
                &lt;Directory /usr/lib/cgi-bin>
                                SSLOptions +StdEnvVars
                &lt;/Directory>
&lt;/VirtualHost></code></pre>



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



<ul class="wp-block-list"><li><strong>ServerName</strong> <strong>yourdomain.com</strong></li><li><strong>DocumentRoot</strong> should point to your WordPress directory, this will be <strong>/var/www/html </strong>most of the time on an apache server.</li><li><strong>SSLCertificateFile</strong> should point to <strong>certificate.crt</strong> file inside keys dir Ex:<strong> /var/www/html/keys/certificate.crt</strong></li><li><strong>SSLCertificateKeyFile</strong> should point to <strong>private.pem</strong> file inside keys dir Ex: <strong>/var/www/html/keys/private.pem</strong></li></ul>



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



<pre class="wp-block-code"><code>sudo service apache2 restart</code></pre>



<p>Now open your main site with <strong>https://</strong> protocol and you should see Let&#8217;s Encrypt valid certificate while clicking on padlock in browser address bar which means you have perfectly configured SSL for your main site.</p>



<div class="wp-block-image"><figure class="aligncenter size-large"><img decoding="async" src="https://gowebsmarty.com/wp-content/uploads/2020/04/letsencrypt-certificate-1.png" alt="" class="wp-image-383"/></figure></div>



<h2 class="wp-block-heading">3. Install SSL for sub sites / mapped domains</h2>



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



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



<pre class="wp-block-code"><code>&lt;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
              
                &lt;FilesMatch "\.(cgi|shtml|phtml|php)$">
                                SSLOptions +StdEnvVars
                &lt;/FilesMatch>
                &lt;Directory /usr/lib/cgi-bin>
                                SSLOptions +StdEnvVars
                &lt;/Directory>
&lt;/VirtualHost>

&lt;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
              
                &lt;FilesMatch "\.(cgi|shtml|phtml|php)$">
                                SSLOptions +StdEnvVars
                &lt;/FilesMatch>
                &lt;Directory /usr/lib/cgi-bin>
                                SSLOptions +StdEnvVars
                &lt;/Directory>
&lt;/VirtualHost></code></pre>



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



<pre class="wp-block-code"><code>sudo service apache2 restart</code></pre>



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



<p>We tried to be as transparent as possible so please excuse for a lengthy explanation.</p>
<p>The post <a href="https://wpencryption.com/ssl-for-wordpress-multisite-mapped-domains/">Easy Install SSL for WordPress Multisite Mapped Domains</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Install SSL for AWS Lightsail Bitnami WordPress</title>
		<link>https://wpencryption.com/ssl-for-lightsail-bitnami-wordpress/</link>
		
		<dc:creator><![CDATA[wp_encryption]]></dc:creator>
		<pubDate>Tue, 25 Aug 2020 11:44:35 +0000</pubDate>
				<category><![CDATA[Apache]]></category>
		<category><![CDATA[Bitnami]]></category>
		<category><![CDATA[DOCS]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[SSL]]></category>
		<guid isPermaLink="false">https://wpencryption.com/?p=459</guid>

					<description><![CDATA[<p>Generate and install free Let's Encrypt SSL certificate for Bitnami WordPress or AWS Lightsail WordPress within seconds</p>
<p>The post <a href="https://wpencryption.com/ssl-for-lightsail-bitnami-wordpress/">How to Install SSL for AWS Lightsail Bitnami WordPress</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>This tutorial demonstrates how to install <strong><a href="https://letsencrypt.org" target="_blank" rel="nofollow noreferrer noopener">Let&#8217;s Encrypt®</a></strong> (open certificate authority) SSL certificate for your Bitnami WordPress as well as AWS Lightsail WordPress. If you wish to use some premium SSL certificate you have purchased, feel free to upload it to a secure folder on your server and skip to step 2 below.</p>



<p><strong>Technical Requirements:</strong></p>



<ul class="wp-block-list"><li>Bitnami WordPress</li><li>SSH / Command line access with root privileges</li></ul>



<h2 class="wp-block-heading">1. Generate free SSL certificate provided by Let&#8217;s Encrypt<strong>®</strong></h2>



<p>To keep this very simple, We will make use of a WordPress plugin &#8220;<a rel="noreferrer noopener nofollow" href="https://wordpress.org/plugins/wp-letsencrypt-ssl/" target="_blank">WP Encryption</a>&#8221; to generate free SSL certificate in one click.</p>



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



<figure class="wp-block-image size-full"><img decoding="async" src="https://gowebsmarty.com/wp-content/uploads/2020/04/wp-encryption-page.png" alt="wp encryption ssl" class="wp-image-379"/></figure>



<p>This process will request and retrieve free SSL certificate from Let&#8217;s Encrypt authority for your domain. SSL certificates provided by Let&#8217;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 &#8220;<a rel="noreferrer noopener" href="https://gowebsmarty.com/product/wp-encryption-pro/" target="_blank">WP Encryption Pro</a>&#8221; to avail auto renew feature and lifetime SSL mechanism. The required <strong>certificate.crt </strong>and <strong>private.pem</strong> files will be generated and stored in <strong>keys/</strong> folder inside your WordPress directory.</p>



<h2 class="wp-block-heading">2. Configure Bitnami to use SSL certificates by Let&#8217;s Encrypt<strong>®</strong></h2>



<p>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&#8217;t ever need to do it again.</p>



<h3 class="wp-block-heading">Solution 1</h3>



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



<p></p>



<p><strong>For Latest Bitnami:</strong></p>



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



<pre class="wp-block-code"><code>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</code></pre>



<p><strong>For Older Bitnami:</strong></p>



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



<pre class="wp-block-code"><code>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</code></pre>



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



<figure class="wp-block-image size-medium"><img decoding="async" src="https://gowebsmarty.com/wp-content/uploads/2020/04/letsencrypt-certificate-1-300x284.png" alt="wordpress ssl" class="wp-image-383"/></figure>



<h3 class="wp-block-heading">Solution 2</h3>



<p>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:</p>



<p></p>



<p><strong>Latest Bitnami:</strong></p>



<pre class="wp-block-code"><code>cd /opt/bitnami/apache2/conf/vhosts/

sudo nano wordpress-https-vhost.conf</code></pre>



<p><strong>Older Bitnami:</strong></p>



<pre class="wp-block-code"><code>cd /opt/bitnami/apps/wordpress/conf/

sudo nano httpd-vhosts.conf</code></pre>



<p>You will find a VirtualHost block similar to below</p>



<pre class="wp-block-code"><code>&lt;VirtualHost *:443>
    ServerName yourserverdomain.com
    ServerAlias *.yourserverdomain.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"

    SSLEngine on

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

    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
&lt;/VirtualHost></code></pre>



<p>All you need to modify here are the <strong>SSLCertificateFile</strong> and <strong>SSLCertificateKeyFile </strong>lines as below</p>



<p></p>



<p><strong>Latest Bitnami:</strong></p>



<pre class="wp-block-code"><code>SSLCertificateFile "/opt/bitnami/wordpress/keys/certificate.crt"

SSLCertificateKeyFile "/opt/bitnami/wordpress/keys/private.pem"</code></pre>



<p><strong>Older Bitnami:</strong></p>



<pre class="wp-block-code"><code>SSLCertificateFile "/opt/bitnami/apps/wordpress/htdocs/keys/certificate.crt"

SSLCertificateKeyFile "/opt/bitnami/apps/wordpress/htdocs/keys/private.pem"</code></pre>



<p>After making these changes, press <strong>CTRL + O</strong> to save the changes and <strong>CTRL + X</strong> 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</p>



<p><strong>NOTE:</strong> Skip to restart command below if you are on<strong> Latest </strong>Bitnami server.</p>



<pre class="wp-block-code"><code>cd /opt/bitnami/apache2/conf/bitnami/

sudo nano bitnami-apps-vhosts.conf</code></pre>



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



<pre class="wp-block-code"><code>Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"</code></pre>



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



<pre class="wp-block-code"><code>sudo /opt/bitnami/ctlscript.sh restart</code></pre>



<p>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 <strong>https://</strong> version of your site, please change the <strong>site</strong> &amp; <strong>admin url </strong>to <strong>https://</strong> via <strong>Settings -&gt; General </strong>of <strong>WP-Admin</strong> and also enable &#8220;<strong>Force HTTP</strong>S&#8221; feature of WP Encryption plugin interface if you notice any <strong>mixed content</strong> warning in browser console.</p>



<h2 class="wp-block-heading">3. Resolving Intermediate Cert (CA) issue in Bitnami WordPress</h2>



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



<p><strong>Latest Bitnami:</strong></p>



<pre class="wp-block-code"><code>cd /opt/bitnami/apache2/conf/bitnami
sudo nano bitnami-ssl.conf</code></pre>



<p><strong>Older Bitnami:</strong></p>



<pre class="wp-block-code"><code>cd /opt/bitnami/apache2/conf/bitnami
sudo nano bitnami.conf</code></pre>



<p>Add below line just after <strong>SSLCertificateKeyFile</strong> line</p>



<p></p>



<p><strong>Latest Bitnami:</strong></p>



<pre class="wp-block-code"><code>SSLCACertificateFile "/opt/bitnami/wordpress/keys/cabundle.crt"</code></pre>



<p><strong>Older Bitnami:</strong></p>



<pre class="wp-block-code"><code>SSLCACertificateFile "/opt/bitnami/apps/wordpress/htdocs/keys/cabundle.crt"</code></pre>



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



<pre class="wp-block-code"><code>sudo /opt/bitnami/ctlscript.sh restart apache</code></pre>
<p>The post <a href="https://wpencryption.com/ssl-for-lightsail-bitnami-wordpress/">How to Install SSL for AWS Lightsail Bitnami WordPress</a> appeared first on <a href="https://wpencryption.com">WP Encryption</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
