Skip to content

History / Synology NAS Guide

Revisions

  • Let's Encrypt recently switched their default to ECDSA instead of RSA; Synology only accepts RSA, so adding --keylength 2048 to obtain RCA certificate

    @xd1gital xd1gital committed Aug 7, 2024
  • Task Scheduler has to be told where the acme.sh file and path are.

    @57194 57194 committed Aug 4, 2024
  • correct $./acme.sh to ./acme.sh in copy command section

    @jaku2019 jaku2019 committed Jun 4, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Apr 25, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Apr 21, 2024
  • Updated Synology NAS Guide (markdown)

    @lluisd lluisd committed Mar 19, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Mar 1, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Mar 1, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Mar 1, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 28, 2024
  • pre-modify

    @scruel scruel committed Feb 28, 2024
  • Fix Typo

    @filol filol committed Feb 26, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 25, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 22, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 22, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 22, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 22, 2024
  • Updated Synology NAS Guide (markdown)

    @scruel scruel committed Feb 22, 2024
  • link to the DNS API wiki for a little added convenience

    @brandonjp brandonjp committed Oct 17, 2023
  • Updated Synology NAS Guide (markdown)

    @chrisns chrisns committed Sep 25, 2023
  • Updated Synology NAS Guide (markdown)

    @chrisns chrisns committed Sep 25, 2023
  • Updated Synology NAS Guide (markdown)

    @chrisns chrisns committed Sep 25, 2023
  • 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=

    @qxj qxj committed Jun 29, 2023
  • Fixed example using `--insecure`

    @rocketeerbkw rocketeerbkw committed Nov 13, 2021
  • Add additional details per @dibas in #2727

    @tresni tresni committed Jan 19, 2021
  • mention missing curl http2 dependencies

    @adjager1 adjager1 committed Oct 27, 2020
  • mention --insecure in combination with "localhost" only

    @adjager1 adjager1 committed Oct 27, 2020
  • mention --insecure option in command to prevent curl error on https deployment

    @adjager1 adjager1 committed Oct 26, 2020
  • 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).

    @mlangenberg mlangenberg committed Sep 7, 2020
  • Fixed 2FA issue help (logins with 2FA enabled _are_ possible!)

    @Eagle3386 Eagle3386 committed Jun 25, 2020