ERROR 403 after Update to WP 5.4.2

Hi– thanks for using Force Login!

The 403 Forbidden error is an HTTP status code which means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason.

Likely, this is caused by incorrect ownership or permissions on your web content files and folders. Contact your web hosting support about this issue.

Also try turning on WP_DEBUG mode to see what (if any) specific PHP error(s) are occurring when you get that 403 Forbidden Error.

After updating [WordPress] all approaches to access a page of my blog result in Error 403 […] When I deactivate [Force Login], all pages are visible, but login is still impossible (Error 403)

It sounds like only your login screen (/wp-login.php) is 403 forbidden.

While Force Login is active–?it successfully redirects visits to all pages to your 403 forbidden login screen. When you disable Force Login, all site pages are now accessible (not being redirected to login and not forbidden), but the login screen is still 403 forbidden.

You need to figure out why your login screen is returning a 403 forbidden error. Again, I suggest you contact your web hosting support about this–?it’s likely an incorrect ownership or permissions setting on your server.

Good luck!

Thank you, you are right!
Suddenly and without detectable reason, any access to some files of my self-hosted WordPress installation causes 403 errors. One of these files is wp-login.php.

If Force Login is activated, all requests are redirected to wp-login.php and result in an 403 error. Deactivating Force Login seems to solve the problem, but acutally it doesn‘t, it just avoids the requests to wp-login.php.

The reasons which are responsible for the 403 errors are unknown. It is neither the .htacess file nor the access rights. I did not change anything – despite the WordPress update a few hours before. I tried for hours without success. Many things work fine, sometimes things result in 403.

My installation is self-hosted and i have more WordPress installations: no problems with these. The solution comes on the same way, as the problem raises: I stopped my work and went to bed. The next day, everthing was fine again, suddenly and without detectable reason.

I found several posts, where people decribe comparable experiences. My advice: if everything fails, go to bed and hope for tomorrow.

Thank you again!