How to log in to Plesk after the Social Login extension is removed

Question

How to log in to Plesk after the Social Login extension is removed

Answer

The Social Login extension is deprecated in Plesk Obsidian 18.0.82 and removed on upgrade to Plesk Obsidian 18.0.84. It cannot be installed again after removal. The Log in with Google, Log in with Facebook, Log in with GitHub, and passkey options disappear from the Plesk login page and from user profiles.

Plesk accounts and their passwords are not affected. After the upgrade, every user logs in with their Plesk username and password. Make sure that every user who logs in with Social Login knows their Plesk password before the server is upgraded to Plesk Obsidian 18.0.84.

Server administrator

1. If you do not know the Plesk administrator password, connect to the server via SSH (Plesk for Linux) or RDP (Plesk for Windows).
2. On Plesk for Windows, start Command Prompt as an Administrator.

3. Get a one-time login link.

   Plesk for Linux:

   # plesk login

   Plesk for Windows:

   C:\> plesk login

4. Open the link, log in, and set a new password as described in How to use token login or reset lost Plesk Administrator password?
5. Optional: protect the account with a second factor by using the Multi-Factor Authentication extension, see How to enable Two Factor Authentication (TFA) / multi-factor authentication (MFA) for Plesk login sessions.

Optional: log in with a WebPros Account (administrators)

On Plesk Obsidian 18.0.79 and later, administrators can also log in with a WebPros Account. The option is off by default and does not replace the Plesk password.

1. Create a backup copy of panel.ini. On Plesk for Linux:

   # cp -a /usr/local/psa/admin/conf/panel.ini /usr/local/psa/admin/conf/panel.ini.bak

   On Plesk for Windows, copy %plesk_dir%\admin\conf\panel.ini to panel.ini.bak in the same folder.

2. Add the following lines to panel.ini, see How to edit Plesk panel.ini:

   CONFIG_TEXT: [webProsAccount]
   enabled = 1
   enabledTypes = admin,adminAlias

3. Log in to Plesk, open Profile & Preferences, and link your WebPros Account in the WebPros Account section. A WebPros Account that was linked through the Social Login extension stays linked.

4. Open the Plesk login page.

   Note: The Log in with WebPros Account button is shown on the login page to all users, not only to administrators. Users without a linked WebPros Account cannot log in with it and keep using their password.

5. Click Log in with WebPros Account.

Additional administrators, resellers, customers, and additional users

1. Log in with your Plesk username and password.
2. If you do not remember the password, click Forgot your password? on the Plesk login page, or ask your administrator or hosting provider to reset it. See How to recover forgotten Plesk User Account Password?

Users who log in with a passkey

Passkey login is removed together with the extension and has no replacement in Plesk. Log in with your Plesk password. To add a second factor, use the Multi-Factor Authentication extension, see How to enable Two Factor Authentication (TFA) / multi-factor authentication (MFA) for Plesk login sessions.

Servers that stay on Plesk Obsidian 18.0.83 or earlier

The extension keeps working on these servers until they are upgraded. Logging in with Google, Facebook, or GitHub relies on Plesk services that are retired after the removal, so it can stop working on these servers as well. Set a Plesk password for every account now, whatever Plesk version the server runs.

Hosting providers

Expect questions from customers who used Google, Facebook, or GitHub login, and point them to this article. To reset passwords for many accounts at once, see How to bulk reset passwords in Plesk.

Additional information

• Plesk Obsidian Feature Deprecation Plan
• Plesk Obsidian change log
• How to log in to Plesk