Hey,

Syncthing has no in-built monitoring support, so sync issues tend to go un-noticed.

What are your solutions to monitor syncthing nodes?

Sure, I could write scripts that use the REST API, but if there's an easier way, I'll take it!

Cheers

I'm currently using Pocket to sync articles between my phone and computer. I would like to leave Pocket behind and just sync downloaded articles directly between devices.

I've been using ST for ~6 months and sync camera folder on my new phone to an old phone with UL photo uploads, works great. What I need is to import ~10k photos from external drive from a relative, but would like to have them synch in google photos to a specific folder so my relative's photos aren't interspersed with my own photos since imports will read the photo date and sort them accordingly most times in google photos.

I'm guessing I need to synch a desktop folder on my computer to my "new" phone's camera folder that is synched to my old phone and that gets me uploaded and free storage, but the photos would be all over the place. Thanks for any ideas!

On my desktop computer, I have tried to use Syncthing WebUI to add my remote headless server (no GUI/display, only CLI), which was established by just running ./syncthing command. I have got the ID from the CLI output.

Yet my WebUI tells me "connection refused" and "context deadline exceeded" and the headless server output shows "rejected: unknown device" next to my connection attempt.

In a "syncthing --help" output, I am unable to find any command which would add mine defined remote machine ID and allow its connections.

I have tried to access http://headless server IP:8384/ but it timeout. I am unable to find any firewall blocking, another service on a different port is accessible.

Any idea how to proceed interconnecting the two devices simplest way?

Hi all, Android 12, on an Ulefone. Android seems to continue to kill Syncthing for some reason, I've set Battery Unrestricted for it already and unrestricted data access too.

My synching speed is like 80kb/s, Am I doing something wrong? (Two phones, one with VPN but with local network allowed)

What I mean by n-to-n sharing is that I have all of my devices sharing the same folder with every other device. This has definitely been a bit of a pain to set up and manage (moreso because a few machines use Docker so they're basically double-NAT'd). My biggest concern is having conflicts out the wazoo and losing data. The most important thing to me is my KeePass vault.

I'm glad to announce v0.2.0 release!

The major feature of the new release is the possibility to use relay transport from the public pool of synthing relays from https://relays.syncthing.net/ . Currently syncspirit picks a random on the start.

More complete changelog can be seen here, and the source code and binaries (for windows and linux) can be downloaded here.

syncspirit is syncthing-compatible syncrhonization program, which implements BEP-protocol. syncspirit is written from the scratch software, which has different technical decisions on it's foundation to overcome syncthing limitations. syncspirit is available for windows and linux; you can build and use it on termux for Andoid. Currently syncspirit is targeted to power users and early adopters, who feel self comfortable with command-line.

Any feedback is welcome!

WBR, basiliscos.

Hello,

I'm glad to do first announcement of my syncspirit, an alternative implementation of BEP protocol, gracefully shared by syncthing developers. In simple words, it is syncthing-compatible.

syncspirit is written from scratch in C++, so a lot of expected features found in syncthing missing. However, it is able to do one-side syncrhonization, i.e. it implements "receive-only" folder model at the moment.

Currenly only command-line intreface is available, so, it is targeted mostly to power users. The prebuild binaries for windows and linux are available for downloading, they are statically built, so no additional external dependencies should be required.

The interface can be evaluated and at asciinema

Why ss might be interesting for you? Well, it already has some unique features, like rsync-like mode (i.e. download files from peer and exit; it is implemented as "exit-on-inactivity-timeout"), and, it might have quite a good disk performance on HDDs since it tries hard to write sequentially. Also, the whole performance is tuneable (i.e. number of threads is manageable and configurable).

Any feedback is welcome. My short-term plan will be implement relay-transport.

Cheers, basiliscos

Ign:10 https://apt.syncthing.net syncthing InRelease                           
Err:11 https://apt.syncthing.net syncthing Release                             
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 82.196.13.137 443]

Anybody got any ideas?

#Syncthing is a great tool for decentralised syncing between devices.. and with some simple configuation, can act as a backup service too.