github
/
acme.sh
mirror of https://github.com/acmesh-official/acme.sh
1
0
Fork 0
Code Issues Releases Wiki Activity
Synology NAS Guide
Simmo Saan edited this page 2025-07-22 23:59:54 +03:00

Wiki Page Revisions

92 Commits

Author SHA1 Message Date
Simmo Saan d23fde8938 Updated Synology NAS Guide (markdown) 2025-07-22 23:59:54 +03:00
cospeedster 2d5b103189 Add chapter for enabling auto upgrading of acme.sh 2025-05-05 22:46:27 +02:00
cospeedster 00e067e88c Specify ec key length 2025-05-05 22:39:35 +02:00
cospeedster d94cd901c8 Use ecc instead of 2048 bit rsa in synology nas guide 2025-05-05 22:30:03 +02:00
Artur Klauser e16696dbf7 Fixing typo 2025-02-19 17:30:39 -08:00
Artur Klauser 277fb13066 Fixing grammar 2025-02-19 17:21:05 -08:00
Artur Klauser d171fb86af Fixing typo 2025-02-19 17:13:09 -08:00
cloudlessa 9e863a0186 Updated Synology NAS Guide (markdown) 2025-01-05 01:42:32 +08:00
XDigital 0d7980099f Let's Encrypt recently switched their default to ECDSA instead of RSA; Synology only accepts RSA, so adding --keylength 2048 to obtain RCA certificate 2024-08-07 15:34:44 +07:00
57194 60c2dfd480 Task Scheduler has to be told where the acme.sh file and path are. 2024-08-04 18:32:56 +00:00
jaku2019 97dd8e2f9b correct $./acme.sh to ./acme.sh in copy command section 2024-06-05 01:16:51 +02:00
Scruel Tao b6d1e91a4a Updated Synology NAS Guide (markdown) 2024-04-25 15:29:29 +08:00
Scruel Tao a5af16d1da Updated Synology NAS Guide (markdown) 2024-04-21 16:14:01 +08:00
Lluís D 6fa9366acf Updated Synology NAS Guide (markdown) 2024-03-19 13:16:57 +01:00
Scruel Tao 93b0faaae1 Updated Synology NAS Guide (markdown) 2024-03-01 15:17:53 +08:00
Scruel Tao 0612774bc8 Updated Synology NAS Guide (markdown) 2024-03-01 15:17:32 +08:00
Scruel Tao 59b9a726b6 Updated Synology NAS Guide (markdown) 2024-03-01 15:16:54 +08:00
Scruel Tao 4288288b6b Updated Synology NAS Guide (markdown) 2024-02-28 16:40:25 +08:00
Scruel Tao 73163fe584 pre-modify 2024-02-28 15:34:03 +08:00
François Dexemple 8b9464b6f3 Fix Typo 2024-02-26 22:51:37 +01:00
Scruel Tao 3991cce921 Updated Synology NAS Guide (markdown) 2024-02-26 06:44:43 +08:00
Scruel Tao 1730640ceb Updated Synology NAS Guide (markdown) 2024-02-22 19:47:56 +08:00
Scruel Tao 9627dcc536 Updated Synology NAS Guide (markdown) 2024-02-22 19:47:40 +08:00
Scruel Tao 8f1fa7725e Updated Synology NAS Guide (markdown) 2024-02-22 19:24:29 +08:00
Scruel Tao 0f8a738c7e Updated Synology NAS Guide (markdown) 2024-02-22 19:23:00 +08:00
Scruel Tao 6559fc025f Updated Synology NAS Guide (markdown) 2024-02-22 19:22:21 +08:00
brandonjp f26524f15d link to the DNS API wiki for a little added convenience 2023-10-17 10:27:37 -05:00
Chris Nesbitt-Smith fa83cd77f6 Updated Synology NAS Guide (markdown) 2023-09-25 21:30:20 +01:00
Chris Nesbitt-Smith 3422765c68 Updated Synology NAS Guide (markdown) 2023-09-25 21:29:49 +01:00
Chris Nesbitt-Smith 975a06bdef Updated Synology NAS Guide (markdown) 2023-09-25 21:28:56 +01:00
Julian Qian 8e24417dd1 Acme.sh is updating their defaults to use zerossl instead of letsencrypt [0]. This has resulted in errors like: Can not resolve _eab_id When our runs of acme.sh attempt to communicate with zerossl. While the default change isn't supposed to happen until August 1 we hit it early because we consume the dev branch of acme.sh. We avoid this entirely by being explicit about the server to communicate to in our acme.sh driver script. We explicitly set --server to letsencrypt. https://opendev.org/opendev/system-config/commit/3d5d2779d284af52c23af69ae4fc1a99e7ecdcbc?style=unified&whitespace= 2023-06-29 11:10:17 +08:00
Brandon Williams cea5a54335 Fixed example using `--insecure` 2021-11-13 05:48:18 -06:00
Brian Hartvigsen a446b572de Add additional details per @dibas in #2727 2021-01-19 16:39:06 -07:00
adjager1 f42297f105 mention missing curl http2 dependencies 2020-10-27 09:44:06 +01:00
adjager1 15d659df7a mention --insecure in combination with "localhost" only 2020-10-27 09:08:31 +01:00
adjager1 88e02acec8 mention --insecure option in command to prevent curl error on https deployment 2020-10-26 22:01:05 +01:00
Matthijs Langenberg 505cb3f163 Specify `--home` for issue and deploy steps in order to prevent certs being placed in the default `/root/.acme.sh` location (and thus wiped after a DSM update). 2020-09-07 13:53:15 +02:00
Martin Arndt 180587e35f Fixed 2FA issue help (logins with 2FA enabled _are_ possible!) 2020-06-25 17:16:19 +02:00
Miguel Angelo b3b50c8f2e Added info about user login error when the user has 2fa auth enabled. 2020-06-23 17:45:05 -03:00
Dave Hall 7dd7ba03f8 Update GitHub org references 2020-06-07 00:38:26 +10:00
Brian Hartvigsen 06e372b1ce Confirmed all instructions to work if followed step by step 2020-05-22 12:43:28 -06:00
Brian Hartvigsen 02f265855a Use `sudo su` instead of `sudo -i` 2020-05-22 12:36:45 -06:00
Brian Hartvigsen 9e12b41e80 Switch to using the synology dsm deployhook as it should be easier for people to use 2020-05-16 01:57:21 -06:00
bosr 114ac9ab88 Avoid creating a temp directory that starts with a digit, as it breaks several of the `jq -r` commands in `reload-certs.sh`. I discovered that by accident, and it took me quite some time ;) 2020-03-28 14:41:29 +01:00
thermionic ddbfc83c47 changed wget from "-o" to "-O". "-o" is output file for logging, "-O" is output file 2020-03-23 16:19:53 +00:00
bartowl db6b18e200 fixed the download path for the script and added missing cd 2020-03-10 14:57:17 +01:00
bartowl d771d9d123 I have figured out how Synology redistributes certificates to all packages and services and wrote a script to reload only those services, where certificates were changed. It does this in very same way as Synology when refreshing/importing new certificate, so no more need to figure out how to reload affected services. It also perfectly integrates with synology certificate management. As it is to be used directly from --reloadcmd there is no need for such extensive scheduler renewal script. 2020-03-10 14:50:28 +01:00
Rin 8659336120 https://github.com/Neilpang/acme.sh/wiki/sudo 2019-11-14 14:58:21 +09:00
Eric Hutchinson e8dff1e1c6 Took me forever to figure out that i was using a token key, and it wasn't the same as the global account key. 2019-10-27 10:39:43 -07:00
florid2 bb9b667b18 Update CF API key URL 2019-03-26 14:49:24 +11:00