Resolved Let's Encrypt Auto Rewew - leading dot in folder name issue

[scottjack1979]

Hello there,

I've been receiving some error messages for auto renewals of Let's Encrypt, have seen some related issues but not quite the same error.

When I try to auto renew, I've turned off any 301 redirects and get an error about not being able to find the token. It should be checking the URL here:

http://example.co.uk/.well-known/acme-challenge/eZEqr0QAnKXzcVgrApalT2OkWApJUweaEP6SA8TaVG0

The problem is the leading dot before the .well-known this makes the web server think it's at the server root so is trying to then load

http://acme-challenge.localhost:80/eZEqr0QAnKXzcVgrApalT2OkWApJUweaEP6SA8TaVG0

which obviously doesn't exist.

I've tried a lot of things within ASP.NET to fix thi, serving MIME types, checking for any redirects in web.config, but nothing seems to be working, I believe this has only been a problem since I updated to the most recent version of Obsidian and has been working for years without any manual intervention previously, can anyone help with this please?

For now I've had to install manual certs from other organisations but it's obviously much more efficient with the automatic renewals in Plesk with LE.

Thanks

 

[scottjack1979]

If anyone else has this error, after days of messing around it was the permissions on the acme-challenge folder (that I didn't even know was there!)

Unable to issue Let’s Encrypt certificate for domain in Plesk: misconfiguration of the Common Challenge Directory

Applicable to: Plesk Obsidian for Windows Symptoms The Plesk of 18.0.26 version or newer is installed on the server Unable to issue a Let’s Encrypt certificate in Domains > example.com &g...

support.plesk.com

That article helped me fix.