• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

acme-challenge

  1. L

    Issue Unable to issue SSL Cert: acme-challenge token is not available

    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...
  2. J

    Issue Lets Encrypt not using DNS-01 for wildcard cert

    Did something change? I'm pretty sure wildcard certs used DNS-01 challenge, but recently I started getting an error every time that it tried the acme challenged (and failed, since I block it on the firewall). How can I force it to use DNS-01? I'm using external DNS. Getting: Invalid response...
  3. bsssrl

    Resolved acme.sh Invalid response from .well-known/acme-challenge

    I need to use acme.sh in order to provide ssl to a virtualhost, I need to do it manually without let's encrypt integrated in plesk. The error is the following: Verify error:Invalid response from vhost/.well-known/acme-challenge/F-h-S9RFcjsfonu1JKd_o7r23Jg6DjQ6NOb0pDwe6-w The command I execute...
  4. J

    Input add external DNS APIs for Letsencrypt extension

    I use Gandi.net's DNS service for most of my domains. I also use wildcard certificates issued by the Letsencrypt extension. However the automatic update of the DNS records with the _acme-challenge only works if the DNS is handled within Plesk, if I understand correctly? Gandi, as many DNS...
  5. A

    Issue .well-known/acme-challenge 403 forbidden

    Environment: Plesk Onyx 17.8.11 Update #54 OS: Debian 8.11 64bit In order to exclude problem with letsencrypt, I just created .well-known/acme-challenge/index.html. If I try to access from browser I get 403 forbidden The problem is not related to permission or nginx directive, indeed if I just...
Back
Top