Open lpvm opened 3 years ago
Same issue here and had no clue what to do since the error message gives no useful info about the issue.
Also unfortunate that this script's switch to using ZeroSSL is causing significantly slower issuance, timeouts and uninformative errors.
zerossl.com says, after logging in, that "We were experiencing delays in issuing 90-day and 1-year certificates."
I want
acme.sh
to run under theacme
user. The command used to issue the certificates:su - acme -c "/usr/local/sbin/acme.sh --force --issue -d myhostname.com -d www.myhostname.com -w /usr/local/www/nginx/myhostname.com --home /var/db/acme --ecc"
The log shows that:
Changing owner/group of .well-known to www:www
acme.sh
should not attempt to change the owner and group in this case because:www
is the user and group ofnginx
acme
user is part ofwww
groupwww
user is part ofacme
group/usr/local/www/nginx/myhostname.com
directory (web root) has permissions0700
and is owned bywww:www
/usr/local/www/nginx/myhostname.com/.well-known
/usr/local/www/nginx/myhostname.com/.well-known/acme-challenge
acme.sh
(underacme
user) is able to write to/usr/local/www/nginx/myhostname.com/.well-known/acme-challenge/
acme:www
and permissions of0644
.nginx
is able to read from/usr/local/www/nginx/myhostname.com/.well-known/acme-challenge/
, a GET returns the file written there.So, there's no reason for
acme.sh
to try tochown
the user and group of the file written, or recursively of the whole.well-known/acme-challenge/
.