Search results

@CMRP The update should not override the file /etc/dovecot/conf.d/99-local-pop3.conf, thus, your customization should remain intact. However, if I am not mistaken, your custom config will be enforced over Plesk's config, and I cannot confirm for sure whether that won't create issues in the future.

Hi, @LRLD . I double-checked with our team and DIGEST-MD5 and CRAM-MD5 were intentionally removed, because they are considered weak in Dovecot 2.4 and cause issues with encrypted passwords and some email clients (e.g. Android-based - try to authenticate with DIGEST-MD5, fails, and results in...

@spip the prompt in question requires the login credentials of the main "admin" user. For reference: Unable to log into the Plesk Repair Toolkit with the root credentials

Hello, @Kouenteen . Could you please confirm the SSH access on a subscription level in Subscriptions > example.com > Websites & Domains > Hosting & DNS > Hosting > SSH access? If it's set to "Forbidden", please change it to one of the other options (recommended /bin/bash (chrooted)).

@pleskuser67553 , could you please run the following command to check the Nginx and Apache syntax: apachectl -t nginx -t It's likely for the issue to be automatically solved by Plesk installer.

@SCRINF , Plesk Obsidian 18.0.73 Update 1 should address the email re-downloading issue. Do I correctly understand that the same is still ongoing on your end after the update? If yes, could you please confirm the OS of your server?

The issue should be resolved after the update released yesterday - Plesk Obsidian 18.0.73 Update 1:

Hello, @KAEL . You should be able to define it in /etc/dovecot/dovecot.conf: auth_allow_weak_schemes = no then restart the service service dovecot restart However, please note that, I cannot confirm if that won't lead to any authentication/login issues.

Hello, @max2334 . Could you please check for potential stuck backup tasks: ps auxfw | grep backupmng | grep -v grep ps auxfw | grep pmm | grep -v grep

Hello, @spip . My guess is that you are trying to access the Repair Kit extension with a reseller user rather than an admin user. The Repair Kit extension is available only for administrators at this point.

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 plesk-talk@plesk.com. 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...