From a77a457b8c805f1148c2759c1285b661f1f5f60a Mon Sep 17 00:00:00 2001
From: nic <31355096+nabbi@users.noreply.github.com>
Date: Thu, 9 Jun 2022 20:30:44 -0500
Subject: [PATCH] more clarificaions on which cmd is root

---
 sudo.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/sudo.md b/sudo.md
index b5ec442..904e811 100644
--- a/sudo.md
+++ b/sudo.md
@@ -45,7 +45,7 @@ sudo su - -s /bin/bash acme
 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
 ```
@@ -53,8 +53,8 @@ Adjust path to your acme.sh installation script
 ## 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?
 ```
-mkdir -p /var/www/EXAMPLE.COM/htdocs/.well-known/acme-challenge
-chown acme:acme /var/www/EXAMPLE.com/htdocs/.well-known/acme-challenge
+sudo mkdir -p /var/www/EXAMPLE.COM/htdocs/.well-known/acme-challenge
+sudo chown acme:acme /var/www/EXAMPLE.com/htdocs/.well-known/acme-challenge
 ```
 
 ## nginx config