Search results

Try using "127.0.0.1" instead of "localhost" had way to much trouble with MariaDB > 10.6 on Debian/Ubuntu lately when using "localhost" (something to do with socket based connections and the "%" wildcard for access restrictions in mariadb no longer covers "localhost")

I do not think that the Plesk Migrator extension does migrate DKIM keys... So all your domains on the new server will have a different key for the email signature than before. For domains with local DNS you can most likely just uncheck and then enable the DKIM checkbox again, in order to fix the...

To answer my own question, in the end it is quite simple. Adjusting the ext-plesk-sitejet-website_template_id value in the dom_param table of the psa database for the new site

For that you may need to convert .htaccess (rewrite) rules to nginx and add it to the nginx config in Plesk.

I assume this function to move/migrate a website is not yet published in the Sitejet extension? As least I don't see anything like that release notes.

most likely a postqueue -f would have helped to deliver them immediately once messages are stuck in the queue for a certain time, new delivery attempts for them only happen once every 1, 2, 4 hours or so. So it's normal that it may have taken quite some time to get these 150 mails out.

Already updated all our servers on the 3rd of April (as it finally fixed a Backup Telemetry extension problem for us) and so far no problems with it.

We do still like the builtin Backup solution, as it allows our customers to see that there are in fact really backups made and available and also sometimes they use it to restore some stuff on their own. (but often it's like Hangover2 already wrote and we have to recover specific stuff for them)...

If the nameserver of this domain are with Kinsta, you're best of buying a certificate (valid for "webmail.CUSTOMERDOMAIN.TLD" as that should also automatically include CUSTOMERDOMAIN.TLD) for a couple bucks and manually renew it every year... For the domain validation you can then select an...

That is a myth, at least with Gmail. Gmail does reject emails from hosts that do not explicitly match the SPF record OR do not have a valid DKIM record. (so, if the email a properly DKIM signed, Gmail in general will accept the email, even if it comes from a host outside the SPF scope)

You can ignore UCEPROTECTL(x) as GMail does consult this rubbish blacklist. (nobody really does) It's also not a problem with missing/wrong SPF record or DKIM, as this would show in the error message you get from Gmail. So, your email(s) just look like spam to Google, maybe there is an URL...

https://support.plesk.com/hc/en-us/articles/12377243101591-MariaDB-fails-to-start-Aria-engine-is-not-enabled-or-did-not-start

If you add something to be bottom of the nginxDomainVirtualHost.php, it will get added after the server{} block for https/ssl vhosts and inside the server{} block for the port 80 vhosts. Do not ask my why, but the whole templating stuff of Plesk is quite complex and sometimes beyond my...

Debian 12

Thank you! (and Google to let me find this post) almost gone nuts, asking myself why event handlers did not work... So, Plesk team, please please please fix your documentation!!!!!! (Event Handlers)

Yes, if you wan't to customize the path of the PHP-FPM unix socket file, then you may be out of luck. (seems to be hardcoded somewhere) But as you want to use the very same socket config/file for all sites, it would also not make sense to let every domain create this file. (will most likely...

You can do that in the file /opt/psa/admin/conf/templates/custom/service/php_over_fpm.php (copy over from /opt/psa/admin/conf/templates/default/service/php_over_fpm.php)

/usr/local/psa/admin/conf/templates/custom/domain/nginxDomainVirtualHost.php is the correct file to add such an include, you just need to place it at the proper position. We use the very same mechanics to include a custom file that blocks "bad" bots and access to some files and directories...

To make a PFP-FPM pool listen to a TCP port/socket, instead of a unix socket, you can simply change the "listen" parameter in the /opt/plesk/php/[phpver]/etc/php-fpm.d/[domainname].conf file from "php-fpm.sock" to "9000" To not mess with Plesk internals (and risk the custom config being...

There will be no guide, as surely nobody ever attempted such a flawed thing, like ever... First, if would require lots of manual fiddling in config files and Plesk templates Second, ALL these domains would need to run on the very same subscription (or else the file system and process...