more clarificaions on which cmd is root

master
nic 2022-06-09 20:30:44 -05:00
parent 5171b5aa31
commit a77a457b8c
1 changed files with 3 additions and 3 deletions

@ -45,7 +45,7 @@ sudo su - -s /bin/bash acme
crontab -e crontab -e
``` ```
Adjust path to your acme.sh installation script Adjust path to your acme.sh installation script, insert into your non-root crontab
``` ```
12 0 * * * /usr/share/acme.sh/acme.sh --cron --home "/etc/acme-sh" > /dev/null 12 0 * * * /usr/share/acme.sh/acme.sh --cron --home "/etc/acme-sh" > /dev/null
``` ```
@ -53,8 +53,8 @@ Adjust path to your acme.sh installation script
## Webserver issue method ## Webserver issue method
When using the webserver method, you need to define the directories acme.sh writes to and adjust ownership to our non-root account. While monitoring the issue event logs, you might observer additional file structure permission errors when ran as non-root. From our experiences, those can be ignored as the script does not hard fail as the important directories and files creation is functional. Maybe this is where the --force should be used? When using the webserver method, you need to define the directories acme.sh writes to and adjust ownership to our non-root account. While monitoring the issue event logs, you might observer additional file structure permission errors when ran as non-root. From our experiences, those can be ignored as the script does not hard fail as the important directories and files creation is functional. Maybe this is where the --force should be used?
``` ```
mkdir -p /var/www/EXAMPLE.COM/htdocs/.well-known/acme-challenge sudo mkdir -p /var/www/EXAMPLE.COM/htdocs/.well-known/acme-challenge
chown acme:acme /var/www/EXAMPLE.com/htdocs/.well-known/acme-challenge sudo chown acme:acme /var/www/EXAMPLE.com/htdocs/.well-known/acme-challenge
``` ```
## nginx config ## nginx config