There are few situations more alarming than being locked out of your own WordPress admin dashboard. If you've encountered a message reading "Lamentable, yous are not immune to admission this folio" when trying to log in, you know the feeling starting time hand.

Fortunately, there are several solutions at your disposal for troubleshooting this mistake. With a trivial patience, y'all can articulate up the mistake and get back to managing your WordPress site in no fourth dimension.

In this post, nosotros'll dig into the "Deplorable, you are non allowed to access this page" mistake and what causes it to occur. Then we'll walk you lot through the many potential solutions to help you find the one that addresses your specific state of affairs.

Let'due south bound right in!

Agreement the "Sorry, You Are Not Allowed to Access This Folio" Error

Although we're referring to it as an "error" for the purposes of this post, the "Sorry, you are not immune to access this folio" bulletin in WordPress is meant to be a helpful security mensurate.

Ultimately, seeing this notification simply means there's a permissions setting that's blocking you from a sure surface area.

This becomes a problem when y'all're locked out of a office of your site that you should have permission to enter which, as an Administrator, is anywhere on the backend. When this situation arises, it is frequently post-obit a recent update to a theme, plugin, or WordPress core.

You may encounter the "Lamentable, you are not immune to access this folio" bulletin for a variety of reasons. It might exist that WordPress doesn't recognize you as an Ambassador. In other situations, the data contained in your site's core code or in a theme or plugin may not match what's in your database.

Additional causes include wrong data in your wp-config.php file or a site that'south running an outdated version of PHP. Whatsoever the source, this error may prevent you from accessing the unabridged admin surface area or just a portion of it.

Since information technology'south likely that you will non be able to access key settings via the dashboard, you'll need to use File Transfer Protocol (FTP) or phpMyAdmin to resolve this upshot. Brand certain to back up your site and brush upwardly on using these platforms before you swoop into the troubleshooting procedure.

The most frustrating affair about encountering the "Deplorable, you are not allowed to admission this folio" notification is that it can be hard to pin downwardly which of its causes are at play. Fortunately, there are many solutions you can test out to find the root of the problem.

How to Fix the "Sorry, You Are Non Allowed to Access This Page" Fault in WordPress (11 Potential Solutions)

Due to its many possible causes, the "Deplorable, you are not immune to access this page" mistake takes quite a flake of patience to resolve. This long list of solutions may exist intimidating only it also covers a diversity of situations to aid you detect the right 1 for your site.

1. Restore a Previous Version of Your Site

The simplest and often the fastest fashion to get back into your WordPress dashboard is to restore your site to an earlier version. A recent change, such as an update, might be the cause of the mistake you're seeing. Undoing your latest modification should enable y'all to access your site again.

Kinsta clients have it easy in this regard. You can restore a WordPress backup in your hosting account with a unmarried click:

Restoring a backup in MyKinsta
Restoring a fill-in in MyKinsta

The drawback to this solution is that you may lose your recent changes and volition accept to observe a way to attain your goals without causing the same fault once again.

For this reason, you may want to restore your backup to a staging site instead. You tin can so test different modifications to determine what caused the problem. After uncovering the root of the issue, you lot tin undo the troublesome alter to regain admission to your site.

2. Disable All of Your Plugins

A specific change that may exist causing the "Sorry, you are not allowed to admission this page" message on your site is the contempo addition or upgrade of a plugin. If you suspect that this is the case, your best course of action is to disable your plugins one by one.

In the event that you disable a plugin and the message goes away, you've establish the source of the problem. Y'all can then troubleshoot the upshot with that plugin (or practice without it, if it's not crucial to your site's functionality).

Of course, if you lot're locked out of your dashboard entirely, this process gets a picayune tricky. You'll need to admission your site using SFTP via a customer such as FileZilla. Once you've done and so, navigate to wp-content and find the sub-directory labeled plugins:

Disable all plugins by renaming the folder
Disable all plugins by renaming the binder

Enter this folder, and then rename your most recently-added plugin to something like "plugin-name_old". Go back to your site and bank check to run across if the error is resolved. If not, change the plugin's name back and echo the procedure with the next ane.

3. Activate a Default Theme

Nevertheless another potential cause of this mistake is that you've recently updated or installed a theme. Your best bet for resolving this problem is to activate a default WordPress theme such as Twenty Twenty or 20 Nineteen.

To do so without access to your admin area, you'll need to use FTP again. Connect to your server with FileZilla and and so navigate to wp-content > themes:

Disable your current theme by renaming the folder
Disable your current theme by renaming the folder

The residue of the process is adequately similar to the ane described above for disabling your plugins.

Rename the folder for your active theme, and so return to your site and log in. You should run into a notification telling you that the agile theme is cleaved, and a default theme has been reactivated.

Then you can troubleshoot the theme. Your site should at to the lowest degree exist accessible, albeit with the wrong theme activated.

iv. Brand Certain Yous're an Ambassador

Some other possibility is that your user role has been inadvertently changed and y'all are no longer listed as an Administrator. This is a common problem with multisite installations. To determine if this is the case, you'll need to access phpMyAdmin and look for the wp_users table:

The WP users table
The wp_users table in phpMyAdmin

Find your username and note your ID. Then, navigate to the wp_usermeta table and notice the wp_capabilties row:

The wp_usermeta table in phpMyAdmin
The wp_usermeta table in phpMyAdmin

If you have Administrator privileges, the meta_value in this row will read:

a:1:{due south:13:"administrator";southward:1:"i";}

If your wp_usermeta table says something else, you lot tin can click on the Edit link and change information technology. Alternatively, you can also create an entirely new Administrator account from phpMyAdmin. To take this route, return to the wp_users table and click on the Insert tab at the top of the table:

Change user information in wp_users table
Alter user information in wp_users table

Then, make full in the fields with your new user information. Once you're done, click on the Go button and your new user should announced in the table. Next, you'll need to make a notation of the ID for this account and caput back to the wp_usermeta table.

Click on Insert over again, and fill in the resulting fields with the post-obit data:

  • Unmeta_id: Leave this field blank; it volition exist filled in automatically for you.
  • User_id: Use the ID from the WP Users table.
  • Meta_key: Gear up this value every bit "wp_capabilities".
  • Meta_value: Add the line mentioned above.

Y'all should at present exist able to use your new credentials to log in to your WordPress admin area. Delete your quondam account or change its user office back to Administrator from the dashboard and delete the new one instead.

Subscribe Now

five. Check Your Fault Log to Pinpoint the Cause

A smart way to streamline troubleshooting whatever problem on your site is to bank check your server'due south mistake log. This may point plugin or theme compatibility problems, database errors, or problems with your site'due south files that are causing the "Sorry, yous are non allowed to access this page" bulletin to announced.

How y'all view your server's mistake log volition vary depending on who your hosting provider is. For Kinsta customers, this procedure is as unproblematic equally logging into your MyKinsta dashboard. There, select the site that's experiencing issues and navigate to Logs:

MyKinsta logs tab
MyKinsta logs tab

Choose fault.log from the drop-down menu. If y'all encounter one of the causes of the alert in your log, and so you can go about fixing it. Otherwise, you'll need to try another solution on this list.

six. Ensure That Your Database Prefix Is Correct

Every MySQL database has a prefix. If this one listed in your website's files doesn't match the one listed in phpMyAdmin, then you may come across the "Sorry, you are not immune to admission this page" message.

This can occur when migrating your site, including if you've used a local staging site for development and are now moving to a live server. To check for discrepancies, you'll need to admission your wp-config.php file.

You can do this via SFTP as we've described in previous solutions. Once you're in your wp-config.php file, you should wait for your database's prefix (the default is "wp_"):

Database prefix
Database prefix

Then, log in to phpMyAdmin and look at the prefixes for your database'southward tables. They should match the ones listed in your wp-config.php file, like in the paradigm below:

Prefixes should match those in your wp-config.php file
Prefixes should match those in your wp-config.php file

If they don't lucifer the prefix in your wp-config.php file, and then you'll need to edit it and so that they do.

seven. Look for Changes in Your wp-config.php File

On a similar note, you should besides look for any changes to your WordPress configuration file. This is especially true if yous were editing this file before long before you received the "Pitiful, y'all are not immune to access this page" bulletin or if you suspect that your WordPress site has been hacked.

You can admission your wp-config.php file using SFTP and look for annihilation that seems amiss. However, this process is much easier if you lot have some kind of file integrity monitoring or change detection feature in place.

8. Upgrade to the Latest Version of PHP

If your WordPress site is running an outdated version of PHP, this could be the source of your troubles. With that said, fifty-fifty if upgrading PHP doesn't solve this event for you, it should better your site'south overall security and operation.

Before you first the upgrade process, create a backup of your site. You can do this manually or from your MyKinsta dashboard, even if you're locked out of your admin area. One time you've saved your fill-in, you'll want to exam to see whether your account is compatible with the latest version of PHP. One way to do this is with a WordPress staging site.

Bold that all goes well, you can run the update. Kinsta customers can hands do then by logging into the MyKinsta dashboard and navigating to the relevant site. Then get to Tools > PHP Engine > Alter, and select the newest version from the drop-down menu:

How to upgrade PHP version in MyKinsta
How to upgrade PHP version in MyKinsta

If you're with some other provider, you may be able to follow a similar procedure via your own command panel. It's recommended that you contact your spider web host for more information.

9. Evaluate Your File Permissions

It'south also possible that your site'southward file permissions have been tampered with. In this case, WordPress may consider y'all unauthorized to view certain areas of your site, even if yous're withal listed as an Administrator.

To check your site's file permissions, you'll need to apply SFTP to access your server. Once you're logged in, enter the public_html directory and bulk-select wp-admin, wp-content, and wp -includes. Right-click on these folders and choose File Permissions:

Checking file permissions
Checking file permissions

In the resulting window, make sure the post-obit options are selected:

  • The Numeric Value is set to 755.
  • Recurse into subdirectories is checked.
  • Apply to directories just is selected.

Click on OK when you lot're washed. Then, highlight all the other files in public_html, right-click on them, and select File Permissions over again:

Setting new file permissions
Setting new file permissions

This fourth dimension, set the options in the permissions window to the following:

  • The Numeric Value should be 644.
  • Recurse into subdirectories should nonetheless be checked.
  • Apply to files simply should exist selected.

Then, return to your site to see if this solves the problem and the "Sorry, you are non allowed to admission this folio" message is gone.

x. Create a New .htaccess File

If none of the above strategies have worked, you may need to reset your .htaccess file. To do so, launch FTP and navigate to your public_html folder. You should see your .htaccess file in that location, but if you don't, follow instructions for showing hidden files in FileZilla.

Next, you'll need to rename your existing .htaccess file, like to how nosotros renamed plugin and theme files in earlier solutions. Something recognizable such as .htaccess_original or .htaccess_backup is ideal.

Then, right-click on the file and select Download. Open the file in a text editor and supersede its contents with the following:

          #BEGIN WordPress  RewriteEngine On  RewriteBase /  RewriteRule ^index\.php$ - [L]  RewriteCond %{REQUEST_FILENAME} !-f  RewriteCOnd %{REQUEST_FILENAME} !-d  RewriteRule . /index.php [L]  #END WordPress        

Rename this file .htaccess and upload it to your server. If this file was the source of the "Sad, yous are non allowed to access this page" fault, then it should now be stock-still.

11. Reset Your WordPress Site

In the worst-instance scenario, there may be an installation outcome. To prepare it, you lot'll have to reset your WordPress site. Information technology'southward vital that you have a recent backup you can restore after this process is consummate, as resetting your site volition crusade you to lose all posts, pages, and user comments.

There are several methods for doing this, including via your MyKinsta dashboard, using a WordPress plugin, and by using WP-CLI (the WordPress control line). It'south best to salve this route as a last resort, so you don't risk losing your site's content.

Are yous getting the awfully alarming *Sorry, Yous Are Non Allowed to Access This Page* bulletin? Try one of these methods to get your admission back! 🙅‍♂️🔑 Click to Tweet

Summary

Being locked out of your admin dashboard in WordPress is nerve-wracking, to say the to the lowest degree. Quickly finding the right solution to the "Sorry, you lot are not immune to admission this folio" error is vital to both your site and your peace of listen.

In this post, we covered a broad range of possible causes and fixes for this issue. Permit's recap them rapidly:

  1. Restore a previous version of your site.
  2. Disable all of your plugins.
  3. Activate a default theme.
  4. Make sure you're an administrator.
  5. Bank check your fault log to pinpoint the cause.
  6. Ensure that your database prefix is correct.
  7. Look for changes in your wp-config.php file.
  8. Upgrade to the latest version of php.
  9. Evaluate your file permissions.
  10. Create a new .htaccess file.
  11. Reset your WordPress site.

Happy fixing!


Salve time, costs and maximize site operation with:

  • Instant assistance from WordPress hosting experts, 24/7.
  • Cloudflare Enterprise integration.
  • Global audience attain with 32 data centers worldwide.
  • Optimization with our built-in Application Functioning Monitoring.

All of that and much more, in 1 programme with no long-term contracts, assisted migrations, and a 30-solar day-coin-back-guarantee. Check out our plans or talk to sales to notice the plan that'south right for yous.