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

Issue First trial with SSL certificate / Authorization for the domain failed.

eric91611116

New Pleskian
Dear all,
I am new here. Recently I bought a domain etfdp.com at godaddy.com. Then I subscribed a hosting service at AspHostPortal.
At godaddy side, DNS settings:
I have added a A record with an IP 23.111.13.151 pointing to AspHostPortal.
At AspHostPortal, I uploaded my web application. I can access it.
Since https SSL is a must, I tried to use the "Let's Encrypt SSL/TLS certificate". I got the below error msg

Could not issue an SSL/TLS certificate for etfdp.com
Details
Could not issue a Let's Encrypt SSL/TLS certificate for etfdp.com. Authorization for the domain failed.
Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/238181962037.
Details:
Type: urn:ietf:params:acme:error:dns
Status: 400
Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.etfdp.com - check that a DNS record exists for this domain

I appreciate it much for anyone who can share your advice and experience.

Thanks,
Eric
 
Last edited by a moderator:
The TXT record in the domain is required if you try to create a wildcard SSL certificate. If you do not need a wildcard (which is most often the case for many users), simply issue a normal SSL certificate. Then the TXT record will not be required and the tokens can be exchanged with Let's Encrypt right away.
 
Back
Top