From f3ba8d3559f83ed56fa752790577b63a9066fb25 Mon Sep 17 00:00:00 2001
From: Ross Shen <sjtuross@users.noreply.github.com>
Date: Thu, 10 Mar 2022 22:42:41 +0800
Subject: [PATCH] Updated deployhooks (markdown)

---
 deployhooks.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deployhooks.md b/deployhooks.md
index 2fe4b08..5c7cc91 100644
--- a/deployhooks.md
+++ b/deployhooks.md
@@ -599,7 +599,7 @@ acme.sh --deploy -d example.com --deploy-hook synology_dsm
 When using https to connect to "localhost" we need to add the --insecure option to the deploy command. refer to [https://github.com/acmesh-official/acme.sh/wiki/Options-and-Params]. If you enabled HTTP/2 you still receive a curl 16 error but the script succeeds.
 
 ```sh
-acme.sh --insecure --deploy -d example.com --deploy-hook synology_dsm
+acme.sh --deploy --insecure -d example.com --deploy-hook synology_dsm
 ```
 
 Certificate should now show up in "Control Panel" -> "Security" -> "Certificates" and can be assigned to Services or set as the default certificate.