@RIP No worries, we are all going through the same thing (together | apart).
If you can, walk around the block.
See the random little critters that have come out to claim the world we left behind.
[we have strange African lizards roaming the streets like they own them ⦠I kinda guess they do, now]
I think we should try the --webroot -w /doc/root/path method
That bypasses the "logic" that tries to figure where to put the files and forces a specific location.
The "logic" falls on us to determine and ensure it works.
And when it does it works flawlessly.
https://certbot.eff.org/docs/using.html#webroot
We match certbot webroot to the expected root of the web server vhost config (or specific location for /.well-known/⦠therein, if specified).
So what does the HTTPS vhost config look like now?
[since everything is being redirected to HTTPS - despite our best efforts]
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for ai2.metricrat.co.uk
Using the webroot path /var/www/ai2.metricrat.co.uk/public_html for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. ai2.metricrat.co.uk (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://ai2.metricrat.co.uk/.well-known/acme-challenge/20NHCRtrSvfm-92GVL6PzmFup_4khTODI8InVVHhkvI [2607:f8b0:400f:800::2013]: "<!DOCTYPE html><html lang=\"en-US\" itemscope itemtype=\"http://schema.org/WebPage\"><head><script type=\"text/javascript\" nonce=\"5Bs"
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: ai2.metricrat.co.uk
Type: unauthorized
Detail: Invalid response from
https://ai2.metricrat.co.uk/.well-known/acme-challenge/20NHCRtrSvfm-92GVL6PzmFup_4khTODI8InVVHhkvI
[2607:f8b0:400f:800::2013]: "<!DOCTYPE html><html lang=\"en-US\"
itemscope itemtype=\"http://schema.org/WebPage\"><head><script
type=\"text/javascript\" nonce=\"5Bs"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
OK tried that. Still getting a redirect to my google site with a 404 page.
Seems like the redirect to my google site is overriding anything on my serverā¦
OK. i think I understand that. I was concerned that this site would lose its https status if it does not renew?
But I have two other sites (virtual hosts on the same IP) with google redirects that have successfully renewed their letsencrypt certificates (main domain names, not a subdomain), so i donāt really understand why this one will not renew. As you may have seen from the posts above, there is apparently no way of providing http access for certbot to do its thing with the acme challenge. Just doesnāt make any sense. Rudy (rg305) has worked very hard on mybehalf trying to troubleshoot but to no avail.
Well, the renewal deadline passed, and despite my reservations, the site is still up and it has retained itās https status without a letsencrypt certificate in place. So @JuergenAuer is quite right, that by using a new google site as a redirect to my domain, it gets its https status from Google.
Still strange that the other site, https://metricrat.co.uk, did renew OK with letsencrypt. Might try letting it expire next time around and see what happensā¦