Support » Fixing WordPress » Can’t login on /wp-login.php

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator t-p

    (@t-p)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thank you so much for your help. I have:

    • Reset plugins through phpMyAdmin
    • Renamed the theme directory (appending “_old”)
    • Renamed htaccess to htaccess_old. This caused the whole site to disappear, but didn’t fix the problem.

    When downloading the raw logs, I see a 200 for wp-login.php at line 3845, but a 500 at line 3847:

    107.172.1.224 – – [01/Nov/2016:06:30:33 -0600] “GET /wp-admin/post-new.php HTTP/1.1” 200 1079 “http://www.searchify.ca/wp-login.php?redirect_to=http%3A%2F%2Fwww.searchify.ca%2Fwp-admin%2Fedit-tags.php%3Ftaxonomy%3Dcategory&reauth=1” “Opera/9.80 (Windows NT 6.2; Win64; x64) Presto/2.12.388 Version/12.17”
    192.0.101.226 – – [01/Nov/2016:06:31:30 -0600] “HEAD / HTTP/1.1” 200 – “-” “jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)”
    91.210.146.222 – – [01/Nov/2016:06:32:15 -0600] “POST /wp-login.php HTTP/1.1” 500 – “http://searchify.ca/wp-login.php” “Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36”

    I can’t see any data from this morning after 9:40, as those logs aren’t available yet.

    However, in htaccess I see references to the plugins that are now deleted. Can I replace the old htaccess with a generic new one, or perhaps remove these manually? Or is it something else?

    Thanks again for your help!

    I’ve tried to replace the site’s htaccess with a new, clean htaccess as listed here: https://codex.wordpress.org/htaccess (the one for Basic WP). That doesn’t work either…

    Thanks again for any help.

    Alright, the problem has been solved! When copying the files from a new WP install to the server, I told Filezilla to override existing files. As someone pointed out, this doesn’t guarantee that the file gets copied correctly. I had to delete existing files first and then copy them to the server. That worked like a charm.

    Thanks for all the help!

    Moderator t-p

    (@t-p)

    Glad to know you got it sorted 🙂

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Can’t login on /wp-login.php’ is closed to new replies.