• 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 Unable to issue SSL Cert: acme-challenge token is not available

laurenzmader

New Pleskian
I am aware that this question has been asked a few times already, but sadly the answers didn't provide a solution for me.

The following error is being repsonded when trying to issue a Let's Encrypt SSL Cert via the Plesk interface:


The subdomain is reachable via the browser. So I assume that the DNS at the registrar is configured properly.

I think that the problem might stem from the automatic HTTPS redirection, since all requests on http://api.main-domain.eu are redirect to HTTPS... and Let's Encrpyt is requesting acme-challenge via the http version.

How do I completely deactivate the https redirection for the subdomain — disabling the "Permanent SEO-safe 301 redirect from HTTP to HTTPS " option unfortunately didn't do the job.


.. but also the problem could be something completely different. I am happy about any leads and suggestions.

Thank you very much,
Laurenz
 
Back
Top