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

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