From b68834b6a2146a0956f777cd84206184264496aa Mon Sep 17 00:00:00 2001
From: muibusan <16862260+muibusan@users.noreply.github.com>
Date: Sun, 6 Aug 2023 13:03:50 +0200
Subject: [PATCH] removed --resume flag for caddy

---
 ...a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md b/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md
index a93885e..f36150d 100644
--- a/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md
+++ b/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md
@@ -64,11 +64,9 @@ You should now be able to reach your vaultwarden instance at https://my-vw.duckd
 
 You can stop caddy by [STRG]-[C]. In the future start caddy in the background by running
 ```
-caddy start --envfile caddy.env --resume
+caddy start --envfile caddy.env
 ```
 
-The `--resume` parameter makes it load the latest configuration saved saved in `/root/.config/caddy`.
-
 **Important:** If necessary, in some routers (e.g. FritzBox) or DNS resolvers (e.g. unbound) an exception must be set for the domain (e.g., `my-vw.duckdns.org`) due to DNS rebind protection.
 
 ## Cloudflare setup