Search results

@Sebahat.hadzhi thank you. I tried a workaround. I solved the problem by renaming the old mailbox, created a new one and imported mails with Plesk import tool.

I’m having a strange issue with mailbox storage reporting on my Plesk server. In the Plesk interface, one of my mailboxes is constantly shown as full — for example, 29 GB / 20 GB used. When I run the following command via the console: plesk repair mail [email protected] the usage briefly shows...

We recently migrated some servers from 20.04 to 24.04 without any problems. We used the Plesk Migration Manager, too.

What we often need the mail_auth_view function for is when a user has lost their password – and that happens quite frequently. Of course, we could generate a new one or point the customer to the “forgot password” function. The problem, however, is that other mail clients often keep sending the...

We are using a primary DNS server that manages all domains as an authoritative DNS-only server. On that server, we cannot simply adjust the DNS template because it holds many different MX records for different domains. The primary DNS server distributes the DNS entries to other DNS servers...

I would like to update the MX record for all domains on my Plesk server so that they all point to the same new mail server. Ideally, I’d like to do this in one go via the Plesk CLI (e.g. using plesk bin dns) instead of editing each domain individually. From what I’ve read so far, it doesn’t...

@learning_curve Thanks for your reply, but I think you might have misunderstood me. I am not talking about disabling auto-updates and doing everything manually – I am aware that this option still exists. What I mean is the old functionality Plesk used to have: the ability to choose between...

The only solution I see for this actual problem with updates is to let users decide for themselves whether they want to install an update immediately upon release, or (as in the past) to have the option of installing only those updates that have been tested for a longer period and are considered...

It actually does affect a large number of users. Why should an update only be stopped if every single user is impacted? Even if it doesn’t break things for all, the fact that it disrupts many is reason enough to reconsider or pause it. That said, it seems the issue has been resolved with the...

@Sebahat.hadzhi I hope that the current update 18.0.72 will be quickly withdrawn due to the issue and is no longer being distributed until the problem has been fixed?

@Sebahat.hadzhi Perfect, that’s exactly the behavior I was hoping for! This way I can ensure the target server consistently uses the desired method without having to adjust anything manually after the migration.

One more question: what happens during a server migration to a new Plesk server where password hashing is enabled — will previously encrypted passwords be converted to hashes during migration, or will they remain encrypted until the next password change? I couldn’t find anything about this...

Hi everyone, I just read in the Plesk changelog for 18.0.72: My understanding is the following: Hashing is now the default setting. This applies not only to new installations, but also to existing ones after updating Plesk. Newly set passwords will be hashed, while existing passwords remain...

@Sebahat.hadzhi great news. Thank you!

@Kaspar Thank you very much for testing. So, that could be a suitable workaround until the fix is ready. We will try that.

We are quite disappointed that Plesk has been aware of this bug for such a long time without a fix, as it can cause serious mail delivery issues not only for us but for many other server administrators as well. Since it may take a long time before the problem is officially resolved, we are...

@Sebahat.hadzhi the ">" is missing in your script. Correct script would be: echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf && service nginx restart For systemctl use systemctl restart nginx instead to restart nginx

As already described: There is something missing in the code, the “>” is missing: echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf && service nginx restart

Keep in mind that if you use the Plesk watchdog extension, nginx will be restarted soon. So first disable nginx monitoring in watchdog.

How many email addresses are set up? We are using Postfix with thousands of mail addresses with excessive use without any problem.