docker-surfshark
docker-qBittorrentvpn
docker-surfshark | docker-qBittorrentvpn | |
---|---|---|
6 | 35 | |
126 | 164 | |
- | - | |
6.1 | 0.0 | |
8 months ago | 6 months ago | |
Shell | Shell | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-surfshark
-
Got my first love letter despite VPN
Looking in the issues this one doesn't have a kill switch. https://github.com/ilteoood/docker-surfshark/issues/48
-
What VPN location do you use for torrenting?
I don't believe they allow port forwarding but no issues with docker
-
Issue with openvpn
I am trying to put in place my vpn using this image and I have an error as below :
-
Netflix fights password-sharing with test of $3 “Extra Member” fee
This is the VPN I use (dockerfied) pay close attention to the examples, configuring your torrent client wrong will result in a IP leak. https://github.com/ilteoood/docker-surfshark
-
Self-hosting all these services on two Raspberry Pi 4s!
SurfShark VPN
-
Run torrent client behind VPN in Docker
Ok everything is running and seems to be ok if I check the container logs but if I switch to the website and the corresponding port I just see ERR_CONNECTION_TIMED_OUT any idea? Did it with https://github.com/ilteoood/docker-surfshark and QBitTorrent now. The surfshark openVPN container looks fine as the connection was established.
docker-qBittorrentvpn
-
Need help with WebUI on Qbittorent
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.
-
What am I doing wrong? Can't get container to spin up
I'm trying to deploy the markusmcnugen/qbittorrentvpn image but I'm having issues.
-
How much better would my torrenting experience be with port forwarding?
- Docker container https://github.com/MarkusMcNugen/docker-qBittorrentvpn
-
Titles are hard but collecting your favourite shows shouldn't be
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.
-
Docker linuxserver.io/qbittorrent: can't find how to attach a vpn network interface
why not use qbittorrentvpn. Auto kill switch, etc. https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/
-
Set Allow Rule to Access Docker Container WebUI
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
-
Losing my mind over docker networking.
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.
-
VPN and Qbittorrent containers
I went with the qbittorrentvpn container.
-
Issue - Cannot access qbittorrent WebUI from outside local network. Using a docker image that automatically puts it on a VPN. Any ideas?
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.
-
Apple Mac Plex Servers
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.
What are some alternatives?
docker-wireguard
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
openvpn-client
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
YoutubeDL-Material - Self-hosted YouTube downloader built on Material Design
docker-qbittorrent
arch-delugevpn - Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
Portainer - Making Docker and Kubernetes management easy.
tubearchivist - Your self hosted YouTube media server
arch-rtorrentvpn - Docker build script for Arch Linux base with ruTorrent, rTorrent, autodl-irssi, Privoxy and OpenVPN