• 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!
  • 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. V

    Forwarded to devs After upgrading to Plesk 18.0.30 apache stops randomly.

    The issue happens only on very specific setups (e.g. with specific Docker images running), so looks like it should be relatively rare. The workaround will be automatically reverted on the next update, so no extra actions should be needed.
  2. V

    Issue No version above 18.0.28 available for upgrade

    Your target server uses Debian 8, which is not supported by Plesk anymore (so no new versions). See also Feature Deprecation Plan I suggest using a more modern OS supported by Plesk, such as Debian 10 or 9.
  3. V

    Issue Downgrade Plesk 18.0.30 to 18.0.29

    Unless you have a VM snapshot you can revert to, there is no way. Plesk doesn't support downgrade.
  4. V

    Forwarded to devs After upgrading to Plesk 18.0.30 apache stops randomly.

    FYI: the issue is confirmed as PPPM-12387 and will be fixed in 18.0.31. Until then, if you're affected, it is sufficient to use the provided workaround.
  5. V

    Forwarded to devs After upgrading to Plesk 18.0.30 apache stops randomly.

    This is expected. Is the issue still present for you after applying the workaround?
  6. V

    Resolved After upgrade to 18.0.30 phpmyadmin not Working.

    It's slightly weird that a restart was required. Anyway, the message means that your phpMyAdmin installation now operates without configuration storage (settings will not be saved on server side, only in your cookies), unless you've already addressed this somehow. The message explains why this...
  7. V

    Resolved Uninstall PHP from OS vendor

    Yes, it's possible since Plesk Obsidian.
  8. V

    Resolved After upgrade to 18.0.30 phpmyadmin not Working.

    Those that had a problem and restarting sw-cp-server service helped, could you post your OS, please? Did you have any errors or warnings on update to 18.0.30 (at least in /var/log/plesk/install/autoinstaller3.log)?
  9. V

    Resolved Plesk 18.0.30 and apache graceful restart

    Thank you for the provided information. Those affected may try to workaround the issue by executing as root: sed -i -e 's|^\(apache_status_linux_debian\)|_\1|g' /opt/psa/admin/sbin/pleskrc
  10. V

    Forwarded to devs After upgrading to Plesk 18.0.30 apache stops randomly.

    Thank you for the provided information. Those affected may try to workaround the issue by executing as root: sed -i -e 's|^\(apache_status_linux_debian\)|_\1|g' /opt/psa/admin/sbin/pleskrc
  11. V

    Question Why doesn't MySQL/MariaDB show within the "Services Management" to be able to restart?

    Simply because Plesk itself requires DB for its operation. However, you can restart the DB and Plesk application server from the /repair page on your Plesk instance. Normally link to this page is shown when Plesk is unwell (e.g. DB is not available).
  12. V

    Resolved After upgrade to 18.0.30 phpmyadmin not Working.

    Try restarting sw-cp-server service. If that doesn't help, run plesk repair installation.
  13. V

    Question Is This A Problem: "Fix incorrectly set sender for outgoing mail"?

    If none of your outgoing mail is wrongfully classified as spam, you don't need to enable this option. What this option does is relatively fully explained in the hint text: The problem: some software (specifically, web applications, such as CMS'es) may send mail with incorrect settings (wrong...
  14. V

    After mu#23 - plesk sendmail[]: Trying to resolve the e-mail alias:

    @Wiz , glad to hear your original problem is resolved. As for check-quota failures, you may try setting null_sender attribute to a full mail address.
  15. V

    After mu#23 - plesk sendmail[]: Trying to resolve the e-mail alias:

    @Ian Collier , you have outdated package installed. Please update to the latest version. You may use the following command: plesk installer update
  16. V

    After mu#23 - plesk sendmail[]: Trying to resolve the e-mail alias:

    To those affected: please also check your package versions. Run either of the following commands and post the output here. dpkg -l 'plesk-mail-*-driver' | cat # if you have Debian or Ubuntu rpm -qa | grep 'plesk-mail-.*-driver' # if you have RedHat, CentOS, or CloudLinux Thank you.
  17. V

    Issue Repository BitBucket

    SSH public keys (deployment keys) are used for client identification. Host public keys (which are stored in .ssh/git_known_keys file in this case) are used for server identification. These are two different entities. I suggest trying option (1) that was outlined in the previous post -- just...
  18. V

    Issue Repository BitBucket

    This means that ssh-keyscan -H bitbucket.org has failed to retrieve any keys. This may happen due to a number of reasons, including networking issues between your box and BitBucket. As a workaround you may try either of the following: Use SSH on port 443 as suggested at the bottom of...
  19. V

    Important About upcoming update

    @x86, are you sure you're having the same error. I don't see the error message from Apache itself in your post. Please check Apache error logs for details - why it could not be restarted. If you haven't done a dist-upgrade from Debian 7 lately it's seems unlikely that you've got the same...
  20. V

    Resolved apt update fails to get autoinstall.plesk.com/ubuntu/LETSENCRYPT

    Most likely autoinstall.plesk.com on your server points to a partial mirror instead of the official download site. To use the official download site make sure /etc/hosts doesn't have autoinstall.plesk.com entry and /etc/resolv.conf uses public DNS servers (e.g. 8.8.8.8 and 8.8.4.4 to use Google...
Back
Top