Search results

We’re seeing a *lot* more CNAME to TXT records because of DKIM rollout for Google services. This means more people than ever are being confused by this warning. Would be nice to see this addressed.

Any tips as to where we might find the configurations for cloud backups? I'd like to see if we can find a way to manually move those over.

It did work! CentOS 7 -> AlmaLinux 8 was smooth. I then took it to AlmaLinux 9, and there were odd charset issues showing in initram initialization and it needed a manual reboot after it finished there, but OS seems to work OK other than it refusing to accept root logins despite PermitRootLogin...

Indeed! Wish we could use it, but we run Plesk inside OpenVZ containers and they're not supported by this. We also converted a couple barebones CentOS 7 KVM VPS to AlmaLinux 8 using ELevate and there was fairly significant downtime for a server that was stock CentOS 7 + OpenVPN only. I imagine...

3 years later and we've reached the CentOS 7 EOL (when last it was CentOS 6) and we still have to tell customers to reconfigure their backups after a migration :(

It would be nice if Plesk and Virtuozzo devs could have a quick chat about how to basically merge the Plesk-specific code into the almaconvert8 script. I believe this would be the best way to do it as almaconvert8 is already designed to work for CentOS 7 => AlmaLinux 8 on containers. It *should*...

Nope. It's here, if you're curious.

We have, and it is not. This is the result: # almaconvert8 convert $CTID CTID: Conversion aborted: Software unsupported by AlmaLinux 8 detected: Plesk Please contact the software vendor and request AlmaLinux 8 support But of course Plesk is compatible, despite that message. I've asked, in the...

See a solution / workaround for this here: Change Log for Plesk Obsidian It states: The gist is that if there's some kind of failure with general renewal (such as a firewall block preventing access to one of the many Let's Encrypt servers as described above), Plesk would try excluding the www...

Note this applies only to web users. They appear under FTP Accounts, but are not deleteable from there. If you click on the user then try to delete it from the Plesk GUI while you're using PHP-FPM, it will say: Unable to execute usermng: usermng: /usr/sbin/userdel execution failed: userdel...

It is still possible under normal conditions for this to happen in a manner that isn't related to that bug. Here's the scenario that seems to be most common: A site takes on hundreds of requests that are passed through apache to PHP-FPM (like uncached WordPress page requests) Each of those...

And as far as I can tell the patch was not backported to 2.4.6 on CentOS 7, so the issue will remain on CentOS 7 boxes. Setting MaxConnectionsPerChild to 0 as described here, helps to delay the issue as graceful restarts trigger less process kill signalling + forking. On a busy server...

To reproduce: 1. Add a domain 2. Add an alias for that domain, but do not enable DNS aliasing 3. Go to the alias's DNS settings and click Transfer DNS 4. You'll see the wrong domain listed if a site exists with the same ID as the alias ID. It appears to use site_id in the URL to identify the ID...

Also looking forward to CentOS 7 -> AlmaLinux 8 in-place upgrade support, after all Elevate already supports it without Plesk being in the mix. @IgorG: above @dash indicated that work would be in progress on this feature this year, but you've indicated that we should all just wait until EOL of...

We submit it as a feature request in 2016. Can vote on it here: Don't send Auto-Reply when message detected as spam

This fixes it by switching PHP 7.4 -> 8.1 repo data over to using RedHat-el8 rather than CentOS-8. The binaries should be identical. sed -i.bak "s#_17/dist-rpm-CentOS-8#_17/dist-rpm-RedHat-el8#g" /etc/yum.repos.d/plesk.repo And if you need to revert it you can either copy the backup file back...

Same here. @IgorG ?

We've been using Imunify360's ruleset, which is updated super-fast with protections for the latest web app vulnerabilities. Plus it's got a feature that disables rules for web apps that don't match what's installed on the domain to keep memory usage lightweight (runs nightly to determine which...

Weird, since the mod_security binary now installed from the Plesk repo is 2.9.5. Maybe the issue all along was twofold: the bug formerly identified a few years ago AND an actual issue with the way the comodo ruleset keys or accesses those entries. Like Peter, we also switched rulesets a couple...

Backup your databases with mysqldump, remove the MariaDB packages, then install the MySQL packages, run mysql_upgrade. Be sure to only use an equivalent version of MySQL to your installed version of MariaDB. Why do you require MySQL? MariaDB is fairly equivalent...