Search results

Plesk is pretty generous about the additional PHP handler that you can install and goes back to PHP 5.3; have you tried installing it first via the Plesk add components feature so that you can make it available to a plan, subscription, or website?

If your data center environment allows for IP re-assignment and you'd prefer to take a slightly "safer" route, you can migrate to a new server (using its new IP), test a site on the new server by pointing to the "new IP", and then swap the IPs so that there isn't a DNS implication for website...

This sounds very similar to a KB that was updated a couple of months ago: Mail delivery does not work: do not list domain in BOTH mydestination and virtual_mailbox_domains Luckily the fix is pretty quick so please post back with your results!

To help others who might find themselves in the same situation, it would be helpful to provide the resolution!

If I recall correctly there was a thread similar to this a few years back as well but it's somewhat old so it may not be relevant to your setup.

This behavior may be attributed to a daily operated system union-mandated break ;) The 403 errors are likely false positives. Do you have any backup processes scheduled for that time? Another other possibility here might be with log rotation - have you checked the server-level error logs to...

Or if you're impatient: Log into Plesk as admin. Go to Tools & Settings > Services Management. Click Restart the service icon next to Web Server (Apache) Then refresh your browser to see if your document root update is properly updated.

That implies that @Pleskie will have to migrate by CentOS 8 EOL whereas @Pleskie might buy more time to see how the OS battle shakes out with either CentOS 7 or Ubuntu.

If you absolutely had to make a decision in the very short term, you might want to stick for CentOS 7 for the moment since it effectively has a longer runway than CentOS 8 (this puts you into the Rocky Linux path). CentOS 8 would force your hand within a year so CentOS 7 (or if you really had...

Did you post on the thread at Reports

Very apropos, especially for such an abstract issue!

It's a bit speculative but a migration approach is safer in that you have the concept of a process restart while backing up, destroying the original source, and restoring means that everything is pinned on that one backup's integrity without much recourse should the restoration process fail.

It would be a nice Christmas present to see the split major/minor and early/general/late adopter tracks brought back! The upgrade roulette really adds to the excitement of Plesk but at scale, especially given the randomness of major upgrade execution, it's quite a headache. Don't fall for the...

If you're looking for confirmation, this might be a better place to post your report.

Unfortunately the two biggest players are both owned by the same parent entity (WebPros) but as Peter Debik astutely pointed out, there isn't enough information as of yet to commit to any one direction. On a personal note, it would be interesting to see Rocky Linux evolve into a MariaDB-esq...

Without more information from the OP, this doesn't appear to be a Plesk-related issue but could be either a low memory problem causing process to use SWAP or an unmitigated process.

Do you have a firewall or appliance sitting in front of your server? You might consider blocking traffic to your SSH port and only allowing your IP address which would effectively kill all of those SSH requests. Alternatively you could also change your SSH port to a non-reserved port however...

Check to see if the subscription is locked which would prevent syncing (syncing would still be successful for other plans).

This sounds more like a general question about using built-in DNS management with control panels - As it pertains to Plesk, Plesk DNS offers relatively tight integration with the Plesk ecosystem for business models that use it (for basic hosting environments it's a quick and no-cost way to...

It is indeed a very credible answer and the "Plesk Guru" badge tells you that it's not Peter's first week of working with the Plesk ecosystem.