You are correct the FIREWALL_VPN_INPUT_PORT is to allow the port to be opened on the vpn side of the connection. You will add the port provided to you from Air as that variable and set the same port within qbittorrent.
You should not be adding the port 6881 anywhere, example compose below from the guide on my website.
Hmm I see, I had the port in 6881 docker-compose and used it for the incoming connections in qBittorrent for 2 days or so, would that get me a notice from the ISP? I’ve been using network_mode: “service:gluetun” the whole time and the curl https://ipleak.net/json/ from the qBittorrent container console always delivered the ip of my vpn.
I’m not involved either. I definitely would never do anything so abhorrent and inconsiderate of rights holders who purchased their copyrights fair and square.
I have PIA and have so far been very pleased. If you are concerned about owner, maybe just go 1 year at a time, so you can pivot elsewhere if their reputation changes.
I DO get captcha on Google sometimes. But it just convinced me to switch to DDG and never looked back.
I use automatic torrent management mode with qBittorrent for most things and set it to seed every torrent for 40 days (iirc). If I had unlimited storage space, I’d probably seed forever, but I found that 40 days works well for me.
Also, don’t use a Debrid service. These services just leech requested torrents and then instantly stop seeding (if they even upload during download, not sure). This is bad for torrent health on public trackers, and will quickly get you banned on private trackers.
If you seed from the same drive where you store your files, learn the art of hardlinking any torrents you’ve downloaded (that don’t require unpacking), and you can seed without taking up too much more space on your drive.
Hard links are essentially links that point to the same file. When one link is deleted, the other still exists and it is only when the last hard link is deleted that the underlying file is actually deleted.
Anyone else has cross-seed configured? I started the process, created the config.json and now I need to configure it. It would be useful to see how someone else set it up and why. I feel the provided explanations in the config file are just a notch too high than what my hobbyist mind can understand atm. Then there’s direct client injection or autotorrent2 I still have to figure out.
For those curious, cross-seed allows you to take what you are seeding and find where else that torrent is and seed it there too, within a defined set of trackers. Perfect for sharin’ ye booty, arr!
Sounds like you already have a good start on this, but I wrote up instructions for myself when I move computers. I use calibre and an older version of the Kindle for PC app. DM me if you need help.
Maybe a dumb question, but how is this better than having your files on a nas? I have a nas and just play my media files from there on my tv and laptop. What do I get from having jellyfin?
Kodi/XBMC has been providing that for like 20 years though…
What jellyfin does provide that Kodi doesn’t is on the fly transcoding for watching on mobile device and remote access. If you don’t need that, Kodi might be a better choice providing a far wider array of features.
You’re not wrong but there are still drawbacks to Kodi where Jellyfin ends up being better. In my use case, with 5 tvs in the house, 2 are hooked up to Nvidia shield tvs but the other 3 are Chromecast w/ Google TV which have very limited storage unless I want to spend a fortune in hubs for each one to add a USB drive or micro SD.
With kodi installed I would regularly hit the storage limit of the device and have all kinds of weird bugs. Just as an example I had my daughter set up with a kids only account, but account switching would cause Kodi to become unresponsive for anywhere from 30 seconds to having to do a hard reset of the device. Jellyfin gives me the same access to my library with a lighter, more streamlined, persistent interface across devices and with easy and fast profiles. It still allows me to keep a pi as the host so the whole setup is low power (important for me as we’re on solar, every watt helps!)
I don’t really need the Kodi plugins I used to have if the main purpose of streaming my local content isn’t smooth and simple for the family. This is coming from a long time XBMC user, I’ve been running it since my original modded Xbox in the early 2000s.
Then you are doing it wrong. I have three instances of Kodi, one of them on completely hard drive less machine booted via PXE, the other two are Pis with minimal is on an SD card. All the media’s are stored on a NAS, and all the metadata is shared between the instances on MySQL, all of it (profiles, views, etc) shared across all the instances.,
“Wrong,” or a matter of preference and willingness to sink time into the project. Your setup sounds great, but it’s also easy enough for me to do a simple apk install for Jellyfin and host it on the pi that already has my network shares vs spending the time setting up a database and a local DHCP server etc. etc. Netboot is great but with a fraction of the setup with Jellyfin my needs were met, which was my original point. Also how many end users will take this route? Realistically not many.
Don’t get me wrong this was something i’d totally be into a decade ago so I get where you’re coming from, love the idea of having the metadata and everything scraped centralized, but what I have works and it’s easyyyyyyyy 🤷♂️
I just recently set up jellyfin as a way for my family to access the stored media outside of my house. Our current Networking setup doesn’t play nicely with VPNs so this was an easy way to do that.
But, Jellyfin/Plex has the advantage you get a nice pretty “app” that works on your TV/Roku/AndroidTV/etc. It handles transcoding if needed, keeps track of what you have watched, and lets you know when new things pop up.
The only ports you need to expose from Gluetun are the ones for the webUI for each of the containers you’re running thru it. You should never expose the port for incoming connections since that would make your torrenting traffic avoid the VPN.
Your qBittorrent and *arr containers should be run with network: “service: gluetun” in your docker-compose file (assuming you’re using compose)
Nope, and it’s awesome. I2P works similarly to tor except instead of being discouraged, there’s a torrent client built in. Only down side is as it’s an entirely P2P network with alot of hops (more than tor) it’s quite slow.
The container connects to the VPN and only the VPN, now you can route whatever docker containers you want through that container as a network. Now that one VPN connection can serve any container you want.
I use gluetun to route traffic from some of my containers that need a VPN. qBittorrent, Jackett etc. Some containers dont have the option to configure a proxy so you’d have to setup a VPN client within a container which isn’t ideal. With gluetun its easy to attach a container to it and it just works
Why isn’t it ideal? I’m currently using this setup with containers routed through a gluetun container connected to a vpn via wireguard, and it seems to be working fine. I’ve verified using curl inside the relevant containers to query an IP checker and I’ve also used a torrent IP checker to confirm my torrent client isn’t leaking my IP.
Also the biggest benefit; You only need 1 VPN connection and 1 key pair for gluetun to connect everything. Most VPN providers limit the amount of active simultaneous connections. If you have lots of containers that need it then it’s not possible
piracy
Aktywne
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.