Related

Error establishing a database connection Question Question
How to set ssl certificate on apache2, 1 droplet server running 2 wordpress websites? Question Question

Question

WP admin not found 404 error

Posted December 17, 2016 14.2k views
WordPressUbuntu 16.04

Hi,

From today onwards I am unable to access my www.technicalnotes.org/wp-admin page. Whenever I try to access it, it shows not found 404 page. It’s been a year and it was working fine with www until today.

I have set a permanent redirect to www, so that even the non-www version gets redirected to www version of the website using ht.access.

While looking for a solution, I remove the code

RewriteCond %{HTTPHOST} ^technicalnotes.org$ [NC]
RewriteRule ^.*$ http://www.technicalnotes.org%{REQUESTURI} [R=301,L]

From my .htaccess file.

After this, if I visit technicalnotes.org/wp-admin I am able to see the login page. But, if I use www.technicalnotes.org/wp-admin, the login page shows 404 not found error.

I am unable to find what’s exactly stopping it from showing login page if I visit www version of the website.

Any help on how to resolve this would be appreciated.

Things I have tried:

Changing the theme
Deactivating all the plugins
changing permission for WP-admin and WP-content to 755

Nothing works.

Add a comment
tashreef
By:
tashreef
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
3 answers
ryanpq December 22, 2016

Please try logging into your wp-admin and then look at what is recorded in /var/log/apache2/error.log and share it here. If you can also share your virtualhost configuration from the file in /etc/apache2/sites-enabled it could help.

If you’re using nginx, let us know. The two files you would need then would be /var/log/nginx/error_log and /etc/nginx/sites-enabled/

Reply Report
tashreef December 23, 2016

Hi ryanpq, thank you for the reply,

But seems like the problem was at Google’s end. I am using Google Publish, it might have caused the problem. It is resolved as I contacted them.

Reply Report
jianum94 April 22, 2019

I had the same issue after I installed the nginx on my server.
The error was caused by some bad statements in my conf file. I just had to add this to the conf file:

include fastcgi.conf;
fastcgi_intercept_errors on;
fastcgi_index index.php;

I used this tutorial, check maybe it will help.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help