• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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