Admin Access Issues

Use this guide when you cannot access the WordPress Admin area, the login page does not load, or /wp-admin returns a redirect, permission, or blocked-access error.

This guide covers WordPress Admin access. It does not cover problems signing in to the Pressidium Dashboard.

Symptoms

You may experience one or more of the following:

• /wp-login.php does not load
• WordPress rejects your login credentials
• /wp-admin redirects repeatedly
• you see an access-denied or blocked-request message
• the Admin area loads without styles, scripts, or some pages
• access works from one browser or network but not another
• one WordPress user is affected while other administrators can sign in
• the website loads, but WordPress Admin does not

Likely causes

WordPress Admin access issues commonly result from:

• an expired or corrupted browser session
• incorrect WordPress credentials
• a problem affecting one WordPress user account
• an IP restriction, Geo-blocking rule, or security rule
• conflicting redirects or incorrect WordPress URL settings
• a recent domain, DNS, or SSL change
• a plugin, theme, or WordPress core change
• a wider website availability or connectivity issue
• a recent custom cache or routing configuration change

Resolution steps

Follow the steps in order until you identify the affected area.

1. Confirm the scope

Test:

• the website homepage
• /wp-login.php
• /wp-admin

Then determine whether:

• the entire website is unavailable
• only WordPress Admin is affected
• only one WordPress user is affected
• only one browser, device, or network is affected
• all administrators are affected

If the entire website is unavailable, follow [Troubleshoot website availability] before continuing with WordPress Admin-specific checks.

2. Test a clean browser session

1. Open a private or incognito browser window.
2. Go directly to /wp-login.php.
3. Enter your WordPress credentials.
4. Check whether the login completes.
5. If it does not, try another supported browser.

If access works in a private window, clear the cookies and stored site data for the affected domain in your normal browser.

3. Check the WordPress user account

Use this path when the login page loads but WordPress rejects the credentials.

1. Confirm that you are using the correct username or email address.
2. Reset the affected WordPress user password.
3. Try signing in again from a private browser window.
4. Test another administrator account, when one is available.

Reset a WordPress user password to restore access for the affected user.

If another administrator can sign in, the issue is likely limited to the original user account.

4. Check for blocked or restricted access

Use this path when you see an access-denied, forbidden, or blocked-request message.

1. Test from another network, such as a mobile connection.
2. Check whether another administrator can access WordPress Admin.
3. Review recent IP Blocklist, IP Allowlist, Geo-blocking, firewall, or login-protection changes.
4. Record your public IP address, the blocked URL, and the approximate timestamp.

If legitimate access remains blocked, contact Support with those details.

5. Check redirect, domain, and SSL changes

Use this path when the browser redirects repeatedly or the login page fails to load correctly.

1. Test the login URL in a private browser window.
2. Clear browser cookies for the affected domain.
3. Review recent domain and redirect changes.
4. Confirm that HTTPS loads without a certificate warning.
5. Check whether the issue affects both the www and non-www versions, when both are configured.
6. Review any plugin that changes login URLs or redirect behavior.

If you cannot access WordPress Admin to review plugin-level redirects, contact Support.

6. Check DNS and connectivity

Use this path when the login page and website do not load consistently.

1. Confirm that the domain resolves to the expected Pressidium destination.
2. Check whether recent DNS changes have propagated.
3. Test the website from another network.
4. Confirm whether the problem affects the entire website or only WordPress Admin.

Check whether DNS changes have propagated after changing records.

Find your website’s IP addresses when you need to verify the configured destination.

7. Review recent WordPress changes

Review changes made shortly before the issue began, including:

• plugin installation, activation, or updates
• theme changes or updates
• WordPress core updates
• login or redirect plugin changes
• custom code changes
• changes to WordPress URL settings
• changes to security or access-control plugins

When a recent plugin or theme change is the likely cause, follow the relevant compatibility troubleshooting guide instead of making several unrelated changes at once.

8. Review cache configuration only when relevant

WordPress Admin access problems are not normally resolved by clearing cache alone.

Review cache behavior when:

• the issue began after a cache-rule change
• the login or Admin path was added to custom caching rules
• Admin assets appear outdated or incomplete
• a redirect or configuration change is not reflected

Clear your website cache and retest from a private browser window.

Verification

After applying a fix, confirm that:

• /wp-login.php loads without errors
• your credentials are accepted
• /wp-admin opens without a redirect loop
• Admin pages load their styles and scripts
• you can open more than one Admin page
• another administrator can sign in when needed
• access still works in a new browser session
• the issue no longer depends on a particular browser or network

Need help?

Contact Support if:

• no administrator can access WordPress Admin
• the login page remains unavailable
• you continue to see a blocked or access-denied message
• the issue began after a domain, DNS, SSL, or infrastructure change
• you cannot reverse a recent plugin, theme, or redirect change
• the issue remains after completing the relevant checks

Include:

• the affected domain
• the WordPress Admin URL
• the exact error message or screenshot
• the affected username or role, when relevant
• your public IP address when access is blocked
• the approximate date and time
• the browsers and networks tested
• recent changes made before the issue began
• the troubleshooting steps already completed

Do not include passwords or other sensitive credentials.

Where to go next

• Reset a WordPress user password when one user cannot sign in.
• Check whether DNS changes have propagated when access changed after a DNS update.
• Find your website’s IP addresses to verify the DNS destination.
• Clear your website cache when a relevant cache or routing configuration changed.
• Troubleshoot plugin compatibility problems when the issue began after installing, activating, or updating a plugin.
• Review website firewall controls when legitimate Admin traffic appears to be blocked.