Search results

Hello, @WhiteTiger . I am not quite sure I was able to understand. Is the DNS of the domain name in question managed locally or the zone is external?

Hello, Maria. Could you please navigate to Domains > example.com > Mail Settings and confirm what's selected for "Mail service on this domain" and "Webmail"?

Thank you for the update. Can you please try running the update through the plesk installer add --componentscommand line and let us know what the result is? It is likely, yes. Please try installing them through the command line. Roundcube: Sogo:

Thank you for the update, @majidalizadeh.yb . The issue might be caused due to SmarterMail being unable to generate a DKIM key with 2048 bit length. Please try adding the following line to panel.ini at C:\Program Files (x86)\Plesk\admin\conf\: If the issue still persists, I would suggest...

@schmitzfabio , apologies for the delayed response. The issue was brought to Kolab's attention by our team and it appears to be fixed already. The repository is accessible at this point. I can see that there is open ticket handled by our tech staff, so if there's a further issue they will...

Thank you for the report, @q-quan It sounds like the answers are swapped by mistake, but I still would like you to confirm.

Thank you for the update. I am afraid, I still have no clear understanding what's going on the server. What I tried in an attempt to reproduce the issue is transferring a non-WordPress (Joomla) website from a source CentOS 7.9 server to a target AlmaLinux 9.5 server through the Plesk Migrator...

@pleskpanel , the fix for the issue is expected to be introduced with the next Plesk update - 18.0.70, which is scheduled for 25th of May. Please note that there could always be delays with the release due to unexpected events and complication. The workaround we can suggest in the meantime is...

It is very likely due to incompatibility. @majidalizadeh.yb , can you please update SmartMail to the latest build. If it is not possible to update the SmartMail version at this point, the workaround you can try is to disable “Allow signing outgoing mail” in Tools & Settings -> Mail Server Settings.

Hello, @othmaqsa . There are various tools in Plesk that can help you minimize the amount of spam messages you receive. You can configure server-wide blacklists based on a address/domain name. You can also configure on a per email-basis Spam settings through SpamAssassin and exclude specific...

Thank you for the update. I still have no precise suggestion on what might be causing the reported issue. Please give it a try with another subscription and let us know if the issue occurs. Additionally, could you please confirm what's the status of "Mail service on this domain" related to the...

Peter, FWIW, I cannot see any unusual activity in the support queue reporting abnormalities with the server load and random crashes.

Thank you for the report, Peter. We will check and follow up with more details.

Would you mind also confirming the version of the SSL It! extension, please? Thank you in advance.

You are welcome. If the issue re-occurs would you mind also confirming the version of the SSL It! extension, please? Thank you in advance.

Thank you for the update, Luis. I forgot to mention that the nmap command is not installed by default. You can install it with: If you wish you can install it by running:

Hello, François. As long as port 8447 is opened, you shouldn't have an issue updating Plesk.

This typically indicates that you have some non-standard repositories and Plesk cannot properly resolve the dependencies. Please follow the details for Ubuntu 20.04 in this article. In case, you are intentionally using custom repositories, you can skip the repository check during Plesk...

A custom fix was published by our team, kindly refer to: https://talk.plesk.com/threads/db-query-failed-deadlock.377826/#post-961313

Hello, @enerspace . There is a similar recent report by another user, but I am unable to reproduce the behavior on a test server in order to forward it for a further review. Am I understanding correctly that the issue appears only for specific domain names? Is there any identifiable pattern for...