Search results

Because instead of having two email templates, the little person who lives in your Linux box just types out one! But yes, in an ideal world, the first portion would be suppressed if there are no new ones and same for renewals if there are no new referrals.

Assuming that's it not all email originated from your server(s), the message content and structure may also play a part in that determination.

Another "here as well" to add to this thread - So apparently even "large" number updates are indeed automatic but with somewhat erratic dates/times that they apply (an update from 18.0.28 #3 to 18.0.29 #2 that kicked off during business hours on its own). All I can say is...... IT'S...

I would recommend avoiding the upgrade/restore circle as that isn't likely going to address the issues that you're using. The first action item might be to engage either Plesk support or your Plesk reseller to get this addressed and if it's especially critical, Plesk support might be the way to go.

If that's the case, there are a couple of things that you can do depending on your level of technical aptitude. More often than not this isn't a Plesk issue and if turns out to be, your provider can address it for you or let you know what's needed to send mail in their environment (in some cases...

In some ways it wouldn't be terribly challenging since they already do it for the database service that ships with Plesk so they could offer a "Use vendor database" option just like we see with PHP handlers as a default alongside a "Use MariaDB shipped with Plesk" option. Now THAT would be...

Are you a hosting provider or are you an end user working on a site that happens to be using the Plesk control panel? Depending on your answer, that will determine the next step to check!

If you haven't already restored your server from a backup and you engage Plesk Support, please post back with your results!

Peter's idea is a good one - If you have Fail2Ban enabled, your server might be banning your own IP address so be sure to add your server's IP address to the Fail2Ban exceptions.

The official Plesk one or are you using one of the third party mirrors? The third party ones (looking at you OVH) seem cause more problems than they're worth.

No doubt, it would be slick to have Plesk take care of the database install and updates as part of its package just as it maintains its own PHP packages but I would mark it down as a not likely to happen scenario since Plesk isn't likely going to get into the business of maintaining site-facing...

I've always thought that Plesk should offer a third checkbox when issuing SSL certificates to the effect of "Secure sub-domains with www" when a sub-domain is included given that sub-domains aren't often added with an extra www DNS record and currently the case you identified would cause the...

What was originally included above was a minor update, not an update to 10.4.x so if you're concerned, you could block updates from MariaDB. I assume that Plesk doesn't want to take on the management of its own set of databases which has both benefits and downsides (you'll have posters...

I haven't seen automatic updates for major version upgrades yet so I suspect that it must have been initiated for you if you didn't kick it off unless Plesk has an undocumented forced major version upgrade system in place (in lieu of the old "late adopter" feature that is dearly missed). EDIT...

Same result following a successful upgrade to 18.0.29 #1.

Peter, thank you for sharing that as it confirms our conclusion as well! We were seeing the same behavior (micro-updates installed automatically but "number jumps" from 28 to 29 are manual) but as the new semi-major versioning system is still relatively new, there isn't much official...

The 18.0.29 update is still reported by Plesk but without manually initiating it, when will it kick off automatically?

Here are the results with Plesk 18.0.28 v3 still reporting a Postfix component update: # plesk installer --select-release-current --reinstall-patch --upgrade-installed-component WARNING: Ignored deprecated parameter in Plesk Installer's configuration file: 'SOURCE_TYPE' = 'plesk' WARNING...

This may not be a Plesk issue so to start, you could check your sending IP against a blacklist tool such as MX Lookup Tool - Check your DNS MX Records online - MxToolbox and then extend it to an SPF check with the sending IP to validate it.

On CentOS Linux 7.8.2003 (Core) running Plesk Obsidian Version 18.0.28 Update #3, we've been seeing the following: We dutifully hit Continue and while the process completes as follows, Plesk continues to show "Component updates are available" - Installation started in background Loaded...