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

Forwarded to devs Lets Encrypt renewal of forwarded domain

TomBoB

Silver Pleskian
TITLE:
Lets Encrypt renewal of forwarded domain
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CentOS Linux 7.6.1810 (Core)‬, Plesk Onyx Version 17.8.11 Update #67
PROBLEM DESCRIPTION:
Forwarded domain according to How to allow HTTPS and configure SSL certificate on domain in Plesk which has Hosting type set as Forwarding?
Domain forwarded to is hosted with someone else.
Domain forward necessary as website is elsewehere, but emails are still with us. Https needs to be secure for webmail.

renew domains Lets Encrypt cert produces an error.​
STEPS TO REPRODUCE:
have subscription with one domain. forward the domain to another domain with another host (or even to a page in a subfolder on that outside domain)
let Lets Encrypt renew the cert for the original domain.​
ACTUAL RESULT:
leads to failure as lets encrypt checks for the challenge on the domain that is being forwarded to (which we have no contorl over), not on the original domain.​
EXPECTED RESULT:
renewal works​
ANY ADDITIONAL INFORMATION:
Could not secure domains of client with Let`s Encrypt certificates. Please log in to Plesk and secure the domains listed below manually.
Securing of the following domains has failed:

* 'clientdomain.com'
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/374170658.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: Invalid response from https://forwarded-to-domain.com/sub...e/2MY1cUhtJbo4QnlfhJP3j0fLkojkA15gRX2OfJVCo0Y [35.222.37.107]: "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"utf-8\">\n <meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\">\n <meta"

The following domains have been secured without some of their Subject Alternative Names:

<none>

Could not renew Let`s Encrypt certificates for client. Please log in to Plesk and renew the certificates listed below manually.
Renewal of the following Let`s Encrypt certificates has failed:

* 'Lets Encrypt clientdomain.com' [already expired]
[-] clientdomain.com
[-] webmail.clientdomain.com
[-] www.clientdomain.com

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/374178603.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: Invalid response from https://forwarded-to-domain.com/sub...e/IAOOoUgFvGv9ZNNlc2yVm0NPNXf90Jg2dgStCnhQdEc [35.222.37.107]: "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n <meta charset=\"utf-8\">\n <meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge\">\n <meta"
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Hello,

At the moment "webmail.<domain>" may be only included as a Subject Alternative Name into certificate for main domain.
LE certificate for "forwarding" domains can not be issued in an automatic manner.
It is because LE requires to pass http challenge (put special file with verification token and access it from LE server) to validate domain.
So this behavior does not work for forwarding domains because request is forwarded to another server which is out of our control.
As we can not issue certificate for main domain- webmail for such domains can not be secured.
 
Back
Top