today returned the following error. No configuration has been changed since last renewal which finished fine.
If anyone has any idea, please help.
Processing /etc/letsencrypt/renewal/gitlab.spartagency.com.conf
2018-01-12 09:59:07,085:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/gitlab.spartagency.com.conf produced an unexpected error: Failed authorization procedure. office.spartagency.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://office.spartagency.com/.well-known/acme-challenge/BRWn7u_NTbF3r7Gx3W12YJ4vD_9rg-DyL7LBwg0m_BQ: "<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>", gitlab.spartagency.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://gitlab.spartagency.com/.well-known/acme-challenge/PG8vw-k_w2Mgo9BkEzxAXGbwMIRYhZv5d4Fcq3mj9rI: "<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>". Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/gitlab.spartagency.com/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: office.spartagency.com
Type: unauthorized
Detail: Invalid response from http://office.spartagency.com/.well-
known/acme-challenge/BRWn7u_NTbF3r7Gx3W12YJ4vD_9rg-DyL7LBwg0m_BQ:
"<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>"
Domain: gitlab.spartagency.com
Type: unauthorized
Detail: Invalid response from http://gitlab.spartagency.com/.well-
known/acme-challenge/PG8vw-k_w2Mgo9BkEzxAXGbwMIRYhZv5d4Fcq3mj9rI:
"<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
If not already done, configuring nginx to serve /.well-known/acme-challenge from a known location and then passing the document root to Certbot via --authenticator webroot --webroot-path should take care of the 404 issue.