[1.34.1]
Update syncthing to 2.1.1
Full Changelog
fix(syncthing): properly upgrade via REST when Syncthing is running (fixes #10697) by @calmh in #10699
fix(versioner): ensure user read/write/execute on archived dirs (fixes #10532) by @calmh in #10696
fix(discover): only announce wildcard for TCP punching when listening on wildcard address (fixes #10503) by @calmh in #10691
fix(stcrashreceiver): close source loader responses on errors by @mattn in #10704
fix(protocol): handle zero-size requests (fixes #10709) by @calmh in #10710
Closest upstream thread I found is https://forum.syncthing.net/t/syncthing-failed-to-notify-sync-failed-for-months/21279 but maybe worth asking in their forum .
@girish said in Changelog format seems broken:
@SansGuidon that's my experience too. In fact, often, it makes up changelog items when it lacks information and no amount of prompt engineering seems to work.
I don’t have good experience with Mistral tbh. Gemini 2.5 Pro is much more reliable for such tasks…
Maybe the syncthing app doesn't re-test permission immediately? I went back to the folder, and the error was gone, syncthing says its "up to date" seems to have created its files ok.
Nothing got touched in the inbetween time. But its working now, so I'm happy with that result.
Thanks!
@james I've had multiple syncthings running on a cloudron server for a few years now without issues. Not sure if this is because the issue was resolved upstream, or if changing the default port for the initial handshake between devices has done the trick.
I think that information is the same across apps . The first part is here - https://docs.cloudron.io/volumes/#add . The second part should be added ( cc @girish)
No, syncthing is made to synchronise files between instances of syncthing. While rclone is ? primarily) an utility to copy files between different backends (of one which could be a local directory).
Just wanted to add a note that Syncthing really only has 1 user. All LDAP authenticated users manage the same set of folders. I have adjusted the postinstall accordingly.
So Cloudron has a package version and an upstream version. In this case the package version is 1.22.0 while the upstream version is 1.23.0. So all fine, however the patch release will be out soon. Not sure why we haven't gotten a notification about this, so thanks for the heads up here.
@girish I followed the example provided at https://docs.cloudron.io/volumes/#sharing and did a 'touch ./test-file'
From what I can see, the directory does appear to have write permissions.
[image: 1668070120922-screen-shot-2022-11-10-at-12.48.07-am.png]
