NAS Codex › Synology › Synology Drive Client: SSL certificate of the Synology NAS is not trusted
Synology Drive Client: SSL certificate of the Synology NAS is not trusted
Synology Drive Client, Synology Drive ShareSync and the Synology Drive mobile app can show The SSL certificate of the Synology NAS is not trusted or Untrusted Connection when you connect or create a task. Synology says the warning depends on how you connect (private IP, public IP, DDNS and so on), and gives two causes: the NAS certificate was changed or has expired, or the address you used, such as an IP address, has no valid certificate.
Written against: DSM 7 (Synology KB: How can I fix common SSL issues for Synology Drive Client, Synology Drive ShareSync, and Synology Drive mobile app?; DSM 7 help: Certificate; Synology KB: Synology Drive Client connection trouble). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Synology's most recommended fix is to connect with a domain name that has a valid certificate: set up DDNS, get a Let's Encrypt certificate on the same page, set it as the default, and check in Control Panel > Security > Certificate that it is used for Synology Drive Server. Then connect Drive Client with that domain name instead of an IP address.
1. Connect with a domain name and a valid certificate
Synology calls this the most recommended method, because it uses a valid certificate and connects directly to the NAS.
- For connections from outside your network, set up port forwarding on your router: ports 5000 and 5001 for DSM (configured by default) and port 6690 for file syncing with Synology Drive.
- Set up DDNS for the NAS. On the same page, apply for a Let's Encrypt certificate and set it as the default certificate. If you already have a valid certificate, import it into the NAS instead.
- Go to Control Panel > Security > Certificate and make sure the valid certificate is the default and is used for Synology Drive Server.
- Connect with that domain name in Synology Drive Client, Synology Drive ShareSync or the Synology Drive mobile app.
2. Or connect with QuickConnect
Synology says QuickConnect can reach Synology Drive Server even on a limited network, but you may still see the untrusted SSL warning in some cases. Its steps:
- If you can, forward ports 5000 and 5001 (DSM) and 6690 (Synology Drive) on your router. Skip this if your network doesn't allow port forwarding.
- Set up DDNS, apply for a Let's Encrypt certificate on the same page, and set it as the default certificate.
- In Control Panel > Security > Certificate, make sure that certificate is the default and is used for Synology Drive Server.
- Enable QuickConnect. Under Advanced Settings, make sure Enable QuickConnect relay service and Automatically create port forwarding rules are on.
- Connect with your QuickConnect ID.
Synology notes two cases where the warning can remain with QuickConnect: on a LAN with DSM 6.2 and earlier, where you trust the connection manually; and when playing media files in the Synology Drive mobile app, where you either turn on Play media files over HTTP (More > ADVANCED SETTINGS) or download the files to the device first.
3. If you connect without a valid certificate
- Signing in with an IP address: Synology says this always triggers the warning. If you are sure the IP address is correct, you can trust the connection manually by clicking the proceed button.
- Self-signed or expired certificate: apply for a Let's Encrypt certificate and use it to replace the invalid one.
- Missing intermediate certificate: if your certificate authority provided an intermediate certificate, import it as well.
4. Check which certificate Synology Drive Server uses
The DSM 7 help explains the Certificate page. To assign certificates to services, go to Control Panel > Security > Certificate, click Settings, open the Configure tab, click the current certificate of the service, pick the right certificate from the drop-down menu, and click OK. The System Default certificate applies to any connection not on the service list. To import a certificate from a commercial or third-party certificate authority, click Add, choose Add a new certificate, then Import certificate, and follow the wizard.
The help also says that when a certificate has errors, the services registered with it become inaccessible. Its repairs: apply for a new certificate such as Let's Encrypt, import the certificate again, or change the services' certificate to a different one.
5. If Drive Client says "connection failed" instead
Synology's separate connection article lists these checks: the NAS is powered on; the network is stable; the IP address, domain name or QuickConnect ID, username and password are correct; Synology Drive Server is installed and working; port 6690 is set up on your router; and, if needed, the NAS MTU is reduced to the default 1500 or lower before trying again.
When to stop and get help
Synology says to note the certificate's expiration date and always renew it before it expires; otherwise every connection that uses the certificate is affected. The DSM 7 help adds that resetting certificates returns the NAS to the default Synology certificate and deletes all other certificates.
Questions
Why does Synology Drive Client say the SSL certificate is not trusted?
Synology says the NAS certificate changed or expired, or the address you connect with, such as an IP address, has no valid certificate.
How do I stop the untrusted connection warning in Synology Drive?
Connect with a domain name that has a valid certificate: set up DDNS and a Let's Encrypt certificate, set it as default, and make sure Synology Drive Server uses it.
Which ports does Synology Drive Client need?
Synology lists ports 5000 and 5001 for DSM and port 6690 for file syncing with Synology Drive when you connect from outside your network.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.