Hi

I need to sync (one way) couple TBs to another pc. Both locations are on USB and they are not really that fast computers. It will take over a day (minimum) to hash the files on the main node. I also made a mistake of changing settings that required restart and Syncthing did not resume the scanning (it was half way)

Is it possible to increase the speed of hashing/scanning? This is going to be a send only sync so I do not need precise sync conditions. It will just mirror , I do not see me needing secure hashing on the node, I hope it makes sense.

3 posts - 2 participants

Read full topic

We are getting network not allowed on the gui - I noticed a few things - we do not have the allowedNetworks defined (but the default config does not either). Also the config documentation does not show this as an array of String(which I assume it is) it shows a simple String object but when I use the api - it returns an empty array (even if it is not defined in the config - which I assume is the proper type)

30 posts - 2 participants

Read full topic

One of my machines in a syncthing shared folder seems to have gotten an automatic upgrade, but is unable to start syncthing anymore. The log shows that it’s “checking db due to upgrade”… and while it’s understandable that it may take a while, it doesn’t make sense that it’s taking days.

Also, task manager in Windows doesn’t report any disk or CPU activity from the syncthing process, leading me to believe that it’s stuck somehow

I am using syncthing under SyncTrayzor. The syncthing version is 1.6.1. Based on the logs the previous version was 1.5.0

I’m mostly wondering if I can safely delete the database file and have syncthing regenerate, or if it is risky. If I understand correctly, the database file only holds a cache of file indexes and things like that, right?

2 posts - 2 participants

Read full topic

ST won’t launch (ubuntu 18.04.4):

...
[SHORT] 13:45:08 WARNING: Database shema: device present in global list but missing as device/fileinfo entry
...
[monitor] 13:45:09 WARNING: 4 restarts in 10.776522s; not retrying further

Any idea please ? Thanks

3 posts - 2 participants

Read full topic

I just installed Kali Linux on my laptop and fired up Syncthing, installed from the apt repo. Everything works fine except for one thing. Roughly every 90 seconds, I get an error popup on the webUI that Syncthing has lots its connection and is retrying. It always comes back but disconnects again after another 60-90 seconds. I have a shared folder containing thousands of nested files and subfolders, which takes a long time to scan, but due to this error causing Syncthing to restart so often, the scan does not progresss past 0% and never begins syncing.

sudo journalctl -fu syncthing

returns:

Jun 11 13:11:18 kali-lp systemd[1]: syncthing.service: Scheduled restart job, restart counter is at 458.
Jun 11 13:11:18 kali-lp systemd[1]: Stopped Syncthing.
Jun 11 13:11:18 kali-lp systemd[1]: Starting Syncthing...
Jun 11 13:11:18 kali-lp syncthing[78849]: [start] 13:11:18 INFO: syncthing v1.6.1 "Fermium Flea" (go1.14.4 linux-amd64) deb@build.syncthing.net 2020-06-02 09:49:22 UTC
Jun 11 13:11:18 kali-lp syncthing[78849]: [start] 13:11:18 INFO: Using large-database tuning
Jun 11 13:11:18 kali-lp syncthing[78849]: [DBPCG] 13:11:18 INFO: My ID: DBPCGCT-2SROUSY-RM24C7K-5B3CLMC-FVMS2OW-DALDH5J-TB3QFUK-353E4Q7
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Single thread SHA256 performance is 456 MB/s using minio/sha256-simd (391 MB/s using crypto/sha256).
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Hashing performance is 372.07 MB/s
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Overall send rate is unlimited, receive rate is unlimited
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: QUIC listener ([::]:22000) starting
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: TCP listener ([::]:22000) starting
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Ready to synchronize "Applications" (4lpd5-zm94f) (sendreceive)
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Ready to synchronize "Persistent" (xwa2i-ehjix) (sendreceive)
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: GUI and API listening on 127.0.0.1:8384
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: My name is "kali-lp"
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Device VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ is "kali-dk" at [dynamic]
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Device 7EJJSXS-TSQSXCO-VYV2FOW-GYB6RKI-ZBUHYFZ-MKS5QI3-UYRYMKD-IJNRPQE is "Win10 VM" at [dynamic]
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Ready to synchronize "Libraries" (yztpm-xcp5q) (sendreceive)
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Completed initial scan of sendreceive folder "Persistent" (xwa2i-ehjix)
Jun 11 13:11:19 kali-lp syncthing[78849]: [DBPCG] 13:11:19 INFO: Completed initial scan of sendreceive folder "Applications" (4lpd5-zm94f)
Jun 11 13:11:20 kali-lp syncthing[78849]: [DBPCG] 13:11:20 INFO: Established secure connection to VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ at 192.168.1.21:35388-192.168.1.164:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
Jun 11 13:11:20 kali-lp syncthing[78849]: [DBPCG] 13:11:20 INFO: Device VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ client is "syncthing v1.6.1" named "kali-dk" at 192.168.1.21:35388-192.168.1.164:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
Jun 11 13:11:29 kali-lp syncthing[78849]: [DBPCG] 13:11:29 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
Jun 11 13:11:29 kali-lp syncthing[78849]: [DBPCG] 13:11:29 INFO: quic://0.0.0.0:22000 resolved external address quic://184.75.208.34:22000 (via stun.syncthing.net:3478)
Jun 11 13:11:34 kali-lp syncthing[78849]: [DBPCG] 13:11:34 INFO: New NAT port mapping: external TCP address 24.61.226.221:43771 to local address 0.0.0.0:22000.
Jun 11 13:11:34 kali-lp syncthing[78849]: [DBPCG] 13:11:34 INFO: New NAT port mapping: external TCP address 24.61.226.221:2358 to local address 0.0.0.0:22000.
Jun 11 13:11:34 kali-lp syncthing[78849]: [DBPCG] 13:11:34 INFO: New NAT port mapping: external TCP address 24.61.226.221:53680 to local address 0.0.0.0:22000.
Jun 11 13:11:34 kali-lp syncthing[78849]: [DBPCG] 13:11:34 INFO: Detected 4 NAT services
Jun 11 13:12:48 kali-lp systemd[1]: syncthing.service: start operation timed out. Terminating.
Jun 11 13:12:48 kali-lp syncthing[78849]: [DBPCG] 13:12:48 INFO: QUIC listener ([::]:22000) shutting down
Jun 11 13:12:48 kali-lp syncthing[78849]: [monitor] 13:12:48 INFO: Signal 15 received; exiting
Jun 11 13:12:48 kali-lp syncthing[78849]: [DBPCG] 13:12:48 INFO: Failed initial scan of sendreceive folder "Libraries" (yztpm-xcp5q)
Jun 11 13:12:48 kali-lp syncthing[78849]: [DBPCG] 13:12:48 INFO: Connection to VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ at 192.168.1.21:35388-192.168.1.164:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256 closed: Syncthing is being stopped
Jun 11 13:12:48 kali-lp syncthing[78849]: [DBPCG] 13:12:48 INFO: TCP listener ([::]:22000) shutting down
Jun 11 13:12:48 kali-lp syncthing[78849]: [DBPCG] 13:12:48 INFO: Exiting
Jun 11 13:12:48 kali-lp systemd[1]: syncthing.service: Failed with result 'timeout'.
Jun 11 13:12:48 kali-lp systemd[1]: Failed to start Syncthing.
Jun 11 13:12:58 kali-lp systemd[1]: syncthing.service: Scheduled restart job, restart counter is at 459.
Jun 11 13:12:58 kali-lp systemd[1]: Stopped Syncthing.
Jun 11 13:12:58 kali-lp systemd[1]: Starting Syncthing...
Jun 11 13:12:58 kali-lp syncthing[79044]: [start] 13:12:58 INFO: syncthing v1.6.1 "Fermium Flea" (go1.14.4 linux-amd64) deb@build.syncthing.net 2020-06-02 09:49:22 UTC
Jun 11 13:12:58 kali-lp syncthing[79044]: [start] 13:12:58 INFO: Using large-database tuning
Jun 11 13:12:58 kali-lp syncthing[79044]: [DBPCG] 13:12:58 INFO: My ID: DBPCGCT-2SROUSY-RM24C7K-5B3CLMC-FVMS2OW-DALDH5J-TB3QFUK-353E4Q7
Jun 11 13:12:59 kali-lp syncthing[79044]: [DBPCG] 13:12:59 INFO: Single thread SHA256 performance is 454 MB/s using minio/sha256-simd (375 MB/s using crypto/sha256).
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Hashing performance is 370.80 MB/s
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Overall send rate is unlimited, receive rate is unlimited
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Ready to synchronize "Applications" (4lpd5-zm94f) (sendreceive)
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: QUIC listener ([::]:22000) starting
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: TCP listener ([::]:22000) starting
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Ready to synchronize "Persistent" (xwa2i-ehjix) (sendreceive)
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Ready to synchronize "Libraries" (yztpm-xcp5q) (sendreceive)
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: GUI and API listening on 127.0.0.1:8384
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: My name is "kali-lp"
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Device VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ is "kali-dk" at [dynamic]
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Device 7EJJSXS-TSQSXCO-VYV2FOW-GYB6RKI-ZBUHYFZ-MKS5QI3-UYRYMKD-IJNRPQE is "Win10 VM" at [dynamic]
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Completed initial scan of sendreceive folder "Persistent" (xwa2i-ehjix)
Jun 11 13:13:00 kali-lp syncthing[79044]: [DBPCG] 13:13:00 INFO: Completed initial scan of sendreceive folder "Applications" (4lpd5-zm94f)
Jun 11 13:13:01 kali-lp syncthing[79044]: [DBPCG] 13:13:01 INFO: Established secure connection to VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ at 192.168.1.21:35460-192.168.1.164:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
Jun 11 13:13:01 kali-lp syncthing[79044]: [DBPCG] 13:13:01 INFO: Device VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ client is "syncthing v1.6.1" named "kali-dk" at 192.168.1.21:35460-192.168.1.164:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
Jun 11 13:13:10 kali-lp syncthing[79044]: [DBPCG] 13:13:10 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
Jun 11 13:13:10 kali-lp syncthing[79044]: [DBPCG] 13:13:10 INFO: quic://0.0.0.0:22000 resolved external address quic://184.75.208.34:12149 (via stun.syncthing.net:3478)
Jun 11 13:13:15 kali-lp syncthing[79044]: [DBPCG] 13:13:15 INFO: New NAT port mapping: external TCP address 24.61.226.221:53680 to local address 0.0.0.0:22000.
Jun 11 13:13:15 kali-lp syncthing[79044]: [DBPCG] 13:13:15 INFO: New NAT port mapping: external TCP address 24.61.226.221:43771 to local address 0.0.0.0:22000.
Jun 11 13:13:15 kali-lp syncthing[79044]: [DBPCG] 13:13:15 INFO: New NAT port mapping: external TCP address 24.61.226.221:2358 to local address 0.0.0.0:22000.
Jun 11 13:13:15 kali-lp syncthing[79044]: [DBPCG] 13:13:15 INFO: Detected 4 NAT services
Jun 11 13:14:29 kali-lp systemd[1]: syncthing.service: start operation timed out. Terminating.
Jun 11 13:14:29 kali-lp syncthing[79044]: [DBPCG] 13:14:29 INFO: QUIC listener ([::]:22000) shutting down
Jun 11 13:14:29 kali-lp syncthing[79044]: [monitor] 13:14:29 INFO: Signal 15 received; exiting
Jun 11 13:14:29 kali-lp syncthing[79044]: [DBPCG] 13:14:29 INFO: Failed initial scan of sendreceive folder "Libraries" (yztpm-xcp5q)
Jun 11 13:14:29 kali-lp syncthing[79044]: [DBPCG] 13:14:29 INFO: Connection to VF5YNJ2-L7AXTFC-5MPS23W-YQJIORI-77PTFTI-5LKR3JN-DZGTD2D-X6D6EAJ at 192.168.1.21:35460-192.168.1.164:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256 closed: Syncthing is being stopped
Jun 11 13:14:29 kali-lp syncthing[79044]: [DBPCG] 13:14:29 INFO: TCP listener ([::]:22000) shutting down
Jun 11 13:14:29 kali-lp syncthing[79044]: [DBPCG] 13:14:29 INFO: Exiting
Jun 11 13:14:29 kali-lp systemd[1]: syncthing.service: Failed with result 'timeout'.
Jun 11 13:14:29 kali-lp systemd[1]: Failed to start Syncthing.

And the cycle just repeats. I cannot trace the source of this error. My desktop PC is running the same setup (same OS) with no issues at all.

3 posts - 2 participants

Read full topic

Is it normal for it to not show the progress? It looks like it is syncing just fine, but the progress just shows 100% and 0B. Reloading the page doesn’t help. Other 1.6.1 and 1.7.0 clients also show that everything is in-sync, while things are clearly not and, interestingly, 1.5.0 shows the progress just fine.

image3840×2002 427 KB

image3840×2002 350 KB

image3840×2112 400 KB

1 post - 1 participant

Read full topic

Background:

I have a send-only sync of all my non-OS drives on my desktop. Windows Desktop -> Linux Server. Both running latest syncthing (1.6.1 at time of post).

I reinstalled the OS on my desktop which wiped my syncthing DB. This is ok from what I can tell from the forums.

I reinstalled syncthing on the desktop and reconfigured the sync to the server. After the initial scan, all drives except for one reported up to date.

Syncthing reported that there were a handful of files that were out of sync to the server (ie the server has “newer” versions of those files), and prompted an override.

I figured the files may have gotten corrupted, so I did a quick sha256sum against the files, both on the server and the desktop. Both were the same. Modtimes are also the same.

Are there other criteria Syncthing uses to determine if a file is different from a remote? Is there any debug flag I can set to see why syncthing thinks the files are different?

Given the SHA’s are the same, there isn’t a real problem here, but it’s odd that syncthing thinks that only a few of the files are different.

2 posts - 2 participants

Read full topic

Recently,i have tested a peer to peer tool----resilio-sync.It is more simple to share files with people,for example ,input the below string into resilio-sync, you can get resources which someone create

BJOXKVTDB6YWGF5LE5QKSITRDTOYYM3D3

It is a key --not very long string ,smaller than magnet link.

To make syncthing more advanced, set a standard for resources (file or directory to share with) such as resilio-sync do,open the third software for them to download ,syncthing will be more popular!

7 posts - 4 participants

Read full topic

Hi there,

I’m using Syncthing for quite some time now behind a Corporate Firewall (which details I’m not aware of). Until now I was working with a Windows 7 computer, lately running Syncthing 1.6.1. ST is configured for NAT traversal, but I did not need to set the all_proxy environment variable described in https://docs.syncthing.net/users/proxying.html. Actually, to my surpise, it simply worked.

Now, with a new Windows 10 Laptop, in the same corporate network, ST cannot establish communication anymore.

I’m running both computers in parallel right now, Windows 7 OK, Windows 10 Both running ST 1.6.1, on both Windows Firewall is open for ST.

Outside the corporate network, ST is running well on Windows 10 as well.

Any idea where I can have a look. I would be happy to provide any additional information (if I have it)…

4 posts - 2 participants

Read full topic

So a while back I had a few features in mind, most of which required devices knowing each others public keys for the purpose of encrypting secrets to each other without having been connected. Currently there is really no way to know that ahead of time.

We have the key available in discovery server, so I was thinking of adding support for discovery server to store that, and returning during discovery lookup (or could be separate endpoint).

The devices would then store that value locally (or store it on connection if they don’t get it via discovery), so if it was a separate endpoint it would only be called once.

I don’t have concrete feature in mind, but I think this would be generally useful to have, as it allows to craft messages only readable by the destination.

A few things where this might be useful:

1. Some sort of side-channel for the future folder password sharing? If I know I want to share folder X with device D and allow it to decrypt it, I could have a blob that is encrypted with Ds public key that only D can read folding the details. I guess the same could be done with encrypting it with a passphrase that both sides know, but just thinking out loud here.
2. This could be useful for encrypted discovery (yet it does not work for bootstrapping, as you can’t encrypt addresses for devices that you don’t know that want to talk to you).
3. Something something, trusted token for auto-accepting remote devices or something? I guess this can just be a passphrase and doesn’t really need to be something that is public key encrypted, but I guess going from a small token to a device + folder + proof combo is more interesting.

Anything else?

General feeling about this?

8 posts - 2 participants

Read full topic

I am very new to Syncthing. I want to know step by step how to connect to the remote device which is on other networks. On my windows, in Syncthing the address is set to ‘dynamic’ and also on the remote device in Syncthing address is to set to ‘dynamic’. I didn’t change any default settings and just used device ids to connect two devices.

I read something about the port forwarding and ssh tunnel but, I didn’t understand it. Can someone please explain to me this? and help with this?

Thanks in advance

Annotation 2020-06-13 1418401123×517 29.8 KB

Annotation 2020-06-13 1419321122×586 37 KB

2 posts - 2 participants

Read full topic

hi guys,

I’ve changed:

    <address>0.0.0.0:8384</address>

restarted systemd service and get:

$ stcli show connections 2020/06/13 11:04:27 getting config: Invalid API key

Is that normal & expected and if ‘yes’ then can you tell what happens there? many thanks, L

3 posts - 3 participants

Read full topic

Seems like this issue came up before but that issue close.

I’m on MacOS 10.15.5 and I’m getting an error, it’s trying to upgrade to 1.6.1

Automatic upgrade: gzip: invalid header

5 posts - 3 participants

Read full topic

Hi,

Using 1.6.1 on a Mac. Shorty after the startup Syncthing has issues.

I reinstalled Syncthing. Config was still available, reinstall did not help. I then deleted the DB files. Rescan and all seemed to be fine then. 3 hours later same starts again.

Attached the log (sorry, I had to replace github.com by githubcom, otherwise I cant send), any hints maybe?

Thanks in advance!

=== [start] 19:57:52 INFO: syncthing v1.6.1 “Fermium Flea” (go1.14.4 darwin-amd64) teamcity@build.syncthing.net 2020-06-02 09:49:22 UTC

…

Panic at 2020-06-13T19:58:19+02:00 panic: runtime error: index out of range [1] with length 1

goroutine 98 [running]: githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).processNeeded(0xc0001b6380, 0xc000041a80, 0xc000959da0, 0xc000959ce0, 0xc000959c20, 0xc000959da0, 0xc000959c20, 0x4e261c0, 0xc0006b9c90, 0xc00285d520, …)

… a lot more and ending with

/Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:247 +0x49 created by githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).pullerIteration /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:245 +0x4a9

goroutine 425 [chan receive]: githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).copierRoutine(0xc0001b6380, 0xc000959ce0, 0xc000959c80, 0xc000959d40) /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:1193 +0x476 githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).pullerIteration.func2(0xc0001b6380, 0xc000959ce0, 0xc000959c80, 0xc000959d40, 0x4e261c0, 0xc0006b9c80) /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:247 +0x49 created by githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).pullerIteration /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:245 +0x4a9

goroutine 424 [select]: githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).dbUpdaterRoutine(0xc0001b6380, 0xc000959da0) /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:1614 +0x238 githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).pullerIteration.func1(0xc0001b6380, 0xc000959da0, 0x4e261c0, 0xc0006b9ca0) /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:239 +0x35 created by githubcom/syncthing/syncthing/lib/model.(*sendReceiveFolder).pullerIteration /Users/syncthing/agent/work/174e136266f8a219/lib/model/folder_sendrecv.go:237 +0x414

goroutine 3829 [select]: net.(*netFD).connect.func2(0x4e28c00, 0xc0038b80c0, 0xc0038cc280, 0xc0063af980, 0xc0063af920) /Users/syncthing/sdk/go1.14.4/src/net/fd_unix.go:129 +0xba created by net.(*netFD).connect /Users/syncthing/sdk/go1.14.4/src/net/fd_unix.go:128 +0x22f

3 posts - 2 participants

Read full topic

I want all the photos in selected folders on my phone to be synced to another computer. On the other computer I want to be able to delete photos. I want my phone not to care about this, but just to keep sending new photos to the other device. Can syncthing handle this?

1 post - 1 participant

Read full topic

After creating the syncthing@.service file in /lib/systemd/system, I created a user on my system called syncthing.

Then I run:

systemctl enable syncthing@syncthing.service

And then:

systemctl start syncthing@syncthing.service

Then I edit the config.xml file in the syncthing home folder to adjust the listening IP address to the machine’s IP.

Then, I open up a browser and load Syncthing. After that, I add the remote machine to Syncthing on my laptop and wait for the prompt on the server.

Now that we’re connected, I want to sync a folder on my laptop to the server. Creating that share prompts the server and when I attempt to point the share on the server to the intended sync folder, every time I get permissions denied to create .stignore and a folder as well.

So, I find myself manually creating that folder…

I thought I could simply setfacl -m user:syncthing:rw that folder on the server to give syncthing user rights…but I’m probably missing a step or doing something wrong.

Any ideas?

3 posts - 2 participants

Read full topic

I’m sorry as I don’t quite get it. Not a tech savy person. I read somewhere that syncthing transfers the files as is from one to another.

I read in the documentation that the file on transfer is protected by TLS Encryption.

My question is, can the relays or the global discovery see my files being transferred? I mean, the files are being passed from thru those relays right? Meaning the files touch those servers/relay, or am I wrong here?

3 posts - 3 participants

Read full topic

Hi,

I’m currently on v1.6.1 with an SO>SR Duplicati “backup” cluster where SO sends to SR periodically while Duplicati is not running.

SO, device A:

image1151×749 45.3 KB

SR, device B:

image1183×788 45.7 KB

If I click 10 items on B, nothing shows up.

image888×372 8.3 KB

I’ve restarted Syncthing on both nodes, clicked “Rescan” and waited a while, but nothing else changes or happens.

Btw: I’ve already checked device A’s ignore patterns and don’t see any mistake. I’ve ignored one folder (months ago on v1.5.0 already) because I don’t want it to be synced over to the target and the target doesn’t have this folder.

Which logs should I grab next?

Thank you.

Kind regards Catfriend1

2 posts - 2 participants

Read full topic

Hello, I wanted to find out if the program Syncthing can be used for synchronization of files in Alfresco, ie desktop and Alfresco database

thank you for the info

Vladimir

2 posts - 2 participants

Read full topic

Hi

On my LAN I have 3 Win10 devices that reach to open upnp portforward in the gateway. Another device (armf raspbian) fails. Any idea please ? I changed config (NatLeaseMinutes=6 & NatRenewalMinutes=3) so that there is more log entries and started STTRACE=upnp syncthing &. All devices are 1.6.1

2020-06-15 11:31:43 My ID: SHORT-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH
2020-06-15 11:31:44 Single thread SHA256 performance is 45 MB/s using crypto/sha256 (45 MB/s using minio/sha256-simd).
2020-06-15 11:31:45 Hashing performance is 40.99 MB/s
2020-06-15 11:31:45 Overall send rate is unlimited, receive rate is unlimited
2020-06-15 11:31:45 Using discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2020-06-15 11:31:45 Ready to synchronize "Folder1" (Folder1-ID) (receiveonly)
2020-06-15 11:31:45 Ready to synchronize "Folder2" (Folder2-ID) (sendreceive)
2020-06-15 11:31:45 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2020-06-15 11:31:45 TCP listener ([::]:32571) starting
2020-06-15 11:31:45 Using discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2020-06-15 11:31:45 ...
2020-06-15 11:31:45 Completed initial scan of sendreceive folder "Folder2" (Folder2-ID)
2020-06-15 11:31:45 Using discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2020-06-15 11:31:45 GUI and API listening on 127.0.0.1:8384
2020-06-15 11:31:45 Access the GUI via the following URL: https://127.0.0.1:8384/
2020-06-15 11:31:45 My name is "Raspi"
2020-06-15 11:31:45 Device WIN101-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH is "WIN101" at [dynamic]
2020-06-15 11:31:45 Device WIN102-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH is "WIN102" at [dynamic]
2020-06-15 11:31:45 Device WIN103-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH is "WIN103" at [dynamic]
2020-06-15 11:31:46 Completed initial scan of receiveonly folder "Folder1" (Folder1-ID)
2020-06-15 11:31:46 Established secure connection to WIN101-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH at [IpV6-0]:39498-[IpV6-1]:22010/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
2020-06-15 11:31:46 Device WIN101-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH client is "syncthing v1.6.1" named "WIN101" at [IpV6-0]:39498-[IpV6-1]:22010/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
2020-06-15 11:31:46 Starting discovery of device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0
2020-06-15 11:31:46 Starting discovery of device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0
2020-06-15 11:31:46 Sending search request for device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0
2020-06-15 11:31:46 Listening for UPnP response for device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0
2020-06-15 11:31:46 Sending search request for device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0
2020-06-15 11:31:46 Listening for UPnP response for device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0
2020-06-15 11:31:46 Established secure connection to WIN102-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH at 192.168.0.49:50444-192.168.0.15:22015/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2020-06-15 11:31:46 Device WIN102-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH client is "syncthing v1.6.1" named "WIN102" at 192.168.0.49:50444-192.168.0.15:22015/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2020-06-15 11:31:47 Established secure connection to WIN103-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH at 192.168.0.49:45912-192.168.0.20:22020/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
2020-06-15 11:31:47 Device WIN103-BBBBBBB-CCCCCCC-DDDDDDD-EEEEEEE-FFFFFFF-GGGGGGG-HHHHHHH client is "syncthing v1.6.1" named "WIN103" at 192.168.0.49:45912-192.168.0.20:22020/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
2020-06-15 11:31:56 Discovery for device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0 finished.
2020-06-15 11:31:56 Discovery for device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0 finished.
2020-06-15 11:32:00 Detected 1 NAT service
2020-06-15 11:32:15 Joined relay relay://46.223.16.186:34617
2020-06-15 11:34:56 Starting discovery of device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0
2020-06-15 11:34:56 Starting discovery of device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0
2020-06-15 11:34:56 Sending search request for device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0
2020-06-15 11:34:56 Listening for UPnP response for device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0
2020-06-15 11:34:56 Sending search request for device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0
2020-06-15 11:34:56 Listening for UPnP response for device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0
2020-06-15 11:35:06 Discovery for device type urn:schemas-upnp-org:device:InternetGatewayDevice:2 on eth0 finished.
2020-06-15 11:35:06 Discovery for device type urn:schemas-upnp-org:device:InternetGatewayDevice:1 on eth0 finished.

Thank you

2 posts - 2 participants

Read full topic