• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. D

    Important New Plesk webmail / SOGo Webmail extension

    The "production" packages seem to only be available against payment - for all distributions. So they will likely never make it into the general Ubuntu repository - I'm not sure how that worked on Ubuntu 22.04? (They also have production builds for SoGo on 24.04 since a while, but they are only...
  2. D

    Important New Plesk webmail / SOGo Webmail extension

    SoGo themselves seems to offer nightly builds for quite some time already: deb Index of /nightly/5/ubuntu noble noble Isn't it possible to use that repository instead? Is it known why no packages are in the general repository?
  3. D

    Question Dist-Upgrade to Ubuntu 24.04 possible?

    Seems you had more problems, for me just ignoring that step and continuing with the full dist-upgrade instead of having a kernel update with reboot first worked fine, the system has been running without problems so far.
  4. D

    Issue Automatic renewal via SSLit doesn't work for wildcard certificates

    Thank you, my reseller is not providing support and I neither want to purchase a support subscription after my home was flooded just recently. It would be great if this bug could simply be fixed instead.
  5. D

    Issue Automatic renewal via SSLit doesn't work for wildcard certificates

    This issue is still persisting by the way and I haven't been able to find a solution, for last month all wildcard domains failed with "Detail: No order for ID XXXXXXXXX", all normal certificates worked normally.
  6. D

    Question Dist-Upgrade to Ubuntu 24.04 possible?

    The instructions are available in the meanwhile. The step for just updating the base-kernel didn't work for me, as python3 upgrade dependencies couldn't be resolved, but just skipping it and directly continuing with dist-upgrade and executing the commands to restore plesk after that worked just...
  7. D

    Important New Plesk webmail / SOGo Webmail extension

    When is SOGo going to be compatible with Ubuntu 24.04? After dist-upgrade we noticed a 502 error, tried to reinstall the extension and got another error. The incompatibility should be noted on...
  8. D

    Question Dist-Upgrade to Ubuntu 24.04 possible?

    Plesk seems to support the new Ubuntu, but no hint at it either bein possible, not possible or possible lster as it was with the last two new releases.
  9. D

    Issue Automatic renewal via SSLit doesn't work for wildcard certificates

    Hello, I actually have this issue ever since we changed over to SSLit!, the domains using normal .acme folder verification do correctly renew automatically, all domains that use wildcard certificates and do DNS check do not. I always get this mail: Could not secure domains of xxx (login xxx)...
  10. D

    Issue Can't remove PHP 8.0 due to Roundcube - but PHP 8.1 is available

    I set the 8.1 handler anyway, not knowing where the variable above comes from, Roundcube is now successfully using PHP 8.1, but I still can't remove PHP 8,0 without removing roundcube, sigh.
  11. D

    Issue Can't remove PHP 8.0 due to Roundcube - but PHP 8.1 is available

    I found this article, but the files don't look like they do there: https://support.plesk.com/hc/en-us/articles/213367729-How-to-change-PHP-version-for-webmail-in-Plesk-for-Linux I instead have this: FcgidInitialEnv PP_CUSTOM_PHP_CGI_INDEX "<?php echo $roundcubePhpHandler; ?>" and the...
  12. D

    Issue Can't remove PHP 8.0 due to Roundcube - but PHP 8.1 is available

    Plesk is refusing to allow me to remove PHP 8.0 without uninstalling Roundcube. But Roundcube is delivered with Plesk in Version 1.6, which does support PHP 8.1 which is available by OS vendor. Any way I can get around this?
  13. D

    Issue Plesk Backup Restoring isn't working

    Multiple times tried to restore a plesk backup of one domain today, always got a success note in Plesk and via e-mail but nothing at the domain was actually changed, neither files, database or configuration, despite everything selected. It's just as if it wouldn't do anything but touch all files...
  14. D

    Issue error_log not rotated properly since approximately February update

    No problem, much better to know there is an issue than wondering what is going on, thank you so much. By the way: Does anyone know for chance how I can correctly remove / rotate php-fpm_error.log? I have deleted the log about six times now, but after a few hours it's just back again with all...
  15. D

    Issue error_log not rotated properly since approximately February update

    No, unfortunately the automatic logrotate did not work.
  16. D

    Issue error_log not rotated properly since approximately February update

    That latency being at least 15+ minutes, while executing stats doing it correctly immediately seems odd to me. In any case, it feels like something here is no longer working correctly since early march. None of what I saw today has been an issue before.
  17. D

    Issue error_log not rotated properly since approximately February update

    Interesting. So I can reproduce the following on my instance: logrotate command does visibly only empty the file, nothing else. Only when I execute /usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=<mydomain> the rotation actually happens. So If i execute logrotate three times...
  18. D

    Issue error_log not rotated properly since approximately February update

    So, I have no idea what I'm actually doing, but executing /usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=<mydomain> does correctly rotate the logs? You can now see the previously vanished big logs that were rotated into packaged files (100 MB and 75 MB). How is that even...
  19. D

    Issue error_log not rotated properly since approximately February update

    I just tried the "logrotate -f /usr/local/psa/etc/logrotate.d/<domain name>" way you had mentioned in your post, the error_log was removed, but not rotated. It's just been emptied. Weird. Maybe that was a problem due to it having become so big, but I see that my access_log also has not been put...
  20. D

    Issue error_log not rotated properly since approximately February update

    Here is a screen, actually only the access_log was rotated when doing the fix mentioned by Peter. The error_log doesn't rotate on manual either.
Back
Top