You share your photo albums from a Synology NAS and your QuickConnect links remain blocked on « Connection in progress... » At your clients? That was my case, and the origin was a safety choice on my part. Here's what I checked, which fixed part of the problem, and the solution I keep: my own domain name, without an intermediate server.
The symptom
I share Synology Photos albums with a QuickConnect link set in « Public ». At home, on the local network, everything opens up. In a recipient, the page remains indefinitely on « Connection in progress... », then displays a connection error to the relay server.
What I checked, no result
The classic causes are known: failure at Synology, QuickConnect disabled or disconnected account, unauthorized application, staggered clock, failed DNS, firewall or automatic blocking too strict (RocketZero). I checked everything: relays enabled, applications allowed, firewall and automatic lock, gateway and DNS, timing of the hour, logs. Nothing unusual about NAS.
The cause: a closed port for security
The starting point was a security audit. I had deleted the redirect from port 5001 to the NAS on my box, as it exposed the DSM connection page to any Internet. Right after that, QuickConnect links stopped working for outsiders.
QuickConnect first tries a direct connection. If she fails, he goes through Synology's relay. But Synology's servers believed my NAS could still be reached live on the port that I had closed: visitors were sent to a dead address.
First fix: restart QuickConnect
In DSM, Control Panel, External access, QuickConnect: Uncheck « Enable QuickConnect », apply, pick up, apply. The NAS re-registers and direct access passes in « disconnected » Synology side. It is also the gesture recommended by the help guides (RocketZero).
Why I'm not content
After this corrective, Synology's relay still refused to open the tunnel, with an error « tunnel request fail », while everything was correct on NAS. I cannot confirm the reason for this refusal. This relay is shared and its flow is limited, according to the same guide. Reopening port 5001 might have set everything up, but this would have exposed the DSM connection over the Internet. I didn't.
The solution chosen: my own domain, without intermediary
My links now start with an address of mine, type photos.monsite.fr. The encrypted connection goes directly from my NAS to the recipient's browser, without Synology server or another third in between. Only Synology Photos is exposed, not the DSM interface, and the recipient does not install anything. Here are the eight steps, in order.
- NDNS. My IP address changes from time to time; a DDNS gives a fixed name that follows it. DSM, Control Panel, External access, DDNS, Add, Synology supplier.
- Subdomain. At the host of my domain, I add a CNAME record
photoswhich points to the DDNS name (with the end point). The spread takes a few minutes to a few hours. - Synology Photos on its own domain. DSM, Connection Portal, Applications, Synology Photos, Edit: I provide a custom HTTP port and custom domain (HSTS checked). This name opens Synology Photos directly, not DSM.
- Redirect ports to the box. Two TCP rules to the NAS: 443 to 443, and 80 to 80. The 443 is the standard port of HTTPS, the link remains clean and passes on all networks; the 80 is used for Latvian Encrypt. Port 5001 remains closed.
- Certificate. DSM, Security, Certificate, Add, Let It automatically renews.
- DSM firewall. In this order: authorized local network, port 443 authorized from France, port 443 refused for all others. Port 80 remains open: it shows nothing and serves to renew the certificate.
- Links. DSM, External access, Advanced: I enter the subdomain as host name, DSM (HTTPS) on 443. I then recreate the link from the album, which starts with
https://photos.monsite.fr/mo/sharing/. - Test. On a 4G phone, Wi-Fi was cut, in private navigation: the album was opened.
Why didn't I keep the Cloudflare tunnel?
A previous version of this article described a Cloudflare tunnel, free of charge and without open port. I abandoned it: Cloudflare completes HTTPS encryption, so traffic is not encrypted from end to end. I'm not saying Cloudflare reads your photos: I can't verify it, and architecture makes it technically possible. For photos of clients that I agree to keep confidential, I prefer that no one is between you and my NAS. This is the same principle as that of Confidentiality commitment.
Honest limits
This solution is not for everyone, and it requires maintenance.
- A door remains open. Only Synology Photos is exposed, but port 443 is. Keep DSM up to date and never reopen the DSM connection on the Internet. I can't guarantee absolute security.
- The filter « France only » But he also refuses a customer located abroad. To fit your customers.
- Your network must accept incoming ports. With a strict NAT or CGNAT in the operator, direct connection is impossible and only a relay or VPN remains possible (RocketZero).
- Three items to monitor : the rules of the box, the state of the DDNS and the validity of the certificate.
If a link no longer opens: the aide-mémoire
- Check that the two rules of the box (443 and 80) are still active.
- Check that the DDNS displays « Normal ».
- Check that the certificate has not expired. If it does not renew, check that port 80 is always redirected and allowed in the firewall.
- Test in 4G the subdomain's only address: it must display the Synology Photos connection, not that of DSM.
For the method that I apply to my own customers, read the article « Share your photos after shooting: Google Photos, Dropbox or private link? » [REASON TO INSERT].
Photographer, agency or image pro: exchange
Are you professional and want to exchange links between our sites or collaborate?
Sources
Source accessed November 18, 2026. The steps described are my personal feedback.