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

Failing to renew Let's Encrypt certificates

brainforge

Basic Pleskian
User name: brainforge

TITLE

Failing to renew Let's Encrypt certificates

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Centos 7 Plesk Obsidian Version 18.0.23

PROBLEM DESCRIPTION

Get emails / error messages like the following.
Can access fine from browser.
Details:
Type: urn:ietf:params:acme:error:connection
Status: 400
Detail: Fetching https://....../.well-known/acme-challenge/...... Timeout during connect (likely firewall problem)


STEPS TO REPRODUCE

Renew cerificate for a domain.

ACTUAL RESULT

Get above error message.
Later get an email with same message.

EXPECTED RESULT

Preferably renew works without any further action.
Improve error message to indicate other areas to examine / change e.g. DNS

ANY ADDITIONAL INFORMATION

See Issue - Let's encrypt not renew

Setup Plesk and DNS to use both PIPV4 and IPV6 addresses.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Looks like will need to everywhere temporarily disable SEO safe 301 as per the January 22, 2020 17:14 comment here:


What's the timescale for internal request ID EXTLETSENC-769?
Or even in short-term providing link to additional information in the error message....
 
Correction looks like SEO safe 301 is not the issue in those I've tried so far.

Instead - have to remove the AAAA records for IPV6 from the DNS - then Let's Encrypt renewal works.
 
Back
Top