Search results

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.

While there are individual parts of many commercial operating systems and platforms that are covered by open source licenses (many Linux distributions), Obsidian is indeed a proprietary product. Mr. Plesk isn't in the business of freebies ;)

This isn't an issue that is related to your domain registrar so they were right to push back. Your subdomain resolves to your Plesk server so the packets are being dropped or rejected somewhere when trying to reach it. Try reaching out to your server provider for assistance as they might be...

It would be helpful to update the release notes to reflect MU 2 as well.

Just after that behavior occurs, is anything meaningful written to the /var/log/sw-cp-server/sw-engine.log file?

Anecdotally I feel that it could be age - I get the feeling some days that the sw-engine on one of our servers has more creaks and takes longer to get up in the morning than it should despite all other services moving within expected operating parameters ;)

Your screenshot shows that you're already running phpMyAdmin 5.0.2 - What's the issue?

Yes, you can disable the mail server (the mail server itself represents customer POP3/IMAP mailboxes while the mail transport agent works separately). The only caveat to mention is that we've seen behavior where even though the mail service itself was turned off via the Plesk GUI (at an admin...

While disabling symlinks and some other tweaks can help, given the gravity and priority of your issue, this really is better suited for Plesk support to look into.

When you have high I/O activity in the disk subsystem, even small to medium tasks such as the Plesk SW engine will pop; Plesk itself isn't particularly a high load ecosystem so it might be worth looking at other services that may be affecting the I/O numbers.

I'm not a particularly big fan of the new update system; if I were the friendly folks at Plesk, I would advocate making the following changes, none of which are particularly development-intensive: Set the update schedule via the GUI (it can still write to the INI file) Consider enabling...

Good thing this came up before going through the process of migrating, otherwise you would find yourself needing to migrate again in the near future!