• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Let'Encrypt SSL not issued

Nicola Urbinati

Basic Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
Version 18.0.52 Update #3
Hi,

I'm trying to (re)issue a certificate for a domain, and LE says:

Code:
Encountered issues while issuing the certificate for www.domain.com
Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/242299753857.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: 2606:4700:3031::6815:3843: Invalid response from https://www.domain.com/.well-known/acme-challenge/4jDhLSxIWYvzRfOoZ1H6mj26XMWEb4A59AF-D-B9kLQ: 526

How to fix it? Is it doing ACME and not DNS challenge?
 
This essentially means that the IPv6 address of your domain is not pointing to the IPv6 address of your Plesk server.

The IPv6 address in your error message belongs to Cloudflare, which indicates that you are using Cloudflare (at least) for IPv6.

So you'll either have to change the IPv6 address of your domain to the IPv6 address of your Plesk server (so that both IPv4 and IPv6 addresses are pointing to your Plesk server) or you'll have to point your IPv4 address to Cloudflare too and follow the steps outlined here: https://support.plesk.com/hc/en-us/...oudflare-s-Full-Strict-encryption-with-Plesk-
 
Back
Top