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

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

bsssrl

New Pleskian
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 as root is the following:

Bash:
/root/.acme.sh/acme.sh --issue -d $domain -d www.$domain --force -w /var/www/vhosts/$domain/httpdocs/ --log $logfile

Here is the exact same issue without reply for plesk 17. I've already had this problem on plesk 17 and I just solved disabling let's encrypt extension and adding following directive to nginx

NGINX:
location ~ /.well-known {
    allow all;
}

In plesk 18 disable or remove the extension is not enough. I also tried to disable Sectigo SSL and SSL It!

Any help would be appreciated!
 
Solved. Inside vhost/conf/nginx.conf something related to let's encrypt remains until rebuild (using Webserver Configurations Troubleshooter extension).
 
Back
Top