New Install: WP + LetsEncrypt SSL = Content Formatting Off

There could be 2 possible reasons for theme issues

1. mixed content
2. centmin mod centmin.sh menu option 22 wpsecure and autoprotect.sh blocking your theme or plugin functionality

Or combination of both issues.

If you have mixed content issue so need to adjust your web app and/or web site style itself see What Is Mixed Content? - KeyCDN Support

Centmin Mod values security and puts additional measures in place so that end users are also mindful of security. So in your case, you might need to whitelist or unblock the WP plugins related to your 403 permission denied messages.

If you used centmin.sh menu option 22 auto installer Wordpress Nginx Auto Installer, the default wpsecure conf file at /usr/local/nginx/conf/wpincludes/${vhostname}/wpsecure_${vhostname}.conf where vhostname is your domain name, blocks php scripts from executing in wp-content for security

Below links you can see examples of setting up specific wordpress location matches to punch a hole in the wpsecure blocking to whitelist specific php files that need to be able to run.

• Problem with timthumb security
• Wordpress - need help for woocommerce plugin
• Wordpress - Visual editor missing
• Wordpress - Social login plugin trouble
• Wordpress - Social login plugin trouble

If on Centmin Mod 123.09beta01, you may have ran into the new tools/autoprotect.sh cronjob feature outlined at Beta Branch - autoprotect.sh - apache .htaccess check & migration to nginx deny all | Centmin Mod Community You uploaded scripts may have .htaccess deny from all type files in their directories which may need bypassing autoprotect. It's a security feature that no other nginx based stack has as far as I know

So instead, all .htaccess 'deny from all' detected directories now get auto generated Nginx equivalent location match and deny all setups except if you want to manually bypass the directory from auto protection via a .autoprotect-bypass file - details below here.

You can read a few threads below on how autoprotect.sh may have caught some folks web apps falsely and the workarounds or improvements made to autoprotect.sh with the help of users feedback and troubleshooting.

• Is it better to add an exeption for 127.0.0.1 for autoprotect rules? | Centmin Mod Community
• IP.Board - Query on autoprotect + IPB forums | Centmin Mod Community
• Wordpress - Akismet JS and CSS - Forbidden? | Centmin Mod Community
• Nginx - Error 403 nginx with sngine script

Check if your nginx vhost at either or both /usr/local/nginx/conf/conf.d/domain.com.conf and/or /usr/local/nginx/conf/conf.d/domain.com.ssl.conf has include file for autoprotect example

Code (Text):

include /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf;

see if your directory for the script which has issues is caught in an autoprotect include entry in /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf which has a deny all entry

Code (Text):

cat /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf

i.e.

Code (Text):

# /home/nginx/domains/domain.com/public/subdirectory/js
location ~* ^/subdirectory/js/ { allow 127.0.0.1; deny all; }

If caught you can whitelist it by autoprotect bypass .autoprotect-bypass file - details below here. So if problem js file is at domain.com/subdirectory/js/file.js then it is likely /subdirectory/js has a .htaccess with deny all in it - make sure that directory is meant to be publicly accessible by contacting author of script and if so, you can whitelist it and re-run autoprotect script to regenerate your /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf include file

Code (Text):

cd /home/nginx/domains/domain.com/public/subdirectory/js
touch .autoprotect-bypass
/usr/local/src/centminmod/tools/autoprotect.sh
nprestart

it maybe you need to also whitelist /subdirectory then it would be as follows creating bypass files at /home/nginx/domains/domain.com/public/subdirectory/.autoprotect-bypass and /home/nginx/domains/domain.com/public/subdirectory/js/.autoprotect-bypass

Code (Text):

cd /home/nginx/domains/domain.com/public/subdirectory/
touch .autoprotect-bypass
cd /home/nginx/domains/domain.com/public/subdirectory/js
touch .autoprotect-bypass
/usr/local/src/centminmod/tools/autoprotect.sh
nprestart

then double check to see if updated /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf include file now doesn't show an entry for /subdirectory/js

 

have you checked chrome devtool network and console tab for clues ?

 

When did you install and run centmin.sh menu option 22, as I committed a fix which should of fixed this back on November 1, 2018 AEST ~11 days ago centminmod/centminmod - edit: actually, i made the fix in the newer fastcgi_cache routines and forgot to add it to cacher enabler routine Just updated to add missing update at update inc/wpsetup.inc autoptimize plugin wp-cli set up in 123.09beta01 · centminmod/centminmod@4ea1e84

it's due to autoptmize newer 2.4 version having additional settings field changes which were incompatible with my automatically set autoptimize settings.

so if you go into wp-admin autoptimize and re-save the settings it should fix it.

 

Great, just updated to add missing update at update inc/wpsetup.inc autoptimize plugin wp-cli set up in 123.09beta01 · centminmod/centminmod@4ea1e84 so future centmin.sh menu option 22 wordpress installs will work out of the box

 

Seems like autoptimize has more new updates for their latest version. So maybe might di auto settings config though i haven't experienced this myself