Search results

Yes, exactly, other than deactivating automatic updates, it's no longer possible. Bugs like this are rare, but something like this happens every now and then and it's just very annoying for many hosting customers. If nothing changes in this regard in the future, more and more larger hosting...

In my case it was a jail that had the instructions at the beginning_ [INCLUDES] # Read common prefixes. If any customizations available — read them from # common.local before = common.conf If I remove this from the jail before the update, the update works normally.

Same problem ...

A new comment has now been added on Conversion inside containers (Virtuozzo) · Issue #87 · plesk/centos2alma -------- commented Jan 5, 2024 Virtuozzo have a special script to convert CentOS 7 containers now. Unfortunately, it does not support Plesk. I believe we will be able to discuss it with...

Do you have any news about this? was there a reaction?

That's a nogo to simply activate an extension like a site builder. Imagine a web designer hosting his customers on a Plesk server and suddenly the customers have a web builder at their disposal. A web host with thousands of customers suddenly has to worry about broken websites and support...

the server didn't have any exceptions No, unfortunately there are no clues in the log I restarted all services once and performed plesk repair for web, mail and installation. Since then it has looked ok. I have to keep watching.

Hi, Last night the maillog was suddenly full of messages like PleskFilter: Unable to set close-on-exec on connfd (Bad file descriptor) what does this message mean? I've searched but can't find anything related to Plesk.

this has already been reported. but there is no update yet ------------ Leonid xxxxx (Plesk) Jul 11, 2023, 07:26 CDT Hello, Thank you for contacting Plesk Technical Support. Such behaviour is registered as Joomla! Toolkit bug with ID EXTPLESK-4677. Currently, no workaround is available...

actually everything has been said. I had written that I know that option 2 is chosen to prevent emails from being delivered locally. option 3 only to remove all mailboxes. It takes a little getting used to that this has now been changed and in my opinion it was solved better in the past, but...

it's not about a possible bug. I know that "with "Disabled for incoming mail", Plesk tries to delivery email to an external server." functions. it's just that it was "before" possible to disable the email service "without" deleting the mailboxes. it would be much better if you could deactivate...

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...