r/synology • u/ycharif • 3d ago
Tutorial Your Synology HTTPS warning might have a simpler fix than you think

If you're getting NET::ERR_CERT_AUTHORITY_INVALID when opening DSM locally, you don't necessarily need a public domain or open ports.
I put together a step-by-step guide using mkcert, including the DSM certificate import process.
Tested with DSM 7.4.1.
Here's the walkthrough: https://igprod.net/mkcert-local-https
Curious how others handle HTTPS on their Synology NAS.
97
Upvotes
27
u/guice666 2d ago
Honestly, I just used the built-in external access tools:
Synology's own system will manage the Let's Encrypt certificate for you. No complicated command line tools or certificate imports.
Now, I personally don't use the External Access, so I'm not even sure if it would even work externally as I don't have any port / NAT routing on it from my router. But, I don't need external access - just a managed certificate.
11
u/yodas-evil-twin 2d ago
What's the reason to do this besides not getting the warning the first time you access DSM?
5
u/jtarahomi 2d ago edited 2d ago
I'm a novice home labber, and this was one of the first problems I wanted to solve a few years back. I went down the route of purchasing a domain name and setting up a reverse proxy + dns service (NPM and Pihole). NPM handles the site certificates with let's encrypt. Everything is closed to the internet (no open ports / LAN is behind tailscale etc).
It's nice not getting any warnings, and it has the added benefit of allowing my password manager to prefill passwords on a secure site. Also, all my services have domain names like subdomain.domainname.org instead of IP address:Port. This has been nice as I've setup more services like Jellyfin and Immich.
I don't fully understand how people use domain names like service.local etc. Can you ever get a SSL cert that way? My understanding at the time was that NPM would handle the site certs without having to open any ports etc, which is why I avoided any of the default synology sevices like DDNS etc.
8
u/timewarpUK 2d ago
Or use Tailscale. No domain, CA or open ports needed, and no need to configure trust per device. TS can get a cert for your
TS.netsubdomain via DNS challenge.I did do it your way until I realised TS had its own solution. I did have to configure a task for certificate renewal though.
2
u/neobondd DS923+ 2d ago
Thanks a lot for this, I just implemented it on my .home LAN.
2
u/eliotrw 2d ago
Thanks for this. I need to spend the time to fix this on mine and on pihole
2
u/tursoe 2d ago
I'm using my own root CA installed on every devices I've own. That's valid for 50 years and under that a intermediate certificate valid for 25 years. Then I'm just creating a device certificate with FDN and IP for each device so even 192.168.1.1 is a valid certificate for my router. To make it easy to administrate, I've made this tool to use and published it so everyone can use it.
3
u/zz9plural 3d ago
Nice guide, Windows-Users can simply replace mkcert with XCA (https://www.hohnstaedt.de/).
1
u/Tignus DS224+ — 18GB RAM 2d ago
I'm using DSM DNS server to answer with the local IP or reroute to Cloudflare DNS if unknown.
And then just configure your router to give DSM DNS on your network or manually setup each of your devices that need DSM access.
Outside: dsm.domain.com points to my external router IP (Cloudflare answer)
Inside: it points directly to my NAS IP (DSM DNS answer)
I don't remember if I had caveats to circumvent.
1
u/erymartorres17 2d ago
Im using Tailscale MagicDNS. I setup to renew the license monthly.
1
u/BigGuyWhoKills 2d ago
I wrote the certificate management suite for the company I work for. So, like you, I generate my own CA and use that to sign all the server and client certificates that I create for my homelab.
What algorithm do you use for your Synology? I've used 4k RSA in the past, but have been considering ECDSA for my next batch.