Issue WordPress: "Sorry, you are not allowed to access this page."

[stevland]

I've been working on and logged into a WP site for several hours.

All of a sudden, when trying to access the Dashboard I received this message:

"Sorry, you are not allowed to access this page"

I tried all of the standard WP troubleshooting techniques (disable theme, plugins, replace .htaccess, check permissions, enable debug, check error logs, etc).

It then occurred to me that I installed this WP instance through Plesk... so I tried logging in through Plesk's interface. Which worked.

I now have full access to the full WP backend using the same web browser.

But if I try any other browser I continue to receive the "Sorry" error.

I would be able to live with this but I have to invite technically-challenged users to contribute to the site. Having them navigate through Plesk to log into WordPress isn't a very elegant workaround.

Has anyone else run into this one?

 

[D4NY]

This morning i've found all WP websites (not yet manually upgraded to 5.0.1) upgraded to 4.9.9. On one of our two servers the front end works but i can't login in the backend.

i try to access https://www.MYDOMAIN.com/wp-admin/ but after waiting long time the browser says "impossible to reach the website" and the address bar is like that: https://www.MYDOMAIN.com:7081/wp-admin/

No way to access, can't understand....i can't find any info on google. What's happening?

 

[D4NY]

Look at this: New Server is randomly adding port 7081 on HTTPS requests

 

[D4NY]

To explain better... let's take a Wordpress website on this server like Livia Marasso – Porcelain Creations ...as you can see the website is perfectly working.
If i want to access the Wp backend and i open this link https://www.liviamarasso.it/wp-admin the webserver redirect me to https://www.liviamarasso.it:7081/wp-admin/ that obviously give me an error.
But if i open this link Login ‹ Livia Marasso — WordPress (with the final slash /) it works normally.

The server with the issue is a Debian 8 VPS with Onyx 17.8 while the second server working good is a Debian 9 dedicated server with Onyx 17.8
The only difference is that on the first one was not running the "server reverse proxy (ngix)" service, but i've reinstalled it and nothing changed.
Also tried to switch from PHP-FPM to FastCGI just to try something without effects.

 

[stevland]

@D4NY,

Thank you sharing. The WP installation that I'm having trouble with was installed on Dec. 5th, and it is now running WP 4.9.9 (which came out more recently).

So there is a real possibility that the 4.9.9 update has triggered this issue. I will keep this in mind. Thanks for helping me realize it.

But, beyond that, I think the issues we are experiencing are unrelated. I have confirmed that my requests are not being redirected to a non-typical port. And it sounds like you are receiving an entirely different error message on your end.

I wish you a speedy resolution!

 

[stevland]

I would expect that a logged out user who followed a link such as Website Domains Names & Hosting | Domain.comwp-admin/plugins.php would be prompted to sign in before being redirected to the correct page.

Now on this site the logged out user who follows that link triggers the "Sorry..." error.

My initial assumption was that, as I set this installation up using the WordPress Toolkit in Plesk and suddenly I could only log back into it through the Plesk/WP Toolkit, that it must have something to do with how Plesk set it up.

I just discovered, however, that a logged out user can go to Website Domains Names & Hosting | Domain.comwp-login.php and log in. After doing so they can access the back end and all works as expected.

I am now inclined to think that this issue actually has nothing to do with Plesk or the WP Toolkit.

 

[ihuongdanvn]

You can fix this error by: Disable or rename the plugin directory into plugin2. Then check with each plugin. You can see more ways to fix it here Cách fix lỗi "Sorry, you are not allowed to access this page" WordPress Good luck

 

[Bitpalast]

I am now inclined to think that this issue actually has nothing to do with Plesk or the WP Toolkit.

Excellent guess.