404 not found after updating to 6.0.5

I went to Settings/Permalinks and resaved my existing Setting. So far, it may be working correctly again. But it is after midnight here, and I will check it again in the morning. Thank you. Please keep me in the loop if you have more information or a new version of the plugin.

We’ve pushed out an update that restricts the .htaccess rewrite to save actions in the RSSSL settings page only. It appears that this was a conflict with an (as yet unknown) other plugin. The restrictions in the 6.0.6 & 6.0.7 update should resolve the issue.

If you’re on Really Simple SSL < 6.0.7 and experience this issue, please update, then resave your permalinks in settings/permalinks.

Hi guys,
I have not been able to fix the problem by editing the .htaccess file, so I restored a backup of my website from last thursday. I got everything up and running smoothly again including Really Simple SSL in version 6.0.3.
Is it save now to upgrade to version 6.0.7 or should I wait for a version with a final update once you have clear what caused the problem initially?

Sure Rogier,

Theme: Astra (with Elementor)

Hosting on One.com
PHP version: 8.0.25

The list of plugins is a bit long:
Akismet Antispam
All in one seo
Astra pro
Autooptimize
Complianz
Elementor
Elementor Header & Footer Builder
Google Analytics for WordPress by MonsterInsights
Google Listings and Ads
Imagify
Jetpack
MailerLite – Signup forms (official)
MailerLite – WooCommerce integration
MailOptin – Lite
one.com
Performance Cache
Podcast Subscribe Buttons
Really Simple SSL
Shipmondo til WooCommerce
Site Kit by Google
Starter Templates
WooCommerce
WooCommerce PensoPay
WP Super Cache
WPForms Lite

Thanks @fallesen

@bmwwebmaster Several users have confirmed that 6.0.7 fixed the issue. I expect no more problems.

We’re still testing with the plugins posted here, so we can reproduce the original issue and include it in our tests, to prevent this from happening again.

If anyone needs help fixing any issues caused by the updates, don’t hesitate to contact us, here or by sending a mail to support(at)really-simple-ssl.com

Yes, the update and resaving permanks worked for me aswell, thank you for that!

I also updated to 6.0.7 and got no problems with pages or posts showing anymore. However, I am still left with a couple of other problems.

Since yesterday, there is no longer any preview when I share new content on my website on Twitter or LinkedIn. (Strangely, the preview do work as before when sharing on Facebook.)

Also Jetpack will not collect my visitor statistics any longer.

While I can’t prove that any of those problem are directly related to the Really Simple SSL, they certainly did’t exist before I made that update.

@inbeijing if you enabled any of the hardening features, please try disabling them. If this doesn’t help, I would recommend to rename the plugin folder through ftp. This effectively disables the plugin, ensuring that there’s nothing the plugin can do anymore, but you can also easily rename it back.

If any of these steps resolve the issue let me know which one and I will investigate.

Hello again,

First i disabled all the hardening features and tried to share on Twitter/FB. Then I disabled the plugin altogether and tried the same thing. In both cases, no success – no preview when sharing on social medias, just a blue text link.

In the case of Twitter, it says “no meta tags” and in the case of LinkedIn it’s a “500 Failure”.

Again, I don’t know how or if this is related to Really Simple SSL, but I never had those problems before the last update.

If the plugin is disabled, it can’t do anything anymore, so maybe some other plugins need to rewrite the htaccess again. This can usually be done by saving each plug-in’s settings.

Please also try if it helps to remove the htaccess redirect from Really Simple SSL, just in case, although that is pretty standard.

If this doesn’t help, maybe you can start a new topic with your domain posted so we can take a look at the website.

Tried saving the settings again on Yoast – didn’t change anything. Tried to remove the htaccess redirect from Really Simple SSL – didn’t change anything.

A last try before I open up a new thread, since this might be related to the above. After experiencing problems yesterday, I also contacted Jetpack support and they said there is some problem with the fact that my site can still also be reached via HTTP:

I ran some tests on your site, and it seems that although your domain has a valid SSL certificate, it is still possible to access your site via HTTP. Your visitors and search engines can use either HTTP or HTTPS to access your site.

HTTP: https://kinamedia.se
HTTPS: https://kinamedia.se

This is an issue for search engines, since it often causes confusion and duplicate content, but it is also an issue for your site’s communication with WordPress.com, as our system does not know whether it should connect to your site via one or the other address.

To solve this issue, I would recommend that you change your site’s URL to HTTPS (you can do so under Settings > General in your dashboard), and then ask your host for help redirecting all traffic from HTTP to HTTPS.`

It was already set to HTTPS in settings, and I have reached out also to One.com support, but to no avail.

Any idea why the site would still be reachable with HTTP, and could it have anything to do with the last update?

Cheers,
Jojje

@inbeijing is the htaccess redirect enabled currently? This usually solves such issues.

You can also manually insert it:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}%/$1 [R=301,L]
</IfModule>

This is the most common, other variants can be found here:

https://really-simple-ssl.com/manually-insert-htaccess-redirect-http-to-https/

• This reply was modified 2 years, 3 months ago by Rogier Lankhorst.

Hi, same problem here. I updated the permalinks again and it worked for me, thanks!

note: yesterday i updated 3 plugins on wordpress plugins page, this plugin plus 2 other plugins at the same time, hope this information helps in something.

drwxr-xr-x 11 * * 4096 Nov 5 14:37 ../
drwxr-xr-x 12 * * 4096 Nov 5 05:17 really-simple-ssl/
drwxr-xr-x 27 * * 4096 Nov 5 05:17 ./
drwxr-xr-x 6 * * 4096 Nov 5 05:17 easy-table-of-contents/
drwxr-xr-x 10 * * 40960 Nov 4 16:46 w3-total-cache/
drwxr-xr-x 7 * * 4096 Nov 4 16:45 ad-inserter/
drwxr-xr-x 9 * * 4096 Nov 3 17:16 formidable/
drwxr-xr-x 8 * * 4096 Oct 28 08:57 pretty-link/

Sorry about my English…

PHP version: 7.3.33

Plugins:

ad-inserter                                 
all-in-one-wp-security-and-firewall         
classic-editor                              
easy-table-of-contents                      
formidable                                  
google-analytics-for-wordpress              
locatoraid                                  
media-cleaner                               
pretty-link                                 
really-simple-ssl                           
redirection                                 
sassy-social-share                          
google-site-kit                             
tablepress                                  
tablepress-datatables-column-filter-widgets 
tablepress-responsive-tables                
tablepress-row-filter                       
tablepress-shortcode-filter-get-parameter   
tablepress-table-auto-update                
tablepress-table-row-order                  
updraftplus                                 
w3-total-cache                              
wp-add-mime-types                           
wp-mail-smtp                                
wordpress-seo

• This reply was modified 2 years, 3 months ago by edersontech.

Yes, the htaccess redirect has always been enabled, apart from five minutes when I tested to disable it yesterday to see if it changed anything.

I still got the problems with no preview on my sharing and Jetpack connection not working properly. As for the latter problem, I will continue my dialog with Jetpack support.

But regarding the sharing, I believe the problem is somehow related to the Really Simple SSL update. All posts published before that update can be shared properly, but the two posts I have been publishing after that update do not generate any preview on Twitter or LinkedIn, instead resulting in error messages “No meta tags” for Twitter och card validator, and a “500” error message when running the post on LinkedIn debug.

This is a post written before the update: https://kinamedia.se/2022/11/01/analys-av-rapporten-om-de-misskota-fallen-gui-minhai-och-dawit-isaak/

This is a post written after the update: https://kinamedia.se/2022/11/05/kina-vagrar-prata-klimat-med-usa-infor-cop27/

First one doesn’t lack meta tags or come with any 500 error message, but the second one – and every post I will write from now on – unfortunately does.

Any idea what setting this problem might be attributed to?