[ad_1]
BTW – our site is updated to v6.0.6 and whatever it does.
Below is the version of .htaccess I found after 6.0.6 was installed. It wrote over the beginning of the file (overwriting the start of our firewall entries):
#Begin Really Simple Security
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>
#End Really Simple Security
IfModule mod_authz_core.c>
Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
Order deny,allow
Deny from all
Do you maybe have Jetpack installed? We’re thinking this is a conflict with jetpack.
I haven’t been able to reproduce the issue yet, but it was most likely a conflict with another htaccess rewriting plugin. We’ve now limited the rewrite to Really Simple SSL save actions only. That added to the previous added conditions should prevent this issue from happening again.
I’m sorry for the problems caused by the recent updates.
For others reading this post: if you run into .htaccess issues, please update to 6.0.7, and re-save your permalinks in the general WordPress settings/permalinks.
Rogier,
Thank you for looking into this. The plugins currently writing to .htaccess are:
# BEGIN All In One WP Security
#AIOWPS_BLOCK_WP_FILE_ACCESS_START
…
#AIOWPS_ADVANCED_CHAR_STRING_FILTER_END
# END All In One WP Security
# BEGIN W3TC Browser Cache
…
# END W3TC Browser Cache
# BEGIN W3TC Page Cache core
…
# END W3TC Page Cache core
#Begin Really Simple Security
…
#End Really Simple Security
# BEGIN WordPress
…
# END WordPress
# BEGIN SMUSH-WEBP
…
# END SMUSH-WEBP
I’m happy to report updating to RSS 6.0.7 with no apparent problems. Thank you for your efforts.
Thanks for confirming the current fix. We’ll continue investigating to ensure full compatibility with all plugins, thanks your help in this.