alexta69 / metube

Self-hosted YouTube downloader (web UI for youtube-dl / yt-dlp)
GNU Affero General Public License v3.0
4k stars 263 forks source link

Issue with File Deletion in Metube Deployment #285

Closed JaninaK2000 closed 9 months ago

JaninaK2000 commented 1 year ago

Hello,

I'm currently encountering a challenge with my metube deployment. Specifically, I'm unable to delete files, despite configuring "DELETE_FILE_ON_TRASHCAN" to true and not using the subfolder option. The issue persists in that the files don't get deleted from the disk and also remain visible on the website.

Interestingly, I had no problem deleting files a few days ago. In an attempt to troubleshoot, I've verified the file ownership and access rights, both of which are in order. There's also ample disk space, so it doesn't seem to be a storage issue.

Earlier today, I removed the entire content of the metube download folder, which included all videos and audio files, as well as the .metube folder. After this, I redeployed the Docker container by fetching the source again, using Portainer. Regrettably, this hasn't resolved the problem. After downloading a new YouTube file, I still couldn't delete it.

Would anyone be able to provide some insight or solutions for this issue?

My YAML file for your reference:

version: "3"
services:
  metube:
    image: ghcr.io/alexta69/metube
    container_name: metube
    ports:
      - "5000:8081"
    volumes:
      - /home/KJ/docker/mt/dl:/downloads
    environment:
      DELETE_FILE_ON_TRASHCAN: true
JaninaK2000 commented 1 year ago

I appreciate your guidance, as I initially believed this report to be unrelated due to its focus on the "DOWNLOAD_DIR" environment parameter, which I do not utilize. However, upon revisiting it with a fresh perspective, I now recognize that it indeed addresses the issue at hand. By reading it multiple times, I have come to understand that this report accurately describes the problem, regardless of my specific usage of the "DOWNLOAD_DIR" parameter.

guahki commented 1 year ago

I was delevoping the DELETE_FILE_ON_TRASHCAN functionality and as seen in #264 will revisit it's implementation anyways.

But to help with this and make sure your issue is the same, could you please provide the error message logged in the container (like in the first comment on #264). You can easily access this log in Portainer and should see a similar error message including a Traceback, when you look in the log right after triggering the issue by trying to delete a undeletable file.