Search results

Noticed this occurring recently since we bumped up the SPF_FAIL score. What's odd to me is that the mail server still records the Received-SPF header as a pass, yet Spamassassin apparently ignores this for its scoring. This is odd because `ignore_received_spf_header` is 0 and...

@Peter Debik Will do, thanks :)

@Peter Debik curious if anyone at Plesk knows what the circumstances are that lead to needing this dbus timeout adjustment. As in, do you know what environment that is expected to apply to? I'd definitely be curious to learn if the KB article was created from a report on another OpenVZ...

Indeed - it certainly was the last time. It appears to be connected to cgroups sessions clashing with the default dbus timeout. Yet it only occurs on busier servers. I think it's going like this: 1. There must be many processes generating short-running cgroups sessions (perhaps php-fpm ondemand...

This issue was fixed with a Virtuozzo update, as indicated above. We were able to remove our workarounds for all CentOS 7 boxes. Now a very similar issue has occurred with AlmaLinux 9 where there are thousands of abandoned sessions to the point they reach the session limit of 8192. The very...

We've run into this issue as well. What I don't understand then is why Plesk allows setting the symbolic link as the document root to begin with if it's just going to cause failure during migrations. Seems to me that either: 1. Plesk should block using symbolic links as the document root, OR 2...

We've written a guide and PHP script to show how to export the data, then automatically update the exported data with the new domain and client IDs, then import the data into the new server. It can be found here: GitHub - websavers/Plesk-Migrate-Backup-Settings: Run this on old and new server to...

Hey @Peter Debik This was already requested here: Increase migration speed And marked Completed in 2016 at which point the admin said "Please let us know on Plesk Forum if still have problems with migration speed." Which is what we did here... Nonetheless it has been added here: Improve...

The Plesk migrator still behaves exactly this way, which means it's very slow to resync.

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