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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I currenly reside in a country with strict piracy rules but also have access to the internet in a country where piracy is not enforced. I want to setup a VPN and route qBittorrent's traffic through it. The idea is to do something like this:
I am fresh to selfhosting and most of the time have no clue how to achieve what I want. So far I have tried Tailscale but I think it won't work how I want it to. If it helps, I have domain name registered. Can anybody point me to the right direction?
Doesn't firejail only allow sandboxing to an actual eth or wifi interface, and not a wireguard one? I've tried this before with firejail, and hit this wall.
Damn you're right, it doesn't work out of the box like I expected. Have to admit that I never used it this way around. But it should work with --netns (network name spaces) which Wireguard uses: https://www.wireguard.com/netns/
Afaik it should work if you move Wireguard to it's own namespace and than start qBittorrent with the new namespace (should even be doable without firejail).
@imetators @lemmy.dbzer0.com sorry for chasing you down that rabbit-hole, it sounded easier in my head