How to Enable Two-Factor Authentication for Plesk and WordPress

Turn on 2FA for the Plesk panel and every WordPress admin, choose an authenticator app, keep recovery codes, and enforce it so a leaked password is not enough.

Published
Reading time
3 min

Passwords leak. They are reused, phished, guessed and sold, and the best password in the world does not help if it was typed into a fake login page. Two-factor authentication adds a second thing the attacker does not have: a six-digit code from your phone. Turning it on for the two logins that control everything — the hosting panel and the site's admin — takes ten minutes.

Pick an authenticator app

Any TOTP app works: Google Authenticator, Microsoft Authenticator, Authy, 1Password, Bitwarden. Prefer one that backs up its codes (Authy, 1Password, Bitwarden, Microsoft with a cloud backup) — a lost phone with Google Authenticator and no backup means a recovery-code hunt for every account. Avoid SMS codes where an app is offered; SIM-swap attacks are routine.

Plesk

  1. Log in and click your name at the top right → My Profile (or Edit Profile).
  2. Two-Factor Authentication (it may be under a Security tab, or as a separate item in the left menu on older versions; if it is absent, an admin installs the free Multi-Factor Authentication extension first).
  3. Click Enable, scan the QR code with the app, enter the code it shows.
  4. Save the recovery codes somewhere that is not the same phone — a password manager or a printed sheet. They are the only way back in if the phone is lost.

From now on, the panel asks for a code after the password. Because Plesk is where the files, databases, DNS and mail for every site live, this is the single most valuable 2FA on the server.

For other users: as administrator, Tools & Settings → Multi-Factor Authentication lets you require it for all panel users; each is prompted to set up at next login. Customers on a reseller plan get the same option in their own profile.

WordPress

WordPress has no built-in 2FA; a plugin adds it. Two we recommend:

  • Two-Factor (by the WordPress core team's contributors) — minimal, no upsell, supports TOTP apps, email codes and security keys.
  • WP 2FA — more options, including enforcing 2FA for specific roles with a grace period.

Install, activate, then Users → Profile → Two-Factor Options: enable Time Based One-Time Password, scan the QR, confirm with a code, and save the backup codes. Do this for every administrator account, then under the plugin's settings enforce it for the Administrator and Editor roles so new users cannot skip it.

With WordPress Toolkit in Plesk, the Security checklist can also Enable two-factor authentication which installs and configures a plugin for you.

Enforce, don't suggest

A team where 2FA is optional has 2FA on the people least likely to be phished. Make it required for anyone with admin rights, and set a date after which accounts without it are locked. Both Plesk and the WP 2FA plugin support this.

Security keys

For the highest-value logins, a hardware key (YubiKey or any FIDO2 key) is phishing-proof: it only signs for the real domain, so a fake login page gets nothing useful. The Two-Factor plugin supports them for WordPress; Plesk supports them from version 18.0.50 onward. Register two keys and keep one somewhere safe.

What 2FA does not cover

  • SSH and SFTP — protect with keys instead of passwords; that is stronger than 2FA.
  • Application passwords and API keys — WordPress application passwords bypass 2FA by design (they are for scripts). Audit them under the user's profile and delete any you do not recognise.
  • A session that is already logged in — a stolen cookie works until it expires. Log out of shared machines; keep sessions short.
  • The email account used for password resets. If an attacker controls your email, they reset everything. Put 2FA on the mailbox first.

Recovery

Lost the phone: use a recovery code, then re-enrol a new device and generate fresh codes. Lost both: for Plesk, an administrator can reset a user's 2FA; for the administrator account itself, root SSH access and plesk bin can disable it. For WordPress, deactivate the plugin via SFTP by renaming its folder, log in, re-enable and re-enrol. On a VPSPioneer plan, a ticket with identity verification gets either done for you.

Two-factor on the panel and the admin is the second item on our WordPress hardening checklist, after updates. Nothing else on the list matters as much if the login is one leaked password away.

#security#2fa#plesk#wordpress#authentication

Keep reading

More from Security

All guides

Security

How to Set Up Automatic Backups (and Actually Test the Restore)

The 3-2-1 rule for a web server, what to back up and how often, Plesk and command-line methods, off-site storage, and the restore test most people never do.

4 min read →

Security

How to Detect and Remove Malware From a Website

How to tell a site is infected, find the malicious files, clean or restore it, close the hole it came through, and clear Google's warning.

4 min read →

Security

First 10 Things to Do on a New Linux VPS (Security Checklist)

A 30-minute copy-paste checklist for a fresh Debian, Ubuntu or AlmaLinux VPS, with a verification command after every step so you know it worked.

6 min read →