Search results

Could you please elaborate on the issue? Restricting the root user should not affect your ability to log in with the admin user.

Thank you for the update. Could you please also try running plesk repair mail and confirm if that helped solving the issue?

@Alfonso Uritec , our team is still working on fixing the issue. In the meantime, the workaround they proposed is to: 1. Switch the branch from the target one (e.g. development) to any other (e.g. main) 2. Switch back to the target branch (e.g. development) 3. After that you should see the...

Apologies for the initial misunderstanding. There are quite a few issues ongoing on right now and I definitely overlooked the report. @Kaspar as far as I am aware we do not have a registered bug for this issue. Just to make sure I understand the issue and attempt to replicate it, and forward...

Hello, @lightingman2003 . Could you please report the issue directly to the plugin vendor: Contact Us It's determined the root cause for the issue is Plesk-related, they will be able to bring it to our attention for further review.

No, the sender address is still [email protected]. I PMed you.

There are currently two root issues present with dovecot. One of them is related to server ciphers and the workaround mentioned above is relevant to it. There is also a second issue related to pci_compliance being enabled, which also leads to failure to start the service. You can try running...

Thank you for the report, @Jose Antonio Gil Parada . Our team is already working on a hotfix (PPP-69670), which should be released soon. In the meantime, the workaround our team suggests is to substitute ssl_prefer_server_ciphers = yes with ssl_server_prefer_ciphers=server and ssl_protocols with...

Hello, @jumpstart . Both options are possible. You can either perform a migration from the old server to a new one. You can also perform an in-place upgrade with the elevate dist-upgrade script. In any case, it is strongly recommended to have a healthy full server backup.

Hi, Peter. We have the following article that addresses similar error: https://support.plesk.com/hc/en-us/articles/12387748164247-Plesk-backup-to-remote-FTP-finishes-with-warning-Unable-to-upload-the-backup-to-the-external-storage-Unable-to-resume-an-interrupted-upload I believe adding the...

@Tobias Sorensson , @DylanJ I would like to confirm that your feature requests are submitted and taken into account. I cannot yet provide any insights on the outcome, but the case is being internally discussed.

@LRob , the issue is supposed to be fixed in 18.0.72. Could you please confirm if the warnings do keep getting logged after the update? In the meantime, I will double-check with our team why there's no mention in the changelog. Thank you in advance.

Hello, @torrocks . Could you please confirm if you have purchased the license key directly from Plesk or through a Plesk partner?

Thank you all for reporting the issue. Our team is already working on a hotfix (PPP-69670), which should be released soon. In the meantime, the workaround our team suggests is to substitute ssl_prefer_server_ciphers = yes with ssl_server_prefer_ciphers=server and ssl_protocols with ssl_min_protocol.

A fix addressing the traffic calculation issue was released today. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.73:

Everyone, a fix addressing the truncation issue was released today. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.73:

A fix for the issue concerning the ioncube_loader installation was released today. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.73:

Hello, everyone. The Tech Domain DNS cluster was migrated, and the issue is completely mitigated. We also have a public status page now.

@pwouda , @cyberjam is right. pzstd is a compression process used by Plesk for backup-related tasks. There is likely a scheduled backup task that runs when you notice the spike, which is expected during backup creations/restorations.

I am not sure why the button would be missing, but could you please try installing the extension via the command line and let us know if that triggers any errors/warnings: plesk bin extension --install support-access