• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Recent content by TorbHo

  1. TorbHo

    Question Change MX record with Plesk CLI

    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...
  2. TorbHo

    Question Change MX record with Plesk CLI

    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...
  3. TorbHo

    Issue 18.0.72 broke IP Default Webites Ubuntu 24

    @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...
  4. TorbHo

    Issue 18.0.72 broke IP Default Webites Ubuntu 24

    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...
  5. TorbHo

    Issue 18.0.72 broke IP Default Webites Ubuntu 24

    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...
  6. TorbHo

    Issue 18.0.72 broke IP Default Webites Ubuntu 24

    @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?
  7. TorbHo

    Question New password hashing option for email accounts

    @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.
  8. TorbHo

    Question New password hashing option for email accounts

    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...
  9. TorbHo

    Question New password hashing option for email accounts

    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...
  10. TorbHo

    Resolved Plesk does not retain DKIM keys during server migration

    @Sebahat.hadzhi great news. Thank you!
  11. TorbHo

    Resolved Plesk does not retain DKIM keys during server migration

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

    Resolved Plesk does not retain DKIM keys during server migration

    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...
  13. TorbHo

    Resolved SNI error

    @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
  14. TorbHo

    Resolved 421 Misdirected Request

    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
  15. TorbHo

    Resolved 421 Misdirected Request

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