Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About DrAwesome

  • Rank
  1. OK, so I tried deleting the container and all cache data and even the directories themselves. I remade them, starting from scratch and opening up the permissions again to 777. I can now get the GUI version to work when setting the destination output to /output as described above, but the watch folder still does not work. Same error as before. This makes me think that maybe one of my routes is bad for the watch folder, but I can't see it myself. Any help?
  2. After further investigation, my Umask value for the whole directory is set to 0000, which shouldn't cause an issue, as I understand it.
  3. I have not done that. How can I change that? I tried using the docker safe new permissions from common problems plugin, but that didn’t help.
  4. Yes. The access mode is set to read/write.
  5. Thank you for the reply. However, the error still occurs when doing that. The same error occurs that is shown in the last screenshot that I posted above.
  6. I'm sorry if this question has already been answered before, but I couldn't find a solution for me after reading through the forum and trying various things suggested. HandBrake was working great until about 6 months ago. Then it stopped working. I couldn't figure out why, at the time, but I wasn't really needing to use it, so I left it alone. Fast forward until today, it still doesn't work, but now I would like to use it. So, I know it can work. It just doesn't any more. The GUI and the watch folder stopped working at the same time and I believe have the same problem. The watch folder does not work. detects files fine, but cannot execute. Log error shown below. Sounds like a permissions issue to me. I have verified that the permissions are appropriate, the owner/user are set to nobody (99), and I even blasted the entire share with a 777 permissions, to no avail. When trying to create a new folder in the GUI, I get an error that says the directory is read only. The result is the same despite changing docker paths to new folders, opening up SMB or AFP settings, changing files to be converted or presets used, and even deleting and reinstalling the docker. I'm sure that I'm missing something, I just don't know what it is. Can you help? Thank you