I have the computer with the files setup as send only and the NAS receive only. I have enabled UPNP and verified the NAS has open the ports but everything is showing disconnected. The computer side does not have ports opened in the firewall. Do I need to open the ports on that side as well?
Here is a link to the documentation area that you’re looking for, I think:
The PC isn’t required to open any inbound ports as long as the other device it’s connecting to has its ports open (some firewalls block both inbound and outbound by default, so it’s best to double check).
The downside to the PC not having inbound ports open is that Syncthing won’t receive any of the local discovery broadcasts from the NAS. It’s up to the NAS to “hear” the PC trying to connect to it via local discovery, or for the two to find each other via global discovery.
Is there anyway to for the NAS to look again? I recently moved the NAS from my office to my house. Its been disconnected since I powered it on 3 days or so ago. I run everything so the outbound ports arent blocked at my office, and I have upnp enabled on my firewall at home for the nas.
This is what the nas requested upnp
Update: I just manually entered my public ip and the upnp port tcp://publicip:12539 and it connected. Not sure what the autodiscovery not work but at least its syncing.
This picture of Services:UPNP, is that being done on your NAS admin tool, or the router interface, or?
Where exactly did you enter the public ip and tcp://publicip:12539? Was that somewhere in syncthing? I’m guessing that server B was configured so the remote, A is located at tcp://publicip:12539?
Many routers today do UPNP automatically without having to set this up. I know nothing about dedicated NAS servers. I have an ASUS router and Syncthing does take advantage of upnp.
My understading is that Global Discovery and Relay servers would make it unnecessary to change the router.
Would you mind posting Syncthing’s log from both the NAS and PC? (preferably first 15 seconds or so after Syncthing starts)
So, based on the log snippets, there are a couple of different problems…
First, Syncthing on the PC and NAS are on different LANs:
2023-08-22 13:44:56 Device Removed client is "syncthing v1.23.7" named "Removed" at 10.38.0.5:22000-RemovedIP:12539/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30
2023-08-26 07:28:51 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp: lookup relays.syncthing.net on 192.168.1.1:53: read udp 192.168.1.147:42663->192.168.1.1:53: i/o timeout
The PC’s IP address is 10.38.0.5 while the NAS is 192.168.1.147. For that to work, the two LANs would have to be bridged.
The second problem is that Syncthing on the NAS is timing out while attempting a DNS lookup.
Is Syncthing on the NAS running in a Docker container?
On a somewhat related note, how are the hardware specs on the PC and NAS? They both have comparatively low hashing speeds (< 70 MB/s), so syncing lots of files or a smaller number of large files could be slow.
The PC’s IP address is 10.38.0.5 while the NAS is 192.168.1.147. For that to work, the two LANs would have to be bridged. Will syncthing not find each other over the internet like resillio? That’s what was using previously. The NAS is at my house and the PC is at my office. I have a google DNS name setup with a dynamic DNS updater so I can continue to just set the address that way
Is Syncthing on the NAS running in a Docker container? Running on a synology nas installed from the app installer.
On a somewhat related note, how are the hardware specs on the PC and NAS? They both have comparatively low hashing speeds (< 70 MB/s), so syncing lots of files or a smaller number of large files could be slow. The NAS is DS415+ so its littler older and the PC is a on VM inside a ESXI server with some older DDR3 era hardware.
Ah, I’d assumed that the PC was at home while the NAS was previously at the office…
Because the PC has most (if not all) ports closed, it’s up to the NAS to receive the connection requests from the PC. Local discovery can’t be used because the PC and the NAS aren’t together on a LAN (could set up a VPN, but that’s for a different discussion).
Syncthing doesn’t require that either the PC or the NAS have static IP addresses or fully-qualified domain names (FQDN). As long as global discovery is enabled in Syncthing, they’ll look each other up via one or more Syncthing discovery servers.
But, the NAS has a problem with its DNS setup, so it can’t resolve any of the domain names of the Syncthing discovery and relay servers. As long as the NAS can’t reach a Syncthing discovery server, the PC look it up, so you have to manually enter the IP address for the NAS on the PC side.
Okay, then it’s most likely a Docker container.
Ah, that explains the slower hashing speeds…
The quad-core Intel Atom C2538 supports AES-NI, but the single-threaded performance is pretty low.
There are a lot of tuning options for optimizing VMs to reduce the typical 20% or more performance hit versus running bare-metal on the same hardware.
One obvious way for installing Syncthing on a Synology is from the package provided by SynoCommunity. That is NOT using Docker. And I doubt a DS415 has Docker available, as it’s quite old.
What “app installer” are you referring to? Did you add the SynoCommunity repository? Probably not related to the cause of your troubles, but just to help us understand what should work.
Yup, that was also my first thought.
But while downloading the spec sheet for the DS415+, I noticed that DSM 7.x had been released for it. And given the number of posts on the forum asking about Docker on a Synology, it seemed to be a reasonable possibility.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.