Resetting a WordPress password (three ways)

If you know your email but not your password, use the Lost your password? link on your WordPress login screen first. It's the fastest fix and needs no technical steps. If email delivery is the problem, or you're locked out of the admin account entirely, you have two more options: resetting the password directly in the database through phpMyAdmin, or using a reset plugin. Both are covered below.

Method 1: the login screen (try this first)

Go to yourdomain.com/wp-login.php and click Lost your password? Enter the username or email tied to the account and submit. WordPress emails a reset link to the address on file. Click it, set a new password, and log in.

This only works if the site can actually send mail and you still have access to that inbox. If the email never arrives, check spam first, then move to method 2. Mail delivery issues on WordPress are usually a plugin or configuration problem, not a Flashcloud limitation. A page that hangs on wp-login.php can also point to a caching or plugin conflict rather than mail delivery. Flashcloud hosting runs on LiteSpeed with LSCache, so on most accounts clearing the LiteSpeed Cache plugin's cache is worth trying before you dig further.

Method 2: reset it in the database with phpMyAdmin

Use this when the reset email never arrives, the admin email address is wrong or no longer exists, or you can't reach wp-login.php at all.

1. Log into your Flashcloud portal, open phpMyAdmin for the site's hosting account.
2. Select the WordPress database in the left sidebar, then open the wp_users table (the prefix may differ if it was customized during install).
3. Find the row for your admin account and click Edit.
4. In the user_pass field, clear the existing value and type your new password.
5. WordPress stores passwords hashed, so make sure phpMyAdmin is set to hash the new value before saving. If you skip this step and save plain text, the password won't work.
6. Click Go to save the row.

Log in at wp-login.php with the new password immediately. If it doesn't work, double check that the value was hashed and that you edited the correct row. WordPress installs with multiple admin users are an easy place to edit the wrong one.

Method 3: a password reset plugin

If you have file access (FTP or File Manager) but the database route feels risky, a small reset plugin is a safer middle ground. The general shape:

• Upload a WordPress password-reset plugin's files to wp-content/plugins/ via FTP or File Manager. This works even without logging into wp-admin.
• Some tools run as a standalone script rather than a plugin, uploaded to the site root and run once from the browser.
• Follow the tool's own instructions to reset the target account's password.
• Delete the plugin or script immediately after use. An unauthenticated password-reset tool left sitting on a live site is a real security hole. Don't skip this step.

This method is a fallback for when you can't reach phpMyAdmin easily. Most people are better served by method 2.

Before you touch the database, back it up

A direct database edit is low-risk if you're only touching one field, but it's still a live production edit. If you're already in there for other cleanup, or you're not confident about which row is which, back it up first. Your hosting account's automatic backups run through JetBackup, reachable from cPanel, and can restore the database on its own without touching your files. See My WordPress site is slow for unrelated performance issues that sometimes get blamed on login problems. A site that times out on wp-login.php can look like a password problem when it's actually a caching or plugin issue.

If you're planning bigger changes around the same time, such as a security plugin swap or a user role cleanup, do that on a staging copy first. See Using WordPress staging.

When to contact support

If you don't have portal access to reach phpMyAdmin, or you're not comfortable editing the database directly, open a ticket from the portal (Support → New ticket). Our team can help you regain access. Have your domain name and the affected username ready so the ticket moves along.