Search results

Hello, @inspyred. Could you please run the following command and confirm if the output matches the value of "Total" The postfix/spawn timeout issue, it is really difficult to point out what might be causing it. It might be due to the configuration, permissions, SELinux. If you have the option...

Have you tried re-testing the Nginx configuration? If not, please try running the following command:

@Kaspar, just a quick update about this report. After further consideration, our team concluded that the case (PPP-64266) classifies as a UI bug rather than functional. The text is misleading and it will be fixed in the upcoming bug-fix weeks. On the other hand, we created another case...

Hello, @flyd. Our engineers are still investigating the case. We understand that this situation is not pleasant. Our team is doing its best to find the culprit of the issue as quickly as possible. Thank you in advance for your understanding on the matter.

Hello, everyone. We have released the fix for the issue with the backup creation. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.65 Update 2:

Thank you for the update, @Sahi. Could you please run the following command: Let us know if the output indicates Roundcube is already installed or if it attempts to install it. Thanks in advance.

Sounds like the error might result from a Plesk bug (EXTPLESK-3895). Could you please try the workaround from this article?

Thank you for your update, @Maarten. I understand your point. However, even with port 587 enabled, some user might prefer to connect over port 465 under specific circumstances. Considering that the setting could be tweaked through panel.ini, I would personally prefer to see how much demand there...

Hello, Michael. Plesk itself should remain working even after 1st of July, 2025, but as you mentioned you won't receive updates and support.

There is an existing UesrVoice request for this suggestion. Please consider voting for it. The more popular a request becomes the higher the chances for consideration are.

Hello, @jmar83. We attempted the reproduce the reported issue, however, the bind-address value is changed accordingly in /etc/mysql/my.cnf and remote access is established without an issue. With that said, the issue you are experiencing is not due to a Plesk bug. I would suggest opening a...

Hey, @doekia. This sounds like a corrupted database. Please try applying the solution for recreating the missing tables provided by Igor here. If that doesn't work, the next best option will be to consider getting in touch with our support team. To sign-in to support and open a ticket go to...

Hm, could you please try re-installing the Plesk Email Security extension?

Essentially, this means that Debian 10 will reach EOL on June 30, 2024 and security patches will no longer be provided directly by the vendor, which might result in vulnerabilities. With ELS Plesk will continue to deliver full-scope product updates and technical support You can find instructions...

Hello, @Sahi . Judging by the provided screenshot it looks like Roundcube is already enabled. Note that the checkbox won't remain ticked when you click on "Enable". The indicator is the green checkmark. Regarding the webmail not working, please provide additional details like what actions you...

Thank you for the update, Jan. I am not quite sure I was able to understand, sorry. Are you saying that the bind-address value in /etc/mysql/my.cnf is set to 127.0.0.1 after enabling "Allow local MariaDB/MySQL server to accept external connections"? If yes, have you tried restating the database...

It will be best to consider an upgrade. A patch most likely will not be introduced for Plesk 18.0.59 considering it is currently 6 updates ahead. We understand the inconvenience caused by the issue and we are extremely sorry. Could you please try the workaround provided in #post-954868 until...

Hey, @vin_12. The issue might be related to a modification of Plesk's CSS files. If you have the option, it will be best to open a ticket with our support team so they can connect to your server and investigate the case further.

There's no ETA for the release of this bug fix yet. It has relatively low priority considering it is just "cosmetic" and has no actual negative impact. We appreciate everyone's patience and understanding on the matter. A possible workaround we can suggest at the time being is to try...

Thanks. How about in the /wp-content folder? As far as I am aware, this is in reference to the local browser cache rather than the server cache.