• 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

Search results

  1. V

    Question SSH Terminal

    This is resolved with the latest update of SSH Terminal.
  2. V

    Resolved Rejecting Plesk SSH Connection

    This is resolved with the latest update of SSH Terminal.
  3. V

    Input Support for PHP 8.0 in Plesk

    xmlrpc extension is no longer available (upstream discontinued its support). ionCube loader extension is not available yet (no version compatible with PHP 8). imagick extension is not available yet (no version compatible with PHP 8).
  4. V

    Input Support for PHP 8.0 in Plesk

    Moreover, many popular applications do not work on PHP 8 yet.
  5. V

    Resolved mail account can not be crated - ERROR:__main__:mails.domain_id may not be NULL

    Check the article Igor posted above. If the last symptom is not present, this might be a previously unknown issue, in which case you're advised to address Plesk support.
  6. V

    Issue Update Plesk not possible Version 18.0.28 -> 18.0.31

    To update to the latest Obsidian you may run: plesk installer upgrade plesk release To install the latest update in scope of the same 3-digit version: plesk installer update Updating to next versions on unsupported OSes (such as Debian 8, which has reached EOL) is unsurprisingly not possible.
  7. V

    Question phpmyadmin 5.0.2 and php 7.4

    Sorry, but no. If you wish to have a customized phpMyAdmin installation (including any supported PHP version), you are free to install it manually on a domain. However, among other things you'll loose functionality of automatic login from Plesk.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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?
  13. 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...
  14. V

    Resolved Uninstall PHP from OS vendor

    Yes, it's possible since Plesk Obsidian.
  15. 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)?
  16. 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
  17. 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
  18. 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).
  19. 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.
Back
Top