Recent content by MHC_1

Hello! Yes this has already been done (Locking that package). I wasn't sure if there was a workaround we could do but looks like maybe not. Thanks.

Can this be marked as "Resolved" with BitPalasters answer. Thanks.

We have got this exact issue; however the issue is caused by the update for: I do not know where the Perl-DBD-MySQL package comes from but running it causes the Plesk Update GUI to become unresponsive. On CLI the yum update has these two MySQL dependencies which can't install due to clashing...

@Bitpalast Ok Update again: Root user has been generated; and mysql_upgrade --force has been run. All tables show "OK" . Re running the SHOW FUNCTION STATUS WHERE Db = 'dbase_name'; in PhpMyAdmin returns a non-error result (blank but not the error it had before. This should fix the issue...

@Bitpalast update: We can not run mysql_upgrade because there is no root user. There is a mariadb.sys user and an admin user but we do not know these user's passwords.

@Bitpalast oooh, I don't think, mysql_upgrade --force was run. I will check the PhpMyAdmin routine and then give this (--force) a try. Thank you.

Ignore that last Q5 that's wrong.

OS: Alma Linux 9.7 MariaDB: 10.11.15 Plesk: 18.0.73 update 5 Plesk backup runs but creates an error for every DB: But the database and the tables all work ok and no other indicator anything is corrupted. This Q&A here: Resolved - Plesk backup can not Dump databases MariaDB 10.6.7 references...

Hi Thanks for working through this. Updates are that we have set the email accounts to "Hashed" in the Security Policy settings. We have migrated a new account across from the old server ( WHM ). This new account are still actively listed in the Command Line feedback above, as needing new/reset...

Jeeeebus Christ, you'd think that Plesk Devs would document this gapping hole in their SSH setup (like somewhere highlighted here: (Plesk for Linux) Enabling SSH Access for Website Users ) rather than having to trawl through support forum posts when this issue is discovered. TLDR: - To change...

"Symmetric encryption". I guess perhaps this should be changed to Hashed? ( I wasn't previously aware of this option) Thanks.

UPDATE: @yspirin One of the domains highlighted has only a single mailbox, re-entering the password for this mailbox via the Plesk UI and restarting Postfix / SMTP does not remove this domain from the list outlined in the documentation. Next steps?

Hello Thank you, yes re-entering the password for an account permits the end client to connect to the mailbox with encrypted rather than plaintext authentication.

@yspirin thanks; so the listing from the documentation is for ALL email addresses under each named account? Can you confirm that replacing the password in the field here (with the same plaintext password) will NOT effect the end user logging in to their emails?

@Sebahat.hadzhi further, it appears as far as we can tell to be an issue for emails imported via the Plesk Migrator. Email accounts created natively on the server seem to be ok. I have set both emails to the same subscriber (Administrator) and the issue remains (although didn't restart server or...