please help nonlinux user

in Cubebackup doker there is a note NOTE: You must set permissions on the appdata folders.

 

Quote

 setup webserver.StartRPCServer(127.0.0.1:43489)
 setup checkChown() chown required

 

found something in google but it doesn't work

chown -R nobody:users /mnt/user/appdata/cubebackup

chmod -R 777 /mnt/user/appdata/cubebackup

? did you use the default pathing in the docker?

did you open the unraid web ui and run the commands?

stop all dockers.
go to Unraid web UI > toos > docker safe permission.

this will set that across for you.

Edited December 16, 20241 yr by bmartino1

yes, i use default paths

i ran "docker safe permission" but still getting chown required

Which docker did you install?

 

Please post a diag of unraid

 

Please show the log error form docker.

hard to say you clearly have a permission issue

This could also be a owner write issue in google workspaces...

https://support.google.com/a/answer/60781?hl=en

 

Review there docs:

https://www.cubebackup.com/docs/tutorials/error-message-and-troubleshooting-steps/

its CubeBackup-GoogleWorkspace

I haven't run the setup yet, I don't want to mess up
 

docker error :

 

Quote

 setup webserver.StartRPCServer(127.0.0.1:43489)
 setup checkChown() chown required

 diagnostics attached

swunrsrv-diagnostics-20241218-1737.zip

i'm still reviewing diagnose.
It is unusual to see a docker RPC error. as in unraid this is more aimed at a issue in nfs export.... Have you restarted the unraid system?

This is what's in the log by clicking log of that docker as the diag helps, but its not the full picture.

you seem to have a emhttp issue with choow onthe fuse os atempting to fix ownership at the share / mount level.

The system logs reveal several chown commands issued by emhttpd, attempting to change ownership of folders like /mnt/user/CubeBackup, /mnt/user/syncthing, and /mnt/user/rpi. These commands suggest that Unraid is managing file permissions as expected.

 

Since there are no explicit rpc error messages, the issue might be related to folder permissions or a configuration in CubeBackup. Consider these steps:

 

ls -l /mnt/user

how did you make "/mnt/user/CubeBackup, /mnt/user/syncthing, and /mnt/user/rpi"
double check the share tab and make sure they are set correctly for storage.

 

chmod 777 -R /mnt/user
chown nobody:user /mnt/user

you may eeed to add a uuid / guid to the docker.

edit the docekr whil;e off ad at the bottom add 2 variables

I am facing the same issues following the standard process and also trying out different things from google and ChatGPT without success. Did anybody get this App to run without errors?

This got it working for me. Tried every combo of different security permissions but it didnt work.. Put these commands into unraid terminal after starting the docker container

 

#Create blank config.toml with correct permissions
touch /mnt/cache/appdata/cubebackup365/cfg/config.toml

#Change permissions on folders to owner root.
chown -R root:root /mnt/user/appdata/cubebackup365
chmod -R 777 /mnt/user/appdata/cubebackup365

Edited May 1, 20251 yr by WillR

I finally found some time to play CB.  Upgraded Unraid to 7.0.1. "checkChown() chown required" message is still there, but setup finished without any problems and backup is running smooth. i like this app and price so far.