You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is with setup-apache-ssl-key: Failed authorization procedure. domain.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from domain.com
Actually, I saw that the httpd config, to be specific /etc/httpd/extra/httpd-acme.conf, has this Alias /.well-known/acme-challenge/ "/var/lib/letsencrypt/.well-known/acme-challenge/"
I tested that apache really points .well-known/acme-challenge to the /var/lib/letsencrypt/... dir.
Here is the problem, in the file /usr/sbin/setup-apache-ssl-key, I saw this line certbot --text --debug --agree-tos --email ${EMAIL} --webroot -w /srv/http/ -d ${HOSTNAME} certonly, if I am right I think it should be /var/lib/letsencrypt/ instead of /srv/http
Update: I confirm that it's the case, I update the setup-apache-ssl-key and everything now works.
The text was updated successfully, but these errors were encountered:
I'm using
l3iggs/owncloud:9.1.2-1
The problem is with
setup-apache-ssl-key
:Failed authorization procedure. domain.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from domain.com
Actually, I saw that the httpd config, to be specific
/etc/httpd/extra/httpd-acme.conf
, has thisAlias /.well-known/acme-challenge/ "/var/lib/letsencrypt/.well-known/acme-challenge/"
I tested that apache really points
.well-known/acme-challenge
to the/var/lib/letsencrypt/...
dir.Here is the problem, in the file
/usr/sbin/setup-apache-ssl-key
, I saw this linecertbot --text --debug --agree-tos --email ${EMAIL} --webroot -w /srv/http/ -d ${HOSTNAME} certonly
, if I am right I think it should be/var/lib/letsencrypt/
instead of/srv/http
Update: I confirm that it's the case, I update the
setup-apache-ssl-key
and everything now works.The text was updated successfully, but these errors were encountered: