Selfhosted

40329 readers

444 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Best way to create my seedbox? (lemmy.world)

submitted 10 months ago by Haha@lemmy.world to c/selfhosted@lemmy.world

34 comments fedilink hide all child comments

Hey guys, i want to ask you all how you seed your torrents. I’m considering either using proxmox to create a seedbox or to build a dedicated machine with a vpn that will seedbox.

What VPN do you also use to seed? I have mullvad, for personal use but for seeding it doesn’t have port forwarding.

Thanks! :

you are viewing a single comment's thread
view the rest of the comments

[–] Haha@lemmy.world 1 points 10 months ago (2 children)

I read a bit about gluetun, why did you pick it?

[–] sailingbythelee@lemmy.world 3 points 10 months ago (1 children)

I also use Gluetun. I consider it more or less mandatory for container--based torrent client setups. The idea is that you run your torrent client in a docker container and you run your VPN in a Gluetun docker container. Instead of opening up your torrent client ports directly for internet access, you make it a "service" of the Gluetun container. When your VPN drops connection, the Gluetun container loses connection, which means that your torrent client is also blocked. So, this setup provides a "fool proof" kill switch that prevents your torrent client from accessing the internet except through your VPN. This is as opposed to the kill switch built in to your VPN client, which tends not to be fool proof, particularly when using containers. I found this out the hard way.

[–] Haha@lemmy.world 2 points 10 months ago (1 children)

Very good to know as i wanted a killswitch too when i go off vpn somehow! I saved that comment :)

[–] sailingbythelee@lemmy.world 1 points 10 months ago (1 children)

Here is the guide I used to understand and setup Gluetun. Enjoy!

https://www.smarthomebeginner.com/gluetun-docker-guide/

[–] Haha@lemmy.world 2 points 10 months ago

Thanks a bunch!! :)

[–] jvrava9@lemmy.dbzer0.com 1 points 10 months ago* (last edited 10 months ago)

Was the best option that I found :)