ADM’s built-in Let’s Encrypt support only offers HTTP challenge, which means opening port 80 to the internet. If, like me, you’d rather keep your NAS off the internet entirely, or you want a certificate for a hostname that only exists on your LAN, using DNS-01 challenge gets around this: Let’s Encrypt checks a temporary DNS record instead of connecting directly to the NAS.
There are a few older guides around for doing this with Cloudflare amongst others, and outdated ADM versions. My DNS is hosted in AWS Route 53, so I’ve put together a version for that, tested and currently running on ADM 5.
What it does
- Installs certbot with the Route 53 plugin in a Python virtual env on
/volume1, so it survives reboots - Issues a certificate for your NAS hostname without opening any ports
- Installs it into ADM’s web interface and restarts the web server automatically
- Renews daily via cron (only when the cert is close to expiry), redeploying it each time
- Uses a least-privilege AWS IAM policy: the key can only create and remove the
_acme-challengeTXT record for your hostname, nothing else in your domain
Requirements
- Domain hosted in an AWS Route 53 public hosted zone
- Python3 installed from App Central
- SSH access (Services → Terminal)
- A hostname that resolves to the NAS on your LAN (e.g. local DNS/router entry)
Full step-by-step instructions, troubleshooting and how to revert are all in the README.
One ADM 5 gotcha worth knowing
Even if you don’t use this project: on ADM 5 it appears that the web server reads its intermediate certificate from a separate file, /usr/builtin/etc/certificate/ssl.chain. The default Asustor certificate doesn’t have one, so the file doesn’t exist. If you install a CA-issued certificate by hand without creating it, the browser shows your certificate but could still say “Not secure”, because the certification chain is incomplete. The deploy hook in the repo script handles this, but anyone installing certificates manually may hit the same thing.
Tested on
AS6706T with ADM 5.1.4. Other ADM 5 models should use the same file layout, but I’d welcome reports either way.
This uses SSH as root and changes system files ADM doesn’t expect you to touch. It backs up the original certificate first and the README explains how to revert, but please back up everything important before you start. Unofficial community project, not affiliated with ASUSTOR or AWS.
Feedback and issue reports welcome on GitHub.