404 not found after updating to 6.0.5

In the 6.0.4 version some users were experiencing issues with the upgrade of the htaccess. In case of issues, removing all lines in the htaccess except the default WordPress lines seems to resolve the issue.

Let me know if that helps!

I just opened my htaccess and it consists only of three lines:

#Begin Really Simple Security
Options -Indexes
#End Really Simple Security

Is there any edit I should to do it that might help?

Problem was solved when I followed the steps and created a .htaccess file in WordPress via this guide:

https://blog.hubspot.com/website/wordpress-htaccess

The other .htaccess that I referred to was the one in the File Manager at my web hotel One.com.

I still don’t understand what happened here? But happy of course that everything works again.

Glad to hear it’s resolved! In the 6.0.4 update multiple requests to the htaccess at once could cause these issues. The .0.5 update fixed this.

For your information, I had the 6.0.5 versin installed and the problem still persisted, was solved only after creating a .htaccess file in WordPress, a solution I was lucky to find when random troubleshooting on Google. My site was down several hours because of this.

Also, Jetpack statistics stopped working when a plugin called Comlpianz was, it seems, automatically installed when updating Real Simple SSL. Seems to be a conflict with Jetpack, so I uninstalled Complianz, again after random troubleshooting on my own.

I’m sorry this update caused so much issues.

What was the version prior to 6.0.5, was that a 5.* or a previous 6 version?

I have the exact same issue. Currently running 6.0.3, if I update to 6.0.5, all my website is in error 404 and my .htaccess file goes blank. I had to use a file/database backup and I stay in 6.0.3 until this is corrected.

I also encountered this issue: all pages show error 404.
Still figuring out how to correct it, but I fear a a backup restore is the only solution?

@khaliel can you post the content of your .htaccess here? I’ve been trying to reproduce this, but haven’t been successful yet, so I don’t know what conditions cause this problem.

I’ve now removed the .htaccess upgrade function that triggers on the upgrade from 6.0.3

https://github.com/Really-Simple-Plugins/really-simple-ssl/

Would be great if you can confirm that resolves the issue for you.

@bmwwebmaster remove all lines from the .htaccess except the wordpress ones should resolve the issue. Sorry for the problems. Still trying to reproduce the problem. possibly a specific .htaccess contents.

Chiming in with same exact same issue, pretty scary to have my webshop shut down a friday evening due to an SSL upgrade, and I am not comfortable editing in htaccess files..

This is really not an okay situation IMO, when what seems like a minor upgrade completely crashes sites..

I have auto updates to keep the site secure, not now it did the complete opposit ??

Yes, I’m sorry for the problems this update caused. I’m about to release an update which removes the upgrade script. There may be a conflict with another plugin we haven’t found yet.

Removing all lines except the wordpress lines (between Begin WordPress and End WordPress) should resolve the issue. Then re-save the permalinks in the settings.

The 6.0.6 update removes the .htaccess upgrade that somehow seems to have caused this.

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

Hi @fallesen @bmwwebmaster @khaliel @inbeijing,

Would you be able to list your plugins/theme and PHP version so we can try to reproduce this issue?

Thanks in advance, regards Aert

I am having the same problem on my website, but unfortunately, I am not tech savvy and don’t know how to create a new .htaccess file: This is the error I got, and I think it’s the same as all the other folks.

The REST API encountered an unexpected result
Performance
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

When testing the REST API, an unexpected result was returned:

REST API Endpoint: https://neversaydiebeauty.com/wp-json/wp/v2/types/post?context=edit
REST API Response: (404) Not Found

@acohen5276 please try going to WordPress settings/permalinks and re-save your settings. Hope this resolves your issue!

It seems to happen with a specific plugin, but we’re not sure which one yet.

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