I replaced my 4 bay QNAP with a 4 bay Synology and moved to QNAP to my son’s home 6 miles away. I intended to use HyperBackup via Tailscale to backup my Synology to the QNAP. With both machines on my home LAN, I successfully backed up the Synology to the QNAP using HyperBackup via the QNAP’s Tailscale ip address. However, after moving the QNAP to my son’s home, the backup failed with the message “No response from the destination server.” I have tried every suggestion I could find from several Google searches, but I still cannot get past the “No Response”.
I have no trouble logging onto the QNAP over Tailscale via http or SSH, or mounting a QNAP share on my home Mac. Indeed, by mounting both QNAP and Synology shares to my Mac, I can manually copy files from the Synology to the QNAP via the Mac. However HyperBackup stubbornly refuses to work. Any suggestions would be greatly appreciated.
In Hyper Backup, select the task, go to the Target tab, and check if the Tailscale address is there.
What protocol (rsync?) and port are you using (see the same tab)?
On the Synology the Tailscale (Tailnet) ip is set to the correct one. Other settings are: Backing up “Folders and Packages” to an “rsync” file server; Backup Version Type is “single version”; Server Type is “rsync-compatible server”; Transfer encryption “off”; Port “873”; user name and password is correct. On the QNAP: HBS3 is set to “Rsync Server”, “Shared rsync server” account with the correct user name and password, and port 873.
When I click on the 'Backup module" section of Backup Destination Settings in HyperBackup, I get the “No response from the destination server” box. When both NASs were on my home LAN this box connected just fine using the exact same setting on the Synology and QNAP, including using the same Tailnet ip address. At this point I’m baffled.
It is really strange that you could back up when the backup NAS was connected to your home LAN via tailnet, but not when it is remote.
I recently created a similar setup for a client, and it worked after the backup NAS was moved to the remote location. I just checked, and it still works.
I have a similar setup with a NAS at home and a remote backup NAS at my son’s house, using DDNS and port forwarding. Fortunately, I recently installed Tailscale at both NASs. I decided to test the backup and discovered I got the same error as you.
I tried all the variables I could think of, including switching off the firewall, but nothing helped.
Just opened a new topic with very similar problem, working link via Tailscale broke and it won’t connect to my remote DS220+ from my DS1522+. worked fine locally and then for a month + over Tailscale but after 1522 was restarted, can’t get them to connect. Tailscale IP OK, Ports OK, Similar but not identical, but following this, TY.
I had success over Tailscale with my office 1522+ to old/replaced from office home 220+. Initial hyper-backup task and connection locally. Moved 220+ to my house and it was fine - ran great for 30+ days. Had to restart the 1522 and can’t get it to reestablish connection and driving me crazy. I need this easy, paid, data owned for offsite back up to work. I think I have mine narrowed down to the pass/fail authentication that changes from green pass to red fail on the Target tab on its own and seems to cause that error message.
The issue you’re encountering with the “No response from the destination server” error in HyperBackup, despite both NAS devices being connected via Tailscale, is likely due to one or more of the following reasons. Let’s break it down step by step:
1. Tailscale Connectivity Issues
Check Tailscale Status: Ensure both the Synology and QNAP devices are properly connected to the same Tailscale network (Tailnet). You can verify this by logging into the Tailscale admin console or using the tailscale status command on each device.
Ping Test: From the Synology NAS, try pinging the QNAP’s Tailscale IP address. If the ping fails, there might be a Tailscale connectivity issue.
Use the Synology’s terminal (via SSH) and run:
bash
Copy
ping <QNAP_Tailscale_IP>
Subnet Routing: If the QNAP is on a different subnet, ensure that subnet routing is enabled in Tailscale and properly configured.
2. Rsync Server Configuration on QNAP
Rsync Service Status: Verify that the Rsync server is running on the QNAP. Go to the QNAP’s HBS3 app and ensure the Rsync server is enabled and listening on port 873.
Firewall Rules: Check the QNAP’s firewall settings to ensure that port 873 is open for the Tailscale IP range. Tailscale uses its own virtual network, so the firewall must allow traffic from Tailscale IPs.
Shared Folder Permissions: Ensure the shared folder you’re backing up to on the QNAP has the correct permissions for the Rsync user.
3. HyperBackup Configuration on Synology
Rsync Transfer Encryption: Since you mentioned “Transfer encryption” is set to “off,” ensure this matches the QNAP’s Rsync server settings. If the QNAP requires encryption, you’ll need to enable it in HyperBackup.
Port Configuration: Double-check that port 873 is correctly specified in both HyperBackup and the QNAP’s Rsync server settings.
Tailscale IP Address: Ensure the Tailscale IP address of the QNAP is correctly entered in HyperBackup’s backup destination settings.
4. Network-Specific Issues
MTU Size: Tailscale uses a virtual network interface with a lower MTU (usually 1280 bytes). If your NAS devices are experiencing packet fragmentation, it could cause connectivity issues. You can try lowering the MTU on the Synology and QNAP:
On Synology (via SSH):
bash
Copy
sudo ip link set tailscale0 mtu 1280
On QNAP (via SSH):
bash
Copy
sudo ip link set tailscale0 mtu 1280
NAT Traversal: If either NAS is behind a restrictive NAT or firewall, Tailscale might have trouble establishing a direct connection. Check the Tailscale admin console to see if the connection is “direct” or “relayed.” A relayed connection might cause performance issues or timeouts.
5. Debugging Steps
Test Rsync Manually: Use the Synology’s terminal to test the Rsync connection manually. This can help isolate whether the issue is with HyperBackup or the Rsync server itself.
Still no luck with the Synology → QNAP rsync over Tailscale. There is no response from the QNAP, and the connection times out, regardless of whether I rsync from Hyperbackup or rsync from the Synology terminal. What is more puzzling is that I can rsync files, directories, and subdirectories from my desktop Mac to the QNAP just fine over Tailscale. The only quirk is that ssh must be enabled on the QNAP for that rsync to work. No joy from the Synology even with ssh enabled on the QNAP. At this point I’m thinking the problem is with the Synology not sending the correct info to the QNAP or perhaps blocking the outbound connection.
I think you are going about it incorrectly. Forgive me if you already know this, or have checked out this whole bit, but I just wanted to make sure.
If everything works locally, I doubt the problem is with the configuration (mostly).
Forgive me if I missed this part, but what IP is the Tailscale in the configuration? I would imagine it needs to be the Public IP address of the QNAP. Otherwise, the Synology will continue to look for the QNAP internal to your house. It cannot be your son’s remote internal IP because that traffic will not find its way out of his network.
I don’t know what Tailscale is exactly, but as I see it the next problem is that the PUBLIC IP of the QNAP end (your son’s firewall/router) is most likely going to change from time to time and that is going to break the config periodically, even if we fix this. So, you will need to find a solution to this like DynDNS or something.
So, we correct the NetBackup configuration with the PUBLIC IP of the son’s firewall/router. Next you will need to make sure that YOUR firewall allows that traffic to be sent to your son’s house… if it is rsync, rsync needs to be allowed to son’s PUBLIC IP from your NETBACKUP.
Firstly at the son’s house, you need to make sure the QNAP talks on HIS network. It could be a different network or another device might have the same IP there. If all this is good, you need to make sure that rsync is allowed from his router/firewall to YOUR PUBLIC IP address (which will also change from time to time) from the QNAP.
Once all this is setup, you can look into authentication issues and such.
Sorry, I was looking this and sending from my phone and I may have missed some bits.
Please ignore some of my duplicate advise.
Possible bad advise to follow, but you can always open all ports from your Synology end firewall/router to your son’s IP and see if that gets it working. Then you would be able to verfiy that you are somehow blocking whatever port it needs.
Just remember to take that rule out after testing.
