cross-posted from: https://sh.itjust.works/post/40624933
Several different, random seeming files across various different Syncthing folders keep failing to sync even after restart, rescan, and reconfiguration, with the below error
syncing: finishing: opening temp file: open /storage/emulated/0/Pictures/Webcam/.syncthing.2024-07-1621:42:30.jpg.tmp: operation not permitted
I don’t how how to fix it, the desktop app has the required permissions, and the Android app has as many storage permissions as I can give it under Android’s horrible SAF limitations.
It seemed to used to be happening only to some specific old files, but now it’s happening to all the new files I add onto my laptop under Videos or Music.
In addition, when trying to sync files with a specific server, it shows as disconnected, even when both are online and connected to the LAN (my phone via WiFi, the server via Ethernet), and there is some error about encryption expectations
2025-06-20 23:33:38: Failure checking encryption consistency with device server for folder “Music” (8ipwu-ehye4): remote expects to exchange encrypted data, but is configured for plain data
The server is running Syncthing GUI on Fedora GNOME, same as the laptop (which does work besides for the first issue), so I don’t know what the difference is that would be causing this, not a single file has been synced to the server.
This is honestly making me want to get a Fairphone 5 with Ubuntu touch to get rid of these issues, but I can’t do that now.
If anyone could advise, I would really appreciate it!

Regarding the second error,
remote expects to exchange encrypted data, but is configured for plain data, does this happen only for newly sharing folders (i.e., not for existing folders)? If yes, then it looks like you are running into overly aggressive auto-completion by your web browser. See https://github.com/syncthing/syncthing/issues/10341 for details.In short, in the “Sharing” tab, make sure that there is no password entered.
I’m not sure exactly when it happens. I removed every folder and added it again, setting the encrypted level to none, and I don’t seem to be getting that error any more.