• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question Access? Maybe due to changes / updates in either Plesk Obsidian 18.0.44 and/or Ubuntu OS

learning_curve

Silver Pleskian
Server operating system version
Ubuntu 20.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.44 MU #3
We have IONOS Cloud servers, all are idenical main specs (forum signature), but hosting different domains & some have different 3rd party packages on them. We have usuable backups of all, taken prior to theses issues becoming known, so can recover using those, if needs be. Only one server is affected, but in two different ways.

1) SSH / SFTP access has been revoked, for domains that previoulsy used, it without any issues or problems, using /bin/bash (chrooted) selected within Plesk. The /etc/ssh/sshd_config file has NOT been changed / updated by either Ubuntu OS or Plesk, since we last modified it in January this year (after an OS update). So that's the primary area of focus verified, but leaves little other immediate point of reference? There's been no changes made (by us) within Plesk - Web hosting access etc to any of the effected domains, nor by the OS - AFAIK. It appears to be just an access rights issue, that may have taken place unseen, as per the thread title suggests i.e. Plesk Obsidian 18.0.44 upgrade and/or an Ubuntu OS upgrade.

2) MariaDB access has not been revoked, but access by users, to certain tables within MariaDB within some 3rd party packages is now limited / denied, compared to the previous access rights. We have made no changes that are releated to MariaDB within Plesk itself, other than the MariaDB 10.5.15 > 10.5.16 upgrade that was relased in late May. The 3rd party packages do fully suport this upgrade, so again, plus there are no errors / faults found, when using either each of the separate domain's check and repair functionality within PLesk or indeed, when using the Plesk repair-kit Extention to check everything, including MySQL aka MariaDB. So it appears to somehow also be, another access rights issue, somewhere... possibly relating back to the thread title again?

Currently, it's just lots of misdirection, so it's proving hard to spot where the glitches are located.

Please fire away with suggestions / checks that we may have not yet run / completed ourseleves yet & we'll run those by return instead!
 
Hmmmm. So
1) is fixed. Seems most likley to have part of a previous Plesk upgrade glitch, as we traced it back to corrupted chroot libraries files. It's obviously not a rare event, as Plesk do have several, online library items / help pages which can & do assist. The one below, being the simple, quick resolution of the 1st fault:
2) We haven't traced this yet, but we're on it - including - seeing if there's some form of a link (by pure chance...) back to 1) above.
 
Back
Top