• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. F

    Resolved Docker doesn't start after upgrade to Debian 11

    Thanks again! I've updated to the latest versions and everything continues to work.
  2. F

    Resolved Docker doesn't start after upgrade to Debian 11

    Thank you! I've now removed the Docker extension, reinstalled, and have setup the containers from scratch and now it's working here to. However, I'm getting an update notification when running apt list --upgradable and now I'm unsure if it's safe to upgrade: # apt list --upgradable Listing...
  3. F

    Resolved Docker doesn't start after upgrade to Debian 11

    OK, thank you. I wish I had seen this earlier and I'm even not sure if this this still valid or just outdated documentation. As I understand, support for Debian 9 was dropped by Plesk starting with 18.0.45 so it'd be great if Docker would be supported with the current supported OS versions.
  4. F

    Resolved Docker doesn't start after upgrade to Debian 11

    My guess is that it's related to AUFS not supported on Bullseye which I now read in the release notes.
  5. F

    Resolved Docker doesn't start after upgrade to Debian 11

    I've updated from Debian 9 to Debian 11 using the recommended steps and everything worked fairly okay. Except for one thing where Docker doesn't start anymore. Using systemctl start docker produces this output in journalctl -xe and I don't know how to proceed. Aug 02 14:33:48 <hostname>...
  6. F

    Issue Unable to send emails after upgrading to 18.0.34

    I had the very same issue after updating to 18.0.34 this morning and switching to qmail and back to postfix fixed it. Also had to fight IP address banning after my own IP was banned due to failed login attempts.
Back
Top