@Dnominated wrote:

Hi! Thanks for your support.

I’ve got a dedicated server setup. It has a Synctrayzor share, called Books, with a unique Folder ID, let’s call it ababa-babab. It’s folder is C:\Books.

I have about 5 other devices, one of which is my laptop. The laptop connects to the Books share, ababa-babab.

I created a second share, on the same server, called ‘Books Read-Only’. It points to the same folder, C:\Books, and has a unique Folder ID, xyxyx-yxyxy. The idea is Books Read-Only can only send out updates. The other 4 clients connected to Books Read-Only can only receive a copy of the contents from the server, not send changes made on them locally.

Is there a conflict here? Is there something I should do special to make the server share out two Folder ID’s mounted in the same folder?

Thanks!

Posts: 2

Participants: 2

Read full topic

@Dnominated wrote:

I’ve got a laptop, with a read-only share called ‘Books Read-Only’.

I have two android clients, 1 & 2, on the local network with the server, that are connected to ‘Books Read-Only’. I have told each android client in their Folder settings, that the folder is Receive Only.

Laptop is running SyncTrayzor 1.1.24, SyncThing 1.3.1 Androids are running SyncThing-Fork 1.3.2.2, SyncThing 1.3.2-preview 1 (From FDROID)

Androids had a previous copy of Books that was out of sync (a manual copy). ‘Books’ on the Androids is at /storage/emulated/0/Books, physically on an adopted, formatted-as-internal, 128GB A2 SanDisk SD card. I’ve had no file system problems, the cards were ordered from Amazon from SanDisk, so they aren’t fake.

Laptop is Windows 7 Pro. The Send-only ‘Books’ is at E:\Books, a partition on the SSD. Again, the SSD is new, has had zero file system errors.

I keep getting a BIG RED WARNING on the Androids, a red cloud with an up arrow: “REVERT LOCAL CHANGES!!!”, sometimes even though it shows in terms of # of files, the local android copy is the same as the global (laptop) copy. And Failed Items (xxx), some random amount [right now it’s 160 out of 16597 global items] on Android 1. Similar things happen on Android 2.

The other annoying thing, is really old invitations like “Default Folder” are not expiring. For instance, I get the “LAPTOP WOULD LIKE TO SHARE DEFAULT FOLDER” on the Androids, even though Laptop NO LONGER HAS that shared folder, at all. It’s been deleted - gone! It’s like the Android clients memorize every invitation, then re-iterate it at every opportunity, although that folder is no longer being offered (it’s been weeks now).

I’m starting to call SyncThing SyncBug among my friends.

Posts: 6

Participants: 4

Read full topic

@kkleinfelter wrote:

Mixing case-sensitive endpoints with case-insensitive endpoints is a Very Bad Thing with Syncthing. I get it.

With APFS and Win10, it is possible to make MacOS and Windows case sensitive. For Windows, it happens at the folder level. With MacOS, it happens at the volume level, but you can create a new volume within an existing container. Theoretically, it should be possible to sync all 3 of them, case-sensitive.

My question is this: Is there anyone who is actually using Syncthing with a setup including case-sensitive Linux, case-sensitive MacOS (with APFS), and case-sensitive Win10? Does it work, and does it avoid the data-loss-with-renaming-changing-only-case scenario?

Posts: 1

Participants: 1

Read full topic

@Alex wrote:

got a warning that my phone ran out of space and I found the problem: syncthing-android filled its log file with endless repeats of:

[X2KPZ] WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: recvfrom: connection refused

since there are no timestamps I don’t know how fast it spammed this. At the first warning I did not notice that it was syncthing and just deleted some files (around 500MB) and after 2 hours I saw the warning again and found a log file with the size of 2GB, deleted it and it started growing again (only this line, nothing else), a reboot stopped it.

Another problem: syncthing should have been stopped at this moment since I set it to only run while charging and it was not charging at this moment.

Version: v1.3.1 for syncthing and syncthing-android

Posts: 2

Participants: 2

Read full topic

@j.n.mol wrote:

I’m a happy Syncthing user, works great! Now I’m facing a new challenge, didn’t manage to solve it yet:

I want to synchronise a fixed directory (say, c:\workfiles) on our company laptops with a directory on our NAS.

That works perfectly for one user per laptop. Now I’ve multiple users who use the same laptop for working at home. They all use the same folder (c:\workfiles) but use their own login credentials. I’ve installed Syncthing as administrator, running from scheduled task even when administrator is not logged in. It works for the administrator but not for my colleagues. In their case Syncthing simply doesn’t connect to the NAS.

What can I do or change?

Posts: 1

Participants: 1

Read full topic

@petrzhebin wrote:

Hello all. At first, i know english bad, so i can sometimes make mistakes. The problem is: I got a PC1 where installed SyncTrayzor and two android phones where Sync installed too. I’ve moved all the photos from two phones to PC1 and the data is constantly being updated with new photos. No the space is over on PC1 and i made a PC2 with Win7 and 2Tb free space. No I want to тransfer the program to PC2 and all data (photos and videos from two phones) and have the phones synchronize with the new PC2 and delete the program and data on the old PC. Describe the procedure for doing this, please.

Posts: 3

Participants: 2

Read full topic

@nivek wrote:

I installed the syncthing app on my Android phone today, and in the course of trying to add a new shared folder, I needed to access the GUI on another Syncthing instance which I have running remotely on a virtual private server.

When I set up the remote instance, a few weeks ago, I thought I had left it publicly accessible with a password. Today however it seems not to want to show itself. So my primary question has to do with accessing the GUI on my remote instance.

It MIGHT be because I installed UFW for the purpose of configuring other applications. But I have run ufw allow syncthing and ufw allow syncthing-gui and still no dice.

Here’s what I get if I query the system service on my remote VPS:

root@localhost:~# systemctl status syncthing@syncthing.service
● syncthing@syncthing.service - Syncthing - Open Source Continuous File     Synchronization for syncthing
   Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-11-23 03:50:13 UTC; 11min ago
     Docs: man:syncthing(1)
 Main PID: 9645 (syncthing)
    Tasks: 9 (limit: 1149)
   Memory: 68.4M
   CGroup: /system.slice/system-syncthing.slice/syncthing@syncthing.service
           └─9645 /usr/bin/syncthing -no-browser -no-restart -logflags=0

Nov 23 03:51:53 localhost syncthing[9645]: [I2AND] INFO: Unexpected folder "SyncPhone" (SyncPhone) sent from device "xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx"; ensure that the folder exist...
Nov 23 03:52:42 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 03:53:52 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 03:55:02 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 03:56:13 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 03:57:23 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 03:58:33 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 03:59:43 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 04:00:53 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"
Nov 23 04:01:53 localhost syncthing[9645]: [I2AND] INFO: Dialer for quic://123.456.78.910:22000: unknown address scheme "quic"

(The first error above is because I added a new shared folder from another device, and I haven’t been able to access the GUI to “approve” it).

I’m wondering if I need to do something to configure the “quic” protocol?

I also notice that there is no GUI IP address shown above.

Here’s the GUI section of my config file for your reference:

<gui enabled="true" tls="true" debugging="false">
    <address>0.0.0.0:37147</address>
    <user>myusername</user>
    <password>mypasswordhash</password>
    <apikey>myAPIkey</apikey>
    <theme>dark</theme>
</gui>

(To confirm, when I try to access the GUI, I use https://my.server.ip.address:37147 — but I have also tried port 8384 just in case. Neither one works.)

Let me know if I can provide any other info. Thanks!

Posts: 2

Participants: 2

Read full topic

@DrPhant0m wrote:

We just lost a month of pictures after realizing syncthing wasn’t running when my wife’s SD card went bad. Dual-mode failure!

It made me realize that I’d like a warning if syncthing hasn’t connected for several days.

We use it to sync our Android phones (pics, etc) to our server.

Is that possible?

Thanks!

Posts: 4

Participants: 3

Read full topic

@trymeout wrote:

Please add the pause button in the main Syncthing folder list and device list on each folder/device listed. This will allow users to easily pause or resume a folder or device by opening the app and tapping pause/resume on the folder/device instead of going into the folder/device settings.

Posts: 1

Participants: 1

Read full topic

@Finomosec wrote:

Hi,

i have the following on my ignores:

(?d)*.tmp
(?d)~*.tmp

I have these in a text-file called globalignore.txt which is shared between all machines and imported in every folder using this: #include ../syncthing-config/globalignore.txt

But still i see this in the “not synchronized” view:

grafik842×350 12 KB

grafik848×496 17.6 KB

I have beeing observing this for a long time already.

It seems though only the tmp files are affected. Other ignores seem to work as intended.

Here is my full ignores file: globalignore.txt (1.0 KB)

Any ideas?

Greetings Fino;

Posts: 1

Participants: 1

Read full topic

@Wal wrote:

Hello,

I am using Syncthing on my two systems (Windows 7 and Linux) in my homeoffice. For some weeks now, Syncthing is not synchronizing anymore. On the Windows system, the terminal says

“[OISNM] 18:30:11 WARNING: Error on folder effgc-ync5j: insufficient space on disk for database (C:\Users\xxx\AppData\Local\Syncthing\index-v0.14.0.db): 0.8 % < 2 %”

I already tried to increase the amount of available disk space for syncthing from 1 % to 2 %.

Can anyone help? I would be very grateful.

Best regards Wal

Posts: 5

Participants: 2

Read full topic

@compusolve-rsa wrote:

This app is most welcome, thank you to the devs. You guys rock for creating this.

A small issue on android fyi.

Android 6.0 has an external sdcard write restriction, and the-awesome-syncthing can’t write .stfolder. As a work around, is it possible to have a “Syncthing” folder on the internal sd as a default where all .stfolder(s) are kept? This would provide a way to get around the write restriction on android 6 and still get external sdcard folders syncing.

Comments welcome.

Lee

Posts: 3

Participants: 3

Read full topic

@Dinosaur wrote:

Hi All

I have a requirement that I like to bounce off the members first before I start installing things. Broad Layout: There are upto 12 machines in a Food factory, each with an industrial PC running Linux Mint. There is one other pc that can be used as a server in the same facility.Each PC (Fitlets) has Wifi. A dedicated program operates each of these machines and requires milli second precision. I say that because I can’t afford Network traffic during production. When a machine is stopped for longer than 30 sec’s the report is updated with values. During that time we can sync with the server which has a very light non-time critical function. The system has been running successfully for a few years now.

I have been asked to automate getting reports to head office on the other side of the country.So getting the reports from the server to HO is my main concern with Syncthing, as the preliminary reading did not shed light on that for me. The reports do not need to be synced to a schedule, but as the operators turn the power off for cleaning when production finishes picking the time for syncing seems difficult. The clients can sync with the server as soon as production has stopped for 30 sec’s. Similarly I don’t mind if HO is updated the following day when the power is first turned On.

So, I don’t have a specific question but hoping to prompt someone to reply with a roadmap to achieving this.

Regards

Posts: 3

Participants: 3

Read full topic

@obma wrote:

There are some thoughts/ideas I wanted to share and discuss with the synchting community. Parts of them may have been discussed here and there, but - I think - not in the following context.

I am running a kind of top down hierarchy of syncthing nodes by having one node that is added by all others as introducer (as described earlier here). The problem/thing I’d love to simplify is that there are some nodes syncing a whole directory (the fileservers) and nodes that should only sync parts of that directory (laptops, smartphone, … - let’s call them client-nodes). So right now I have stignore files set up on each client-node. Easier to administer would be a central, per peer-node stignore set up on the introducer-node.

I’ll try to explain that with the following use-case: Sharing a directory, i.e. photos, with somebody else.

In the current setup I have to seperate the folder to be shared from the main share - by putting the directory outside of the main directory or seting up a stignore-pattern to exclude the directory from the main share and setting up a new share.

If there would be a per node stignore for a share, I could just leave everything as it is. I would just add the new node to the introducer, share the main share with that new node and set a stignore-pattern on the share for the new node (on the introducer) that excludes everything except for the photos-directory.

Also it would be nice to maintain the stignores of your syncthing network centralized this way. You just need to open the UI of the introducer to see or adopt the ignore patterns of the connected nodes. Additionally it would be more comfortable to add an android node. Instead of fiddling on the touch screen to type in the ignore patterns you could just sit on a PC, open the UI of the introducer, add the android node and set the stignore-patterns for it.

It could also add some security. Right now I can sync parts of the big, allover share to trusted nodes via stignore on the trusted-node or to untrusted nodes only by separating them from the allover share as described above (what could mean to have to go through UIs of several nodes). If the per-node stignore gets pushed from the introducer to all other nodes, it might not be necessary anymore to seperate a directory from the allover-share in order to share it with an untrusted machine.

I hope you can follow my thoughts. I know, everything quite vague. Maybe something somebody else also thought of? Maybe an inspiration for a new feature?

Thanks for reading.

Posts: 3

Participants: 3

Read full topic

@kkleinfelter wrote:

The browser tab for the web page for one of my Syncthing nodes has an exclamation point in a black circle. I presume this indicates an alert. I don’t see anything obviously related in the log.

Where do I go to see the current alert (or whatever else the icon indicates)?

Posts: 3

Participants: 3

Read full topic

@ibrouting wrote:

I am trying to install Sync on a server at my office that renders reports every 4 hours and pushes them to a folder. The idea is that I can sync the folder to my phone and laptop so when I am not in the office I can read them. My server is Windows server 2012 and my laptop is Win 7 and Ubuntu. Have not tried on the phone yet but I cannot see the server from wither laptop. I checked the logs and this is what I see after a restart:

[EDIW7] 12:44:44 INFO: Detected 0 NAT services
[EDIW7] 12:44:54 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[EDIW7] 12:44:54 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[EDIW7] 12:44:54 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]
[EDIW7] 12:44:59 INFO: Couldn't fetch release information: Get https://upgrades.syncthing.net/meta.json: dial tcp 82.196.13.137:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[EDIW7] 12:44:59 INFO: Automatic upgrade: no version to select
[EDIW7] 12:45:02 INFO: Couldn't fetch release information: Get https://upgrades.syncthing.net/meta.json: dial tcp 82.196.13.137:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[EDIW7] 12:45:15 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[EDIW7] 12:45:15 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (1.615513 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]
[EDIW7] 12:45:15 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[EDIW7] 12:45:36 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[EDIW7] 12:45:36 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (1.994575 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]
[EDIW7] 12:45:36 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[EDIW7] 12:45:57 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[EDIW7] 12:45:57 INFO: Entering the backoff state.
[EDIW7] 12:45:57 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (2.227601 failures of 2.000000), restarting: false, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]

Not really sure how to proceed here?

EDIT: I have tried turning off the firewall and the AV on both sides to make sure it isn’t blocking anything.

EDIT2: And the laptops (Win 7 and Linux) can see each other.

Posts: 12

Participants: 3

Read full topic

@syncteam wrote:

Hey folks - sorry if this is a common topic, but I have been searching and I still cannot find an answer.

I wonder if there is a “selective sync” capability built within Syncthing. I mean it in the same way that Dropbox means it.

So let’s say I “sync” or rather “share” a folder with 100 subfolders in it. And the other user just wants to download the contents of 2 or 3 of those folders, not all 100. Maybe sort of like an FTP site. Is this possible?

I am also looking into this feature within Syncthing because Resilio offers it as a “Pro” feature. Hoping to get this functionality for free.

Can someone tell me if this is possible? Does this sort of functionality have a special name within Syncthing?

Thanks a lot!

Posts: 7

Participants: 2

Read full topic

@microwavesafe wrote:

I have been playing with a proof of concept client written in TypeScript with node. My rough idea was to create a client that can download single files, rather than sync whole directories.

I have the client to the point where it is receiving Index messages from a syncthing server on port 22000. One thing that jumps out as not ideal is the inclusion of the Blocks (array of BlockInfo messages) field in the FileInfo message in the Index message. This list can be very large and cost a fair amount of bandwidth. It makes perfect sense if all files are always synchronized, which I accept is the use case for this protocol, but my client may not even want to download this file, so downloading the BlockInfo is a waste.

Is there a way we could separate the two messages? Maybe a field in the ClusterInfo I send that informs the server to not include them in the Index message it sends, then add a field in the Request message that asks for the BlockInfo?

This may all be impractical and there’s a fair chance I’m missed an important use case, but I thought it was worth floating the idea.

Posts: 4

Participants: 2

Read full topic

@Tommy wrote:

Hi!

First of all, thanks for this incredible software.

I have an issue with invalid file names that the NAS (ASUSTOR, manually updated) is throwing to the Windows client. Since there’re too many (2100+ and still scanning) to manually edit, is there a way for the Windows client to normalize the directories and files names on sync, instead of ignoring them?

Thanks in advance.

Posts: 3

Participants: 2

Read full topic

@Wizard17 wrote:

Once in a while, and only on one server (2012R2) Syncthing loses connection and starts logging continuously until all available diskspace is consumed and Syncthing goes into stopped-mode. The log when it starts is like this: [VISHJ] 18:47:05 INFO: Connection to JDB3PLR-HNWZ7H4-2ZDRVYR-HUKZ32W-LMXMAZG-3BBBOXH-GFIIS5K-DM3XDQL at 192.168.0.55:62260-212.47.253.154:22067/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 closed: replacing connection [VISHJ] 18:47:05 INFO: Device JDB3PLR-HNWZ7H4-2ZDRVYR-HUKZ32W-LMXMAZG-3BBBOXH-GFIIS5K-DM3XDQL client is “syncthing v1.3.1” named “Management” at 192.168.0.55:62638-80.56.17.214:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 [VISHJ] 02:39:53 INFO: Connection to JDB3PLR-HNWZ7H4-2ZDRVYR-HUKZ32W-LMXMAZG-3BBBOXH-GFIIS5K-DM3XDQL at 192.168.0.55:62638-80.56.17.214:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 closed: reading length: read tcp 192.168.0.55:62638->80.56.17.214:22000: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.

Then, it keeps repeating the last message over and over fillling up the entire disk. This is Windows 2012R2 Syncthing v1.3.1. I can’t find a setting to at least disable logging. Simply shutting down Syncthing and starting it solves it because it starts a new logfile. Annoying thing is however ofcourse that Syncthing stops without you knowing, so that node is then stopped/offline for as long as the disk holds out…

Posts: 6

Participants: 3

Read full topic