Results 738 comments of meeb

@Vandekieft you can delete large channels using a shell command. See: https://github.com/meeb/tubesync/issues/250

OK, so your volumes are very wrong. Try (after making sure the directories exist on the host): ``` /volume1/docker/tubesync/config:/config /volume1/docker/tubesync/downloads:/downloads ``` And drop `cookies.txt` into your `config` directory. It's not...

TubeSync doesn't use the YouTube API. It uses `yt-dlp` which itself basically scrapes the front end of YouTube. The way TubeSync works is it "flat" indexes just the video IDs,...

I meant inside the container the file needs to be at `/config/cookies.txt` which it currently is not. I don't wish to sound antagonistic here, but these are issues to do...

No, a full index only occurs once when you add a playlist or channel. Each time the indexer runs again it does a "flat" index again and indexes new media...

It is not TubeSync. Either it's going to be a) an update required upstream in yt-dlp b) the way you've exported your cookies or c) the cookies file is not...

That error just means the expected outfile doesn't exist on disk. It's not the cause of the error. The error might be anything related to either YouTube, the downloading process...

The actual error is "HTTP Error 403: Forbidden" which is YouTube has blocked you or your IP address. Does YouTube work for you in a browser off the same IP?

Ah, this may be that YouTube has marked the format tubesync is trying to download as "premium".

I probably need to see if I can filter out premium formats from being an index option as a patch to fix this.