• 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 the .well-known / acme-challenge folder is protected by a username

Sylvain

New Pleskian
Hello,
updating a letsencrypt certificate cannot be done on a domain, because access to the .well-known / acme-challenge folder
is protected by a username / password.
It has no reference to that in a web.config whatever it is installed on this domain.
Do you know how to overcome this concern?
 
Hi Sylvain,

Please check the following things:
1) Check if there is a "protected directory" for this folder via Plesk > Protected Directories

2) Maybe you need to reconfigure your folder permissions, can you access this folder via Plesk > File Manager?
When you place a test.txt file inside your httpdocs directory, can you access it via the web?
Check if the IIS Worker Process user had read access to the directories and the files.

3) Maybe it is in your web.config file, temporary rename your web.config to web.config.backup and see if you can access a let's encrypt validation file like so:
 
Hello,
thank you for your comeback.
The concern encountered was related to the protection by htpasswd put in place on the statistics.
Disabling it solved the problem.
 
Back
Top