I have installed Syncthing ( v0.14.35, Linux (64 bit) ) in a jail through the plug-in interface in FreeNAS and it is failing to recognize other devices trying to connect to it. I figured this issue probably had to do with the jail so I installed Ubuntu Sever in a Beehyve VM inside of the same FreeNAS and then installed Syncthing ( v0.14.35, Linux (64 bit) ) in that and got the same issue except the Ubuntu VM could connect to the FreeNAS Syncthing plug-in jail. This obviously is not a Syncthing having issues but instead I’ve probably just mis configured FreeNAS networking, I’ve been stuck on this for a few days and I don’t know what to do other than just setup an independent system and I do not want to do that… If you need more information about my setup let me know, I didn’t know what would help and didn’t want to bog down the post.
Thanks in advance!
The UI on all sides shows addresses discovered for each device (even if they are not connected). That’s probably the best starting point, to see if those addresses are pingable from other locations.
When I click on Discovery: 5/8 the following
`global@https//discovery-v6-2.syncthing.net/v2/: Post https//discovery-v6-2.syncthing.net/v2/: dial tcp [2604:a880:800:10::182:a001]:443: connect: network is unreachable
global@https//discovery-v6-3.syncthing.net/v2/: Post https//discovery-v6-3.syncthing.net/v2/: dial tcp [2400:6180:0:d0::d9:d001]:443: connect: network is unreachable
global@https//discovery-v6-4.syncthing.net/v2/: Post https//discovery-v6-4.syncthing.net/v2/: dial tcp [2a03:b0c0:0:1010::4ed:3001]:443: connect: network is unreachable`
I don’t have IPv6 connectivity.
Also no Address has been discovered for the device yet, it just say “dynamic” and still has the first 6 characters of the device ID as the name of the device.
I apologize if I didn’t answer your question, I’m pretty new to all this and really appreciate your help!
Also, I removed the colons out of the URLs because it wouldn’t let me post more than one link.
The v6 discovery failure is expected if you don’t have connectivity. Are the addresses blank on the other side?
Did you add A on B and B on A? Are you sure the device IDs are correct?
Addresses are blank on both sides. I added B on A (A was already added to B) and nothing has happened. The IDs are definitely correct.
Addresses should say dynamic in the device editor modal.
They do, when I said they were blank I meant they don’t have any IPs in them.
Well if discovery is showing more than 2 successful discovery services on both sides, then the device IDs must be wrong.
Running with STTRACE=connections env var might show more debug info in the log, such as connection attempts.
The output of that didn’t show anything too alarming as far as I could tell. Here is a link to the logs though: https://pastebin.com/EpwMfAqv
Yeah it looks like it just doesn’t get any discovery result for the redacted device ID. Is it the same on the other side?
STTRACE=discovery may give some further info, if there is a problem with announcing for whatever reason.
Still nothing blatant that I saw https://pastebin.com/CVBFV6H5. I don’t think this is a Syncthing issue but rather FreeNAS being misconfigured…
That one is more interesting, but I’m not sure if it’s due to you cutting it up or not. Specifically, we see:
INFO: My ID: REDACTED-...-EI4WHAT
INFO: Device REDACTED-...-EI4WHAT is "ThunderServer" at [dynamic]
DEBUG: discover: Received local announcement from 10.0.4.105:30035
- This log is from EI4WHAT
- It knows about itself, but it doesn’t seem like you’ve added any other devices to the config
- It sees local discovery announcement from Y2N2DAS
Is Y2N2DAS your other device? Have you just forgotten to add it? Is the IP correct (FreeNAS does funny business with jails)? (The port is for the UDP announcement so won’t match the sync port; that’s fine.)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.