Why can’t I enter the WordPress backend?
Many Internet marketers are using WordPress for search engine optimization.
However, sometimes you suddenly cannot log in to the WordPress backend and will jump to such a connection repeatedly.
https://域名/wp-login.php?redirect_to=https%3A%2F%2F域名%2Fwp-admin%2F&reauth = 1
This situation of being unable to log in to WordPress is a common phenomenon:
In the background login interface, after entering the account and password,
click to enter, but there is no response or prompt...
Cannot log in even if you change the browser.
Solution 1
Step 1: Open the WordPress system file ▼
/wp-includes/pluggable.php
Step 2: Use the find tool to find this line of code▼
setcookie($ auth_cookie_name,$ auth_cookie,$ expire,ADMIN_COOKIE_PATH,COOKIE_DOMAIN,$ secure,true);
Please note that different versions of WordPress may have different lines of code.
Step 3: All you have to do is find all these codes and replace them with ▼
setcookie($ auth_cookie_name,$ auth_cookie,$ expire,SITECOOKIEPATH,COOKIE_DOMAIN,$ secure,true);
Solution 2
If both There is a conflict between plugins, and WordPress plugins can sometimes cause this problem.
Disable all plugins:
Please use an FTP client to connect to your virtual host.
Rename the /wp-content/plugins/ directory to plugins_backup.
This will deactivate all WordPress plugins installed on your site.
Once you have deactivated all plugins, try logging into your WordPress site.
If you log in successfully and see a prompt about a plug-in error in the background, it means that one of your plug-ins is causing the problem.
You only need to rename the plug-in through FTP software (rename shortcut key: F2), and you can directly deactivate the plug-in.
Solution 3
If you use the plug-in directory renaming method, disable all WP plug-ins, successfully log into the WordPress backend, and do not see any plug-in error prompts.
I only see error messages similar to the following
Warning: Unable to modify title information - already in (home/username/web/domainname/public_html/wp-content/advanced-cache.php: headers sent in 26) /home/username/web/domainname/public_html/wp-admin/includes/misc.php
on line 1116 of /home/username/web/domainname/ headers sent in username/web/domainname/public_html/wp-content/advanced-cache.php:26) /home/username/web/domainname/public_html/wp-includes/option.php# on line 919
##Warning: Unable to modify header information - header already sent in (home/username/web/domainname/public_html/wp-content/advanced-cache.php:26)/home/username/web/ domain name/public_html/wp-includes/option.php at line 920. Therefore, the error may not be caused by the WordPress plugin. The following is the solution for netizens to test successful login: Through "Quick Edit", let WordPress pop up a small login window Enter WordPress article editing page/wp-admin/edit.phpEnable plug-in back: Change back to the previously changed WP plug-in directory name. On the article editing page, click "Quick Edit". After clicking "Quick Edit" and waiting for a few seconds, a small login window will pop up, requiring you to enter your login account and password. Enter your account password and you will be able to log in successfully. (Because the login will not be redirected by popping up the "small login window")Final solution
Delete the manual addition Code of functions.php: If you have manually added other codes to the functions.php file, please back up the code first. Then, test removing the code you added manually. If you can successfully log in to the WordPress backend after deletion, it means there is a problem with the code of the functions.php file. Need to check one by one, which code is wrong? Some network promotion operators said that they used the following "delete 1/2 of the code to troubleshoot" method to troubleshoot, and successfully deleted a manually added code, which perfectly solved the problem. .Delete 1/2 of the code for troubleshooting
Step 1: Delete half of the function code firstFor example, if you are in the functions.php file , manually added 10 function codes, and first tested to delete half (5) codes. Step 2: In an incognito window of the browser, log in to the WordPress backend againIf you find that you can successfully log in to the WordPress backend, it means that the half of the code you just deleted is wrong. If you cannot successfully log in to the WordPress backend, it is because the half of the code that has not been deleted is wrong. Step 3: Continue to test the half of the error codeContinue to repeat the above two steps and test the half of the error code until you successfully log in to the WordPress backend. For more WordPress technical articles, please visit theWordPress Tutorial column!
The above is the detailed content of Why can't I enter the WordPress backend?. For more information, please follow other related articles on the PHP Chinese website!