• 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. J

    Issue Your IMAP client does not appear to correctly implement Unicode messages, see https://tools.ietf.org

    It's frustrating, we have been like this since the weekend and without any solution. Help!
  2. J

    Resolved API call failed: <urlopen error [Errno -3]

    Since we updated to Plesk Obsidian, every afternoon the system returns this error to me: Cron <root@fae> dgri-report collect on_unchanged_config=nop API call failed: <urlopen error [Errno -3] Temporary failure in name resolution> error: failed to collect system info Any clue to solve it...
  3. J

    Resolved Kernel Care extension not open in Plesk Panel

    related to the Kerner Care error, the system sent me this report: Cron <root@.....> /usr/bin/kcarectl -q --auto-update Traceback (most recent call last): File "/usr/bin/kcarectl", line 5282, in <module> sys.exit(main()) File "/usr/bin/kcarectl", line 2797, in main...
  4. J

    Resolved Kernel Care extension not open in Plesk Panel

    Hi, Yesterday we updated Plesk Obsidian 12.8.20 By opening the Kernel Care extension in the Plesk panel within extensions, which we have acquired. It does not open and remains indefinitely thinking .... What can we do ? Thank !
  5. J

    Issue Your IMAP client does not appear to correctly implement Unicode messages, see https://tools.ietf.org

    Hi, Yesterday we updated Plesk Obsidian 12.8.20 and this morning our clients report us an error when sending messages from IMAP server. It returns an error message: The IMAP server wants to alert you to the following: Your IMAP client does not appear to correctly implement Unicode messages, see...
Back
Top