YoutubeDL-Material VS docker-qBittorrentvpn

this the one I use: https://github.com/Tzahi12345/YoutubeDL-Material

There are a few options. So far, I kinda like the way YoutubeDL-Material looks. If you're using an unRaid server, there's even a docker app you can run without configuring anything.

I'm using this one through docker, but it's a little flakey.

I've had a look at youtubedl-material, and it hasn't been updated for a while. is there anything else? Can someone confirm it does everything youtube-dl cli does?

I self-host an instance of YoutubeDL-Material and it works great most of the time. Nice frontend UI for youtube-dl.

I've been using https://github.com/Tzahi12345/YoutubeDL-Material. Seems to work pretty well.

Looking at the Github issues for the container many seem to be in the same situation as you: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues There doesn't seem to be any activity from the developer either.

I'm trying to deploy the markusmcnugen/qbittorrentvpn image but I'm having issues.

- Docker container https://github.com/MarkusMcNugen/docker-qBittorrentvpn

In terms of downloading your "Linux ISO's" automatically, I highly recommend setting up a qbittorent/vpn combo docker container, such as this one. There's also an entire set of programs with docker containers youll see referred to as the "*arr" stack, which help to manage your collection, as well as automatically download your selected media as it becomes available. These are a bit trickier to set up, but once you have everything configured and running, they are a godsend.

why not use qbittorrentvpn. Auto kill switch, etc. https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/

Hey all, I'm pretty decent with normal networking on routers and switches, etc. but I know very VERY little about iptables. I am trying to fix an issue with a qBittorrent + VPN container. The VPN includes a script setting up a bunch of iptables rules to prevent leaks outside of the VPN. Script is located here: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/blob/focal/qbittorrent/iptables.sh

Been having issues with docker ever since I first tried it, I can't for the life of me access it on the supposedly open ports. Tried setting up this docker for usage in my home plex server with arr services.

I went with the qbittorrentvpn container.

So here's the situation. I have a seedbox at home. It is currently running this docker image: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Which runs qBittorrent and OpenVPN. It's set up so that all of the torrenting traffic goes through the VPN while the rest of my seedbox can be used for other things without having to worry about the VPN. I access this seedbox using the WebUI, which works fine whenever I'm on the local network.

Have Sonarr, Radarr, Sabnzbd, qBittorrent/VPN (NordVPN just for qBittorrent, not on Usenet connections) running in containers on the NAS using Docker Compose. Had OMBI also connected, but has been troublesome as of late for me. Newshosting as my usenet provider, NZBGeek for usenet indexing, Rargb and Nyaa for torrents. Just joined a few private trackers, but those are manually managed and seeding day and night.