Search results

In many (not all) instances, it can be due to high I/O loads that have a detrimental effect on services. What is the result of a # top command?

More importantly, why downgrade?

Yes!

It would make sense to add this feature to the GUI (to restart the website server database, not the Plesk database itself), just as the Apache service can be restarted via the Plesk GUI. While it's not clear that there would be a lot of use for this, it's not a terribly difficult enhancement to...

Check out this handy reference out and while never having tried this personally, there's also a Plesk Extension that is willing to take your monthly coffee money in exchange for access to the same information in a more GUI-oriented format that you can access directly via the Plesk panel.

Just to ensure that you don't have this value set in a script, have you tried running an execution time loop outside of WordPress to ensure that it is environmental?

I believe that it will change sooner than later per Igor's note that about the bug fix PPPM-12236. It just takes time for the Plesk Devs to wind down the clock ;)

Is mail activated for the domain? To clarify, you have multiple domains with multiple email accounts that can send without a problem however on just one single domain you have multiple accounts that cannot send email, correct? Can you check to ensure that the sendmail utility is enabled for...

You can start by first checking the headers of the spoofed email to see if the original sending IP is actually your server. If you confirm that it's not, then consider using SPF to help combat message spoofing.

Great to hear - Plesk is finicky about permissions so customizing ownership can give it a bad cold.

The best problems are the ones that solve themselves! Care to elaborate on your solution?

As you seem to be handy with SSH, have you run the command? plesk repair fs Without any additional flags that should recurse through both your vhosts and system files. Link to all options for Plesk Repair Utility: File System

Why yes sir! There's a handy dandy article on this very topic complete with well-snipped screenshots here.

This came up not too long ago - Have you checked out this thread to see if there is a nugget that might help?

Correct, as @Peter Debik pointed out the first part is strictly for the initial issuance of the SSL certificate. Ideally it really should be in two different messages or the empty part should be suppressed but that might be splitting hairs at the moment.

Additionally, DigitalOcean may require a request or change on their to open 25 at a level higher than your installation. Other cloud providers have been known to imposed that limitation out of the box to help combat spam originating from their IPs.

A little "unresolve" status magic would be nice on this post - Has anyone running 18.0.28 reported this as a bug?

No doubt making some t-shirts or bumper stickers with that very quote can be tempting as is the case with any complex ecosystem. As previously suggested, have you started by making this change? content_filter = amavis:[127.0.0.1]:10024 to content_filter = smtp-amavis:[127.0.0.1]:10024

For any interested (or just plain bored readers) of this post, the issue, albeit a bit difficult to tell from the lack of a more meaningful error, stemmed from the same circumstances detailed here so by disabling priority protections, running the update, and then re-enabling it as documented in...

If you're using the WordPress tool for each location, try scanning for them again. You should likely see a "broken" instance for the source one that you can remove if you're not using it or its files/database and the new one should pick up its new "home" regardless of directory change.