\/wp-admin<\/code>), it is usually due to a domain configuration error, a plugin conflict, or security settings. This guide combines multiple troubleshooting methods into one clear path to help you regain access quickly.<\/p>Step 1: Check for Firewall or IP Blocks<\/h2>
If you see a 403 Forbidden error or a connection timeout, your IP address may have been flagged by our security systems. This often happens if an IP is linked to previous malicious activity or has a poor reputation.<\/p>
\n- Verify your IP: Find your current IP address (e.g., search “what is my IP” on Google).<\/li>\n
- Contact Customer Success: Reach out to our support team via live chat. We will check if your IP is currently blocked by our firewall.<\/li>\n
- Review the outcome: Our team will confirm whether the block can be safely removed.\n
\n- If the IP has a history of harmful behavior, we may not be able to unblock it for network safety.<\/li>\n
- In such cases, you may need to contact your ISP for a new IP or use a VPN to access your dashboard.<\/li>\n<\/ul>\n<\/li>\n<\/ol>
Step 2: Check DNS records<\/h2>
Ensure that the domain points to Hostinger<\/b> by either nameservers or A record.<\/p>\n- \n
Check A Record DNS: Making Sure Your Domain is Correctly pointed<\/a><\/p>\n<\/li>\n- \n
How to look up domain nameservers<\/a><\/p>\n<\/li>\n<\/ol>Step 3: Deactivate plugins<\/h2>
There are a few plugins that can protect the login page<\/a> by restricting access to it, adding 2-factor authentication, or captcha features, such as WordFence, Force Login, WPS Hide Login, among others.<\/p>There are a couple of options if you wish to deactivate some plugins but don’t have access to your WordPress administrator page.<\/p>
Disabling plugins via the WordPress dashboard<\/h3>
In your Hostinger account, go to Websites<\/a> <\/b>→ Dashboard <\/b>next to the site in question. Then, search for Security<\/b> on the sidebar and click on it:<\/p>![\"Hostinger](\"\/support\/wp-content\/uploads\/sites\/55\/2024\/07\/8e5cc239-b5de-4116-8e32-d376d841c305.jpg\")
<\/div>Scroll down to the section Installed plugins<\/b> to find all the plugins currently installed on your website. Move the toggle to disable or enable them:<\/p>Disabling plugins via the file manager<\/h3>
If you don’t have the WordPress dashboard enabled or prefer managing data via files, you can disable the plugins using the file manager.<\/p>
\n- Open your website’s File Manager<\/a><\/b> and access its wp-content<\/b> folder (
domains\/domain.tld\/public_html\/wp-content<\/code>). There, you’ll find the plugins <\/b>folder:![\"Hostinger](\"\/support\/wp-content\/uploads\/sites\/55\/2024\/07\/b8d6fd0f-16f0-432e-a783-ce2b0cd23b70.jpg\")
<\/li>\n- You can rename the entire plugins <\/b>folder to plugins_disabled<\/b> (or any different name) – this way, you’ll disable all the plugins inside this folder:<\/li>\n<\/ol>
![\"WordPress](\"\/support\/wp-content\/uploads\/sites\/55\/2024\/07\/30c1db43-5930-47ee-af95-a270676a29b1.jpg\")
<\/div>Alternatively, rename the specific plugin folder within the plugins<\/b> folder.<\/p>
Now try access your WordPress admin and see if it works.<\/p>
Step 4: Disable password protection in .htaccess file<\/h2>
If you have enabled password protection for your WordPress wp-admin<\/b> page:<\/p>![\"WordPress](\"\/support\/wp-content\/uploads\/sites\/55\/2024\/07\/d83c32ce-7c46-4334-b0f1-7ab4676db977.jpg\")
<\/div>You can disable it by following these steps:<\/p>
\n- \n
Reach the wp-admin<\/b> folder using a file managing tool.<\/p>\n<\/li>\n- \n
Open the .htaccess <\/b>file in edit mode.<\/p>\n<\/li>\n- \n
Remove or comment these lines:<\/p>\n<\/li>\n<\/ol>
AuthType Basic\r\nAuthName \"Protected 'public_html\/wp-admin'\"\r\nAuthUserFile \"\/home\/dir\/.htpasswds\/public_html\/wp-admin\/passwd\"\r\nRequire valid-user<\/code><\/pre>\nTo comment out a line, add a #<\/code> symbol at the beginning. This will prevent its content from being executed 💡<\/p>\n<\/div>Save the changes, and test it by accessing your wp-admin<\/b> again, it should load now ask only for the WordPress username and password.<\/p>
Alternatively, disable the .htaccess by renaming it to .htaccess-disabled (or any other name)<\/p>
Step 5: Reset to default .htaccess file<\/h2>
If the issue persists, create a new .htaccess file and paste the default code.<\/p>
\n- \n
Access the website’s webroot <\/b>folder in the file manager.<\/p>\n<\/li>\n- \n
Find .htaccess<\/b> file there and rename<\/b> it. You can rename it to .htaccess-old. This will disable the old file.<\/p>\n<\/li>\n- \n
Create a new file called .htaccess<\/b> and add the following default WP code.
\nYou can find it here
\n
\n#BEGIN WordPress
\n<IfModule mod_rewrite.c>
\nRewriteEngine On
\nRewriteBase \/
\nRewriteRule ^index.php$ – [L]
\nRewriteCond %{REQUEST_FILENAME} !-f
\nRewriteCond %{REQUEST_FILENAME} !-d
\nRewriteRule . \/index.php [L]
\n<\/IfModule>
\n#END WordPress<\/i><\/p>\n<\/li>\n<\/ol>Step 6: Reset to default wp-config.php<\/b><\/h2>
If the issue persists, enable a default wp-config.php<\/b> file<\/p>\n- \n
Access the website’s webroot <\/b>folder in the file manager.<\/p>\n<\/li>\n- \n
Find wp-config.php file and rename<\/b> it. You can rename it to wp-config.php-old<\/p>\n<\/li>\n- \n
Create a new file called wp-config.php and add the default sample WP code<\/b> that you can find here<\/a>.<\/p>\n<\/li>\n- \n
Locate and copy <\/b>the following details from the old file: wp-config.php-old<\/b> and fill them under the new wp-config.php<\/b> file:<\/p>\n\n- \n
Database name<\/b><\/p>\n<\/li>\n- \n
Database Username<\/b><\/p>\n<\/li>\n- \n
Database password<\/b><\/p>\n<\/li>\n- \n
Database prefix<\/b><\/p>\n<\/li>\n- \n
Keys\/salts<\/b>. These can be either<\/b> copied from the old wp-config.php file or<\/b> generated here<\/a><\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>Step 7: Check Malware scanner report<\/h2>
If you see that the domain is pointing correctly, but the admin page still does not open, check out malware scanner to see if no malware was detected:<\/p>
\n- Go to your website dashboard<\/strong>.<\/li>\n
- Find security<\/strong> tab at the left side of your dashboard.<\/li>\n
- Click on Malware Scanner <\/strong>category under security tab.<\/li>\n
- If your website has been affected by malware – follow cleanup steps: How to fix malware-infected WordPress Website at Hostinger.<\/a><\/li>\n<\/ol>
Other Important things to check if the issue persists:<\/h3>\n- \n
If the domain is not pointed to Hostinger, follow the guide here: How to point a domain to Hostinger<\/a><\/p>\n<\/li>\n- \n
Check if the database limit<\/a> is reached and follow the steps here: What to Do If the Database Size Limit Has Been Reached<\/a><\/p>\n<\/li>\n- \n
Check if the website is affected by malware: How to use the malware scanner at Hostinger<\/a><\/p>\n<\/li>\n- \n
If you encounter a 403 error on your website, restoring the core WordPress system files<\/a> can help resolve the issue.<\/p>\n<\/li>\n- \n
If you see the ERR_SSL_PROTOCOL_ERROR, follow this step-by-step SSL troubleshooting guide<\/a> to fix the problem.<\/p>\n<\/li>\n- \n