From 92c92528c7355a6e511672c414b6e6d4d889fc5c Mon Sep 17 00:00:00 2001 From: Scruel Tao Date: Thu, 22 Feb 2024 19:01:15 +0800 Subject: [PATCH] Updated deployhooks (markdown) --- deployhooks.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/deployhooks.md b/deployhooks.md index 7973ae9..2d0da21 100644 --- a/deployhooks.md +++ b/deployhooks.md @@ -638,7 +638,14 @@ The default device name is `CertRenewal`, you can select another name as your ow ### Additional optional parameters It's recommended to set `SYNO_Scheme` to `https`, `SYNO_Port` to `5001` and `SYNO_Hostname` to your actual DSM's domain (e.g., `nas.example.com`) instead of the defaults. Which increased security by TLS-based connection. -However, using `https` & `localhost` requires addition of the [`--insecure` command line argument](https://github.com/acmesh-official/acme.sh/wiki/Options-and-Params) to successfully deploy the certificate to DSM. Though, enabling HTTP/2 still might give you a `curl 16 error` warning, although the script succeeded anyways. + +However, using `https` & `localhost` requires addition of the [`--insecure` command line argument](https://github.com/acmesh-official/acme.sh/wiki/Options-and-Params) to successfully deploy the certificate to DSM: +```sh +acme.sh --deploy --insecure --deploy-hook synology_dsm -d example.com +``` + +Though, enabling HTTP/2 still might give you a `curl 16 error` warning, although the script succeeded anyways. + When issuing a certificate (e.g., Let's Encrypt) for the first time instead of renewing it, `export SYNO_Create=1` must be executed _once_.