Search results

no of course not Yes, exactly, and that's no longer the case with the newer Plesk versions. this was the case in previous versions. but now the service can only be deactivated if you confirm that all mailboxes are also deleted, see picture the email service can only be deactivated if the...

at least with plesk without the dns extension this is the case. if plesk has activated the mail service for the domain, the emails are delivered locally. For domains that have an external mx, the email servoce must be deactivated, which is also not a problem apart from the fact that plesk then...

No, this is not a bug or a misconfiguration. If the customer has 5 domains but one of them has been switched to MS then this is normal. As long as the mail service is activated in Plesk, Plesk does not care which MX is set (Plesk has no DNS), but delivers the emails locally. Plesk only looks for...

When a customer migrates their domain to MS, they also need to migrate the content of their mailbox to MS. Customers often want to keep the mailboxes in Plesk for a while before they are finally deleted. But that only works if the email service is activated. If the customer has several domains...

In the past, you could simply deactivate the email service of a domain (e.g. after switching to office365) but the mailboxes were not removed. Now you can only deactivate the email service if you confirm that all mailboxes will also be deleted. Is it not possible to avoid removing the mailboxes?

I can only agree. Of course, it's really not a problem if you only have a few webs on one server, but if you have a large number of servers with many customers, the only option left is to completely disable automatic Plesk updates in the future. who would like to get unnecessary support just...

a workaround # rpm -ivh --nodeps php-process-5.4.16-48.el7.x86_64.rpm then upgrade works. only one Warning -- Warning: RPMDB altered outside of yum. ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: php-process-5.4.16-48.el7.x86_64 has missing requires of php-common(x86-64)...

@sebgonzes that's not the solution. It is surprising that another server that has php5.6 as OS-PHP upgraded without any problems. i haven't figured out why yet. If you remove the OS-PHP via the plesk installer and reinstall it (php5.4), the upgrade also works.

few years ago the OS PHP version was upgraded from php5.4 to php5.6. the remi repro has also been deactivated since then. you mean I should remove the OS-PHP completely? Plesk PHP versions 5.4 and 5.6 are still required on the server. I don't understand why there is suddenly a problem. over...

>requires php-common(x86-64) = 5.4.16-48.el7 this is already installed #yum install php-common #Package matching php-common-5.4.16-48.el7.x86_64 already installed. but #yum install php-process #Error: Package: php-process-5.4.16-48.el7.x86_64 (base) #Requires: php-common(x86-64) =...

Plesk 18.0.47 #5 CentOS 7.9 when updating from 18.0.47 Update #5 to 18.0.48 i get the following error Exception: Failed to solve dependencies: php-process-5.4.16-48.el7.x86_64 requires php-common(x86-64) = 5.4.16-48.el7 Does anyone know where exactly the problem is and how I can solve it?

that didn't work yesterday. This morning it suddenly works again without an update. at least I can't find any reference to an update.

Many Thanks should there be a workaround before the patch, please let me know

logged in as admin it works normally. you have to be logged into plesk as a reseller and then open the toolkit excerpt from the log 23: /usr/local/psa/admin/htdocs/modules/joomla-toolkit/index.php:4 [2022-09-07 07:56:12.741] 22000:63183279949ae ERR [panel] Call to a member function...

Username: TITLE Plesk 18.0.46 Update #1 - Joomla! Toolkit no access PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 7.9 Obsidian 18.0.46 Update #1 Joomla! Toolkit 2.5.1-328 PROBLEM DESCRIPTION As a reseller you no longer have access to the Joomla Toolkit. The error...

on some servers the "allowhardlink" line was added to /usr/local/psa/etc/logrotate.conf.rpmnew !! but not to logrotate.conf

I can confirm. that was already the case 2 years ago when the certificate was changed. Now that the certificates are only valid for 1 year, this problem comes up every year. a certificate is often displayed as used even though ssl is deactivated for the user. but since the certificate was...

Try this https://support.plesk.com/hc/en-us/articles/213917525-Unable-to-open-the-Updates-and-Upgrades-page-or-start-Plesk-Installer-in-CLI-Update-operation-was-locked-by-another-update-process

please read the thread above. it was all discussed there

only a few minutes. we switched about 30 servers within 2-3 hours https://talk.plesk.com/threads/conversion-of-centos-8-server-with-plesk-to-almalinux.361493/#post-902348