Search results

Thank you for the update. Could you please try:

Hello, @simonedev . Have you tried the Plesk repair utility already? If not, could you please try running the following command: In case the issue persists afterward, could you please provide us with the contents of /var/www/vhosts/system/example.com/conf/vhost.conf for an example domain name...

For the sake of testing, could you please set the value to back to the default one. That should be:

@Jens Johansson , the behavior was confirmed as a bug identified with ID PPPM-15001. At this point, I cannot provide an ETA on when the fix will be introduced. You can monitor the change log here. Thank you for bringing our attention to the issue.

Thank you for the report, @hschramm . I consulted with our team and they confirmed this is an expected behavior. mirrorctl only creates a mirror with Plesk-related packages, thus, anything related to Applications and Extensions is not included in the Plesk Autoinstall Servers mirror.

Hello, @alonzofer041 . Please try adding the missing keys following the instructions here. For Grafana, please try fetching and installing the key by running the following command: wget -q -O - http://autoinstall.plesk.com/plesk.gpg | gpg --dearmor > /etc/apt/keyrings/plesk-ext-grafana.gpg...

@MHC_1 , Deferred, bounced, and failed messages are all logged into /var/log/maillog. Plesk does not maintain a separate dedicated log for failed emails.

Thanks for the confirmation. Was that change performed before or after the occurrence of the issue? As far as I am aware, that particular issue could result from such changes.

Thank you for the report, @Jens Johansson . Frankly, I am not entirely sure if the system value should be set by default during database creations, but it does make sense to be. I will confirm with our team if that would be considered as a product bug and follow up with more details.

I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in and open a ticket please go to: https://support.plesk.com If you got your license from a reseller, your reseller is in charge of providing you with support. You can raise the...

Hello, @JuanCar . Is the repair utility unable to fix the reported "file not found" error? Can you please try running and let us know if the issue persists after that: Is there a wildcard subdomain added for domain.com by any chance? If it is, that could be a result of to a product bug...

Hello, @gabriel.mstowski . Could you please provide a little bit more context to the issue you are experiencing with the modsecurity jail?

Thank you for your feedback. Our team now published an article on the matter: https://support.plesk.com/hc/en-us/articles/26972108383511-Unable-to-save-a-new-key-in-SSH-Keys-Manager-Incorrect-format-of-SSH-public-key

Thank you for the update. Could you please double-check the test_db.php file (or whichever the database config is for your application) and confirm if the database user is correctly defined. It should be the one you see assigned for the database when you navigate to Domains > example.co.uk >...

Can you recall of making any recent changes on master.cf, main.cf, or any mail settings/configuration whatsoever?

Hello, @D4NY . Yes, the patch should be automatically applied on Plesk Obsidian 18.0.69.

This will most likely require a review by our engineers, I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket, please go to: https://support.plesk.com If you got your license from a reseller, your...

Disabling rules could potentially negatively impact your website's security, yes. Still, it depends on which rules in particular you are disabling. If the rules are continually being triggered due to false-positives and cause issues the widely used workaround is to disable them. Because...

@MHC_1 the key is expected to have three, space-separated, non-whitespace parts (type, key, title):

Hello, @CMAdamadman . Would you mind confirming what's the exact error you are encountering upon reloading the website?