Unsolved Failed to Create Folder in Syncthing Admin - Read Only File System
I am trying to setup syncthing between my server and laptop. However, when I try and create or use an existing directory under /mnt/, /media/, /srv/, etc. I keep getting the same read-only error from the syncthing admin panel.
I have also tried to login through console as root, and created the directories in CLI, which was successful. Below is an example.
But, when I try to add the whatever directory created in CLI in syncthing admin panel, it gives me the same error.
Last, I have also tried to chmod -R 777 the directory to see if it was an access issue between accounts, but still running into the same issue.
I am trying to create this "volume" so that I can sync things in from my Laptop, but use Nextcloud's "External Storage" plugin to have it show up in Nextcloud.
Any tutorials or videos that can help explain what could be going on?
For a start the volume would probably be mounted in
/mntwithin the app. You can check this with using the webterminal into the app. Then you have to give other users write access for that folder, so syncthing, which runs as
cloudronuser has access to create the folder and write into it. Then it worked in my testing here.
@nebulon Thanks for the reply, so I've gone ahead and tried your suggestion. So far, I haven't had success. Can you see if there's anything I am doing incorrectly?
I've added the directory to under /media/.
And originally, the /sync/ and it's sub-directories were all owned by root.
From what I understand, cloudron runs as user 1000, so I tried:
chown 1000:1000 /sync/ chown 1000:1000 /sync/server_io_mba
chmod -R 774 ./sync
But am still getting the same error when trying to resume sync in Syncthing.
As a test to see if could be a permission issue, then tried:
chmod -R 777 ./sync
But that didn't change anything.
Is there something I may have missed?
Hi guys, following up on this question.
@saint this seems pretty much what I did and got it working there. Do you know why in your screenshot the mountpoint has the red indicator that it is down?
@nebulon For some reason it says it's not mounted.
But, I am able to upload files to that Mount Point?
At this point, does it make sense to do a private login and see what may be causing this situation? Thank you.
@saint Since this is
mountpointtype, you have to SSH and check why it's not mounted using
mountcommands. I guess you set this mountpoint manually ? Check the output of
@girish So at this point, I feel like I'm grasping at straws.
I've deleted the directories, remade them and changed the mount type to "filesystem"
Now it says it's mounted.
But when I do, it tells me it is not mounted.
I feel like I'm going back-and-forth, and not sure how to move past this and get to what I actually need to do (which is setup syncthing so I can get Sketch files linked to the server.)
@saint Did you figure this one out?
To help debug, let's do this step by step:
Can you tell me what is
/media/sync? Is this really an external disk or external mount ?
You have two choices on how to mount this on the server: Either use the volumes UI to mount the external file system OR mount this by ssh'ing into the server yourself and select the
mountpointtype. In the former case, Cloudron will generate the needed systemd mount config files for automatic mounting on server reboot etc. In the latter case, you can consider it totally 'unmanaged' and you have to manage it. Do not choose the 'filesystem' type unless it's really the same disk (internally, what this does is to skip many of the mountpoint tests and thus will make debugging harder).
Once you do the above, we have to get the green icon as the status. If we don't get this, we have to figure out why. I can help further, if you can explain your setup a bit more.
Lets pick this up again now here instead of the private email support channel, so others can benefit from the information as well.
Just to be clear, Cloudron has the host filesystem and then runs apps in containers, which are isolated from the host, but get specific folders (the /app/data as well as volumes) mounted into the container. The permissions of those things will look different from the host system compared to what the app sees. This is to be expected. This is because of how unix user IDs are matched with actual usernames.
In your case what you need to do is, to open the webterminal into the synthing app instance and there perform the chown of the folder in the volume which needs to have changed permissions. The user who should own those directories is called
cloudronas that is the user with which syncthing runs.