SSL Letsencrypt Letsencrypt & CloudFlate - infinite loop

If you set Cloudflare Full SSL, then all origin servers subdomain or main domain will need to have HTTPS at Centmin Mod Nginx origin side supported. You can switch all other subdomain/main domain's Centmin Mod origin to using HTTPS via outlined method 3, existing non-HTTPS Nginx migration to HTTPS guide and then enable Cloudflare Full SSL for future site creation.

There's generally 3 ways of setting up HTTPS SSL certificate for Centmin Mod Nginx HTTP/2 based HTTPS

Method 1. The traditional way via centmin.sh menu option 2, 22 but ensuring you set LETSENCRYPT_DETECT='y' in persistent config file created at /etc/centminmod/custom_config.inc before you run centmin.sh menu option 2 or 22 for wordpress. You can do that using command below - only need to do this step once and every subsequent run of centmin.sh menu option 2 or 22 will have letsencrypt ssl certificate support enabled

Code (Text):

# enable letsencrypt ssl certificate integration https://centminmod.com/acmetool/
touch /etc/centminmod/custom_config.inc
echo "LETSENCRYPT_DETECT='y'" >> /etc/centminmod/custom_config.inc

Method 2. Using and testing Centmin Mod 123.09beta01's new addons/acmetool.sh addon which is still in beta testing only for integrating Letsencrypt SSL certificates. And has both auto and manual methods.

Method 3. Fully manual method for free Letsencrypt SSL certificates.

• For existing non-HTTPS Nginx vhost sites migration to HTTPS as outlined at Migrating Existing Nginx Vhost From HTTP to HTTP/2 based HTTPS With Letsencrypt SSL Certificates
• For brand new Nginx vhosts not yet created on server use this guide Using Centmin Mod acmetool.sh addon for Nginx HTTP/2 based HTTPS with free Letsencrypt SSL certificates

You can test in SSH via curl to check headers for location field (where the redirect goes) using the following commands:

Code (Text):

curl -I http://domain.com

Code (Text):

curl -I http://www.domain.com

Code (Text):

curl -I https://domain.com

Code (Text):

curl -I https://www.domain.com

for posting code or output from commands to keep the formatting, you might want to use CODE tags for code How to use forum BBCODE code tags

Make sure you update Wordpress settings URL to be the HTTPS version and not old non-HTTPS otherwise Wordpress PHP will do an internal redirect from HTTPS to non-HTTPS itself which may cause a redirect loop too. Also ensure it's the main domain you want folks to land on and not a redirect i.e. non-www to www or www to non-www redirect.

What's output for these commands changing /home/nginx/domains/domain.com/public/ to the path to where you installed wordpress i.e. if domain.com/blog then it would be /home/nginx/domains/domain.com/public/blog

Code (Text):

cd /home/nginx/domains/domain.com/public/
wp option get siteurl --allow-root
wp option get home --allow-root

If siteurl and home values are coming up with non-www and you want www being the main destination you can change them in your wordpress generation url settings or more thoroughly via wp-cli command line

Code (Text):

cd /home/nginx/domains/domain.com/public/
wp search-replace 'https://example.com' 'https://www.example.com' --skip-columns=guid

Code (Text):

cd /home/nginx/domains/domain.com/public/
wp option update home 'https://www.example.com'
wp option update siteurl 'https://www.example.com'

And same in reverse, if siteurl and home values are coming up with www and you want non-www being the main destination you can change them in your wordpress generation url settings or more thoroughly via wp-cli command line

Code (Text):

cd /home/nginx/domains/domain.com/public/
wp search-replace 'https://www.example.com' 'https://example.com' --skip-columns=guid

Code (Text):

cd /home/nginx/domains/domain.com/public/
wp option update home 'https://example.com'
wp option update siteurl 'https://example.com'