• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

caa

  1. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    There seems to be numerous items about: Details Invalid response from https://acme-v02.api.letsencrypt.org/acme/finalize/356300830/211673632166. Details: Type: urn:ietf:params:acme:error:caa Status: 403 Detail: Error finalizing order :: Rechecking CAA for "example.com" and 18 more identifiers...
  2. PReimers

    Forwarded to devs DNSSEC and CAA not working

    TITLE: CAA entry is not covered by DNSSEC PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Ubuntu 16.04, Plesk 17.8.11, MU #1 PROBLEM DESCRIPTION: After adding a CAA entry in DNS (and waiting serval days) a DNS query responds with: STEPS TO REPRODUCE: Enable (and configure)...
Back
Top