• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Password changed

T

tek01

Guest
Hi there,

We just upgraded from SB 2.1.3 to SB 3.0.2 on Linux. We also migrated all websites from the old SB but noticed that all users now have different password.

Yes, we can manually change all the password but since there are more than 200 users i would like to know if there any way we can do it automatically.

I think this is a common issue for everyone migrating from old version...

Thank you!
 
Yes, you are right. During migration, passwords of resellers are changed. Also, passwords for site owners created in the process of preparatory migration are generated. See information on users' passwords in the <sitebuilder-root>tmp/migration/migration-passwords.log file. In the migration-passwords.log file, information is stored in a table with vertical lines used as separators. The table has the following format:

| User name | Password | E-mail | User role |

Password for appropriate user in Sitebuilder database can be updated with following command:

mysql> update user set user_password=md5('NEW_PASSWORD') where user_name='USER_NAME';

So you can get the list of user names from migration files or directly from database, compose list of password for users and right a little script which will update password for each user.

Hope this information will be helpful.
 
Back
Top