October 31, 2018, 9:46am
Verification path containing “.” symbol “/.well-known/acme-challenge/” is causing that the right file can not be found.
If the verification path was “/well-known/acme-challenge/” i.e. without “.” symbol I wouldn’t have any issues with HTTP verification.
Do you know why this happens? Please share.
looks like a problem with your webserver configuration.
What's your domain name? And your Webserver + operation system?
October 31, 2018, 10:26am
My guess is…
Second guess is…
.htaccess file is blocking files that start with “.”
October 31, 2018, 1:04pm
Thank you JuergenAuer - you’re right - it is the webserver Apache that caused it. I have confirmation from my hosting provider who claims DNS verification is the only manual option for now.
October 31, 2018, 1:06pm
Thanks rg305 - I’ve tried deleting htaccess - still the same, but was worth trying.
Ref. Windows - well I have state of art Win10Pro, so system is not an excuse
October 31, 2018, 7:16pm
Were you able to create the
November 1, 2018, 6:46am
Good point, yes Apache allowed creation of such folder starting with “.”.
It seems that either hosting provider simply wants to force people to buy far more expensive plans with automatically renewed Let’s Encrypt certs or it is tricky for Apache to make such URL’s containing folders starting with “.” work.
December 1, 2018, 6:46am
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.