Being told you’re “not allowed to access this page” on your own WordPress site is disorienting, especially when you’re the administrator. It’s a user-role or database issue rather than a true permissions restriction, and it’s fixable. Here’s how to get back in.
What usually triggers it
This message appears when WordPress thinks your account lacks the capability to view a page. Common causes are a role that got corrupted during a migration, a database table prefix mismatch, a plugin conflict, or a PHP version change that broke how roles are stored.
Check the table prefix
After a migration, a classic cause is a mismatch between the table prefix in wp-config.php and the actual prefix in the database. Open wp-config.php and note the $table_prefix value. Then in phpMyAdmin, check the actual prefix on your tables (e.g. wp_ or something custom). They must match exactly — if they don’t, correct the config line.
Rebuild your user’s capabilities
If the prefix is fine, your admin role’s capabilities may be corrupted in the wp_usermeta table. The cleanest fix is often to create a fresh administrator account directly in the database, then log in with it. You can do this in phpMyAdmin by adding a new user row and a matching capabilities entry, or via a small snippet added temporarily to your theme’s functions file.
Rule out a plugin
Membership, security and role-management plugins can restrict access in ways that lock out even admins. Disable plugins by renaming the plugins folder in File Manager. If access returns, reactivate them one at a time to find the offender.
Check PHP compatibility
This error sometimes appears right after a PHP upgrade, when a plugin that manages roles breaks on the new version. In MultiPHP Manager, roll back to the previous version. If that restores access, update the offending plugin before upgrading PHP again.
Increase memory
Occasionally the page simply runs out of memory partway through checking permissions. Raising the memory limit in wp-config.php is a quick thing to rule out.
If a prefix mismatch or corrupted role is behind it, the database work can be delicate. Rather than risk it, open a ticket and we’ll restore your admin access safely.
