Access denied due to failsafe; check server log #163
-
Hi, Thank you, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
I don't know anything about unraid so I can't help with the details, but here's the technical explanation: The problem is that you are telling the docker image that it should read and use a particular copyparty config file, but you are not giving it the config file you are telling it to load. The UI is saying you should check the serverlog, and you will find something similar to the following error there: EDIT: Like the error message says, it could also happen if you do give it a valid config file, but without specifying any volumes inside the config file. (in copyparty, a volume is the filesystem-path to a folder that you want to share from the server filesystem, and what name you would like to give it in the copyparty web-ui) |
Beta Was this translation helpful? Give feedback.
-
Hi, This is deployed as a docker by using templates in which you can enter some variable as you would do with Docker compose, so at the end it's like using a Docker. here is the output of the logs (those from UnRAID), and yes I see the sentence you've highlighted in RED.:
a path is defined behing /w in read/write... so it seems that it just doesn't work. Thank you for your help. |
Beta Was this translation helpful? Give feedback.
-
Hi, I could make it work by adding "-v .::rw" |
Beta Was this translation helpful? Give feedback.
please beware that this disables the authentication system, and will share the "working directory" with read-write permissions (and just those permissions, not move/delete) for ALL USERS without authentication. Note that the meaning of "working directory" depends on UnRAID's choices while integrating copyparty.
The better alternative is to give copyparty a config file; this will also make the logfile have colors like in my screenshot (the default is black and white). Here are two examples: