How to reset WordPress admin/users password from Linux command line?

1, Log into server as root.
2, Enter to MySQL command prompt.

[root@vps ~]# mysql
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 265
Server version: 5.1.73 Source distribution

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.


3, Use WordPress database.

You can check the database name from the WordPress configuration file.

mysql> use user_images;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed

4, Verify user details from “wp_users” table.

We need to select only the following details from “wp_users” table.

mysql> SELECT ID, user_login, user_pass FROM wp_users;
| ID | user_login | user_pass                          |
|  1 | admin      | $P$BjUKUieEYT1B3TnkQHsv4Y8hfnSK5t. |
1 row in set (0.00 sec)


This WordPress has only one user “Admin”. The password displayed here isn’t real, it’s in MD5 encrypted format.

5, Updating user password.

This is the point that we are looking for. As I mentioned, the password displayed is in MD5 format. In latest MySQL versions we can generate the password in MD5 format from the commandline itself. Please see the syntax:

mysql> UPDATE wp_users SET user_pass = MD5(‘WPEXPLORER’) WHERE ID=1 LIMIT 1;

In previous versions we have to enter the password in MD5 format. It’s simple, we can generate it from here >> MD5 <<

Syntax to change the password

mysql> UPDATE wp_users SET user_pass = "61250b88abfe298f2df4821d081a3add"  WHERE ID=1;

Here the user pass in MD5 format.

See the updated password:

mysql> SELECT ID, user_login, user_pass FROM wp_users;
| ID | user_login | user_pass                        |
|  1 | admin      | 61250b88abfe298f2df4821d081a3add |
1 row in set (0.00 sec)


Screenshot from 2015-04-25 19-55-07

That’s it!! Now try to login with the new password.

For more details, check the below url.


JETPACK Troubleshooting Tips

Troubleshooting Tips

Are you having trouble with Jetpack or one of its components? If so, here are a few key steps that can help you solve the problem.

  1. Check if the error you received is listed on this page. If it is, you can follow the instructions there to solve the issue.
  2. Disable all other plugins, then try connecting or using Jetpack. If Jetpack starts connecting or working properly, turn your plugins back on one-by-one until you start seeing the error again. Then note the plugin that caused this error and get in touch with us. Sometimes Jetpack and other plugins are incompatible; just let us know and we’ll see what we can do.
  3. If you are having a display issue, or the plugin step above doesn’t help, try activating Twenty Fifteen or Twenty Sixteen (one of the default WordPress themes) as your theme. Then try again. If your action starts working, something in your theme is likely broken and you should get in touch with your theme’s author. Be sure to let them know the troubleshooting steps that you have tried.
  4. Check your XMLRPC file. You can do this by going to your web site URL and adding “/xmlrpc.php” to the end (without the quotes). When it loads in your browser, you should see “XML-RPC server accepts POST requests only.” on a line by itself.
    • If you see this message, but it is not on a line by itself, a theme or plugin is displaying extra characters when it shouldn’t. See points 2 and 3 above for debugging steps.
    • If you get an 404 Error Not Found message, contact your web host. They may have security in place that is blocking XML-RPC.
  5. Do you use an SSL certificate on your site? Try adding the following to your site’s wp-config.php file:
    define( 'JETPACK_SIGNATURE__HTTPS_PORT', 80 );

    This works on hosts that have SSL terminate on a reverse proxy and the server itself is still listening on port 80 or something similar.

    Alternatively, you could add this to your wp-config.php file (please not both!):

    $_SERVER['SERVER_PORT'] = 443;

    This sets the server port to 443 for the whole site.

  6. If you’ve installed an SSL certificate on your domain and if can’t access your site via HTTPS, start by checking the status of your domain’s SSL certificate. If you can’t fix the SSL issues on your site, try adding the following to your site’s wp-config.php file to bypass the HTTPS check during the connection:
    define( 'JETPACK_CLIENT__HTTPS', 'NEVER' );
  7. Check the Known Issues list and make sure you aren’t using a plugin or theme listed there.
  8. If you were using Development Mode, check your wp-config.php file and make sure that define('JETPACK_DEV_DEBUG', true); is no longer present.

Upgrade WordPress Manually

Step 1. Go to the page in google [ Download latest version of wordpress ]

Step 2. Copy the link address

Step 3. Wget link [ From the server and also in the folder where wordpress installed ]

step 4. unzip Download file

step 5. remove or rename wp-admin and wp-includes [currently installed ]

Step 6. GO to download folder and remove wp-content [from the file,above we download ]

step 7. copy the files in the download download folder to the wordpress installation folder
{ # cp -pr * ../- command used to copy to the parent dir }

Steo 8 change ownership of files and folders

step 9 go to
{for upgrading database }

[ Refer to the url for more information – ]

wordpress “Briefly Unavailable For Scheduled Maintenance” Message Remainins After An Automatic Upgrade

Your WordPress site is showing “Briefly unavailable for scheduled maintenance” after an automatic upgrade has completed.

Solution: Remove .Maintenance File

A file named .maintenance is placed by WordPress during an automatic upgrade to notify visitors that the site in under a short maintenance. If an upgrade fails or is corrupted, the file will remain in the WordPress folder and won’t get deleted.

To remove .maintenance file,

  1. Access your blog root directory via FTP.
  2. Locate the file .maintenance.
  3. Remove the .maintenance file from the blog root directory.

Once you solve this problem, you may want to run the WordPress automatic upgrade again.

WordPress Admin Login 404 Issue

You’re not able to login to WordPress admin. You receive a 404 error page instead.

Solution 1: Update The URL In Database

If you’re able to access phpMyAdmin, try to update the URL in the database.

  1. Login cPanel, click on phpMyAdmin under Databases.WordPress Admin Login 404 Issue - 10 Most Common WordPress Errors (+Solutions)
  2. Select your WordPress database. For example: Username_wrdp1.
  3. Go to wp_options, click on Browse.WordPress Admin Login 404 Issue - 10 Most Common WordPress Errors (+Solutions)
  4. Search for siteurl under the field option_name.
  5. Click on Edit Field.WordPress Admin Login 404 Issue - 10 Most Common WordPress Errors (+Solutions)
  6. Change the URL in the input box of option_value.WordPress Admin Login 404 Issue - 10 Most Common WordPress Errors (+Solutions)
  7. At the bottom of page, click the Go button.

Solution 2: Update Folder Attributes

  1. Go to “/wp-admin” directory via FTP.
  2. Right click on wp-admin directory and click on File Attributes.
  3. Update the value to 755 and check Recurse into subdirectories if there’s an option.WordPress Admin Login 404 Issue - 10 Most Common WordPress Errors (+Solutions)
  4. Click OK.
  5. Repeat step 1 to step 4 for /wp-content and wp-includes.
  6. Open your web browser and try to login to WordPress admin. Press Ctrl + F5 to clear cache

WordPress – Fatal Error: Allowed Memory Size Of 33554432 Bytes Exhausted

Receive “Fatal error: Allowed memory size of 33554432 bytes exhausted” when try to upload an image with medium file size. To solve this error, try to increase the memory allocated to PHP. You can set the limit to 32MB, 64MB, 128MB or 256MB. It depends on your host.

Solution 1: Edit PHP.Ini

If you’re still allowed to edit your PHP.inifile, update your memory_limit in PHP.ini by modifying the below line

memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)

If the line is showing 64M in default, try 128M.

Solution 2: Edit .Htaccess File

Add the script below to your .htaccess file.

php_value memory_limit 64M

Solution 3: Edit Wp-Config.Php File

Add the script below to your wp-config.php file

Increasing memory allocated to PHP
define('WP_MEMORY_LIMIT', '64M');

Solution 4: Create A PHP.Ini File To Wp-Admin Folder

  1. Open Notepad.
  2. Insert the following code into Notepad.
    memory_limit = 64M ;
  3. Save as “PHP.ini”.
  4. Upload this file to “wp-admin” directory.