Let's Encrypt Windows Plesk Extension having trouble accessing .well-known folder

[groupedsi]

Hi!

Most of the time it's okay but I've been having a couple of websites where Let's Encrypt extension for Plesk Onyx (v17.8.xxx) is having trouble accessing the files in the .well-know folder. It's usually is because of a redirect rule or anything related to redirects in the website's programming.

The thing is, as a hosting provider, it's sometimes risky and complicated to go and change those redirect rules to be able to install/renew a Let's encrypt certificate.

When I saw that you've added a Wildcard option that could be validated by a simple DNS entry in the past months, I had to ask myself why isn't that an alternative to the .well-known validation? It would be way easier for hosting provider if the plugin would just add a DNS entry from the start when it installs the certificate and then uses the same DNS entry to check if it's still valid for renewal after a couple months.

Just like when Google asks you to validate the domain property when installing the Search Console and provides you with multiple validation choices. You can either do this by uploading a file in the website's root or by adding a TXT entry to the domain's DNS.

That would really simplify the installation/renewal process for a lot of cases where we are unsure of what's preventing the extension from accessing those files in the well-known folder.

Not sure if I'm posting this in the right place though. Should I send this here instead? https://community.letsencrypt.org/

Thanks!

[groupedsi]

Oh and by the way I realize this may not be possible for whatever reasons but an alternative would be to forget about the .well-known folder (which you can't even create in Windows most of the times as a folder name cannot start with a dot) and instead creating the file at the root of the website with a .txt or .html extension instead of using a weird no-extension file.