I am ttying to configure Syncthing inside CasaOS. In settings, I added two existing paths to a syncthing folder where all of the synced files will live. However, when I save the settings then go to my Syncthing admins screen and add my folders, I get the permissions error, even though they are already created.
What steps or process am I missing? Thanks in advance!
The error “folder path missing” tells me that either /home/ralphbrown/selbynas/syncthing doesn’t exist, or that the user running Syncthing doesn’t have access to that folder.
Also, I would not have two shared Folders with the same name. That could lead to user confusion.
According to the screenshots, Syncthing is running inside a container (probably using Docker):
Syncthing is effectively running inside a bottle with a limited view of the world outside of the container.
On the host (CasaOS) side you’ve configured – aka. mapped the storage volume – /home/ralphbrown/selbynas to /syncthing inside the container…
So because the container only sees /syncthing, you have to set it as the “Folder Path” in Syncthing.
Think of it like /home/ralphbrown/selbynas ↔ /syncthing are connected by an invisible 2-way pipe.
Update - making progress.
The “server” is a 2018 Mac Mini running Ubuntu 22.04 LTS on a NVMe drive with a 5 SSD disk array running RAID 5.
In the CasaOS host, I edited the “Host” and “Container” values as the same: /home/ralphbrown/selbynas/syncthing and then the server showed “up to date.” But now the “Remote Device” shows Disconnected. I have paused and restarted it with negative results. I think I may be overlooking one of the settings.
The container side isn’t required to match the host side, but because you had configured Syncthing to use /home/ralphbrown/selbynas/syncthing, you basically made the storage match Syncthing rather than make Syncthing match the storage.
The up-to-date is normal because from your Mac Mini’s perspective, it has all the files it needs (which according to your screenshots, consisted of zero files and folders).
According to your screenshots, the Mac Mini’s Syncthing host identification has changed from “DOIGRZ7” to “Y45BALK”, is the MacStudio still referring to “DOIGRZ7”?
Update - I uninstalled and reinstalled the Syncthing on the server (2018 Mac Mini) and have no errors. However, I am still disconnected. I did edit UFW and opened port 22000/tcp, but made no difference. The remote device (Mac Studio) host ID is 5IVZ7XA. The server host ID is 2AVLR3K. I also edited the Host and Container paths in CasaOS to include the full path to ensure the Casa app sees that Syncthing is operating outside the container. I attached screenshots to help.
Thank you for any guidance!
Also, is the API Key supposed to be the same for the Host (server) and the client (Mac Studio)?
This is not required.
I faced a similar problem. The steps to fix this can be found here : Fixing Syncthing permission errors on CasaOs (external storage) | by Fady Othman | User-friendly Linux | Dec, 2024 | Medium
Friend link (in case you don’t have medium subscription) : Fixing Syncthing permission errors on CasaOs (external storage) | by Fady Othman | User-friendly Linux | Dec, 2024 | Medium
Just a closing comment. Due to the complexity and issues involved with Syncthing deployment in CasaOS, I abandoned the project. I moved to installing Syncthing within Ubuntu (on 2018 Mac Mini i7) and now it works great.
Case closed. Thank you!
