Recent content by Kaspar@Plesk

The most common cause is a (almost) full disk or a mailbox which has reached their quota. I suppose in theory it could be caused by insufficient inodes. But in that case you would have a whole range of other issues too. None the less, you can check your inodes usage with df -ih. Do you have...

Is Proxy Mode disabled for the domain? If so, when you create a new PHP (for example mytest.php) and add the following code to <pre> <?php print_r($_SERVER); ?> Does it output the HTTP_HOST variable?

I see. I can't find anything related in our internal documentation. I suggest contact Plesk support, either by chat or ticket.

This is an community forum, available for users to discus Plesk and related technologies (but I you want to discus beer recipes that's okay too). Like you've done in this thread. The forum is not an official support channel. As far as I can tell this issue not caused by any configuration by...

Seems to be a know issue with Nginx and PHP. As a workaround you can try setting the host manual (instead of using a variable) in the Additional nginx directives of the domain. fastcgi_param HTTP_HOST example.com;

Why not?

What's the exact error your getting when you try to install the upgrade?

No, this has to be resolved by your license partner.

DMARC validation has failed because of an DKIM issue. The DMARC policy is set to QUARANTINE, which means that any email that fails DMARC validation will be delivered to the spam folder. The recommend suggestion to solve this issue can be found here...

It means that another IP's is likely already assigned to the license. Contact your license partner (in your case Hetzner) about the issue. They can re-assign IP's for the license.

The /etc/apache2/conf-available/javascript-common.conf file is part of the Javascript Common package. However, even if it has recently been installed the file will still show 2020 as the last modified date, as that's the date from the repository. The Javascript Common package isn't part of the...

Thank you for letting us know. I've tried to replicate this on a Alma8 with Plesk .61 to Alma8 with Plesk .61 server, but all attempts with successful and any mail folder with an ampersand in their name where successfully transferred. There could still very well be a bug that causes issues...

Just to be sure if I understand your objective correctly, you do mean that any visitor/user who try to access Plesk on the URL of your previous server gets redirected to the URL of Plesk on your new server? If that's the case, and you've used a (sub) domain you own as the servers hostname, you...

No, but if there are any configuration issues it might end up in the spam folder. Have a look at the email headers to see if there any information in there as to why the email ended up in the spam folder. Things to look out for are spam score and dmarc failures.