I had a problem similar to this and did not like the containers being binded to gluetun (problematic on docker daemon restarts, gluetun container being recreated, etc)

My solution was changing the gateway of each container to be routed through the tun. So first by having them both on the same internal network, then changing the entrypoint of the container I want tunneled to include the gateway change.

For example my entrypoint would be:

… && route del default && route add default gateway $GATEWAY_IP eth0

The container may be missing packages related to route so it may be necessary to modify the Dockerfile to install extra packages.

The reason the gateway must be set at the entrypoint is because docker overrides the gateway to correspond with the networking defined during container creation. And the entrypoint is the last thing executed before the container starts for realsies.

However gluetun also needs to work as a gateway which is done by modifying it’s iptables post-up rules file (at /iptables/post-rules.txt). I appended at the beginning of the file the following rules:

iptables -A FORWARD -i eth0 -o tun0 -s 172.84.0.0/24 -d 0.0.0.0/0 -j ACCEPT iptables -A FORWARD -i eth0 -o tun0 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A FORWARD -i tun0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT

What this does is accept any traffic from the net I have my gluetun and other container in, then forwards outgoing traffic to eth0 from tun0, and vice versa for incoming.

Sorry for wall of text this is not very straight forward :(

Forgejo my beloved 🥰🥰

That may be true. So far I got the “Firewalled” icon (the little flame) if my port isn’t forwarded for reason x or y so idk

The qbittorrrent wiki isn’t very helpful so I don’t actually know what the green globe truly entails :/

That’s just the nature of service migration; of course for people like you who are very dependent on it, it’s not a no-brainer, but for anyone who wants to start hosting one of the two, yes it will be.

In your case yes Plex is more appropriate but at the same time the clock is ticking for Plex if they continue on this route…

I don’t know why everyone in the selfhosting community still even mentions Plex or uses it.

It’s closed source, not free; Jellyfin is a no brainer yet people still go to Plex??

Librewolf (privacy focused firefox fork) syncing the user folders with Syncthing maybe?

See this issue on their github repo: here

Basically from what I understand there’s loads of unauthenticated api calls, so someone can very easily exploit that.

If they just supported mTLS in their clients it wouldn’t be an issue but oh well :(

Oof was looking to start selfhosting this but it has no client Linux support and has a subscription 😬😬

Made me learn about Archiveteam, thanks :D

You’re right actually it’s not native I don’t know what I’m on about 😅 Still it’s much easier to have a baked in terminal app than having to install proot on top of termux, hopefully it will have less of a performance impact than proot as well.

Just installed arch with chroot on my old rooted phone a week ago.

Seeing this is great because it means there’s no need for complicated workarounds or even root access! Plus the distro runs natively and not with difficulties like with chroot :D

yep

In my opinion it’s the best solution because there’s a really low attack surface plus it makes it easy to control which device has access to which services.

Not any in particular but mTLS is essentially just a reverse proxy (like nginx) asking a client for a certificate to be able to access the service behind it.

There are quite a few guides out there, so choose one for your reverse proxy of choice!

Tailscale is simpler but when you’re accessing from devices behind VPNs like I do mTLS is a lifesaver.

I use DAVx⁵ for caldav (supports mTLS)

I find mTLS cool too :P

In terms of being a pain it’s not that bad with nginx in my opinion. I can just build my own certificate for each service I expose or you use a common one, giving read only access to the key for my nginx containers and in two lines in the .conf it’s sorted.

mTLS with a reverse proxy!

How exactly does stuff get broken? Never rly had a problem bumping up the version in docker. The only issue has been the playstore version taking longer to push updates sometimes for the mobile apps.

I have a project on Forgejo and I’ve needed to set up a runner for compilation but I’ve been very confused so far on how everything works.

All I’ve been able to do is make a runner and connect it to my Forgejo instance, but I didn’t really know what to do from there.

Where are you located? If in the UK, BargainHardware has pretty good deals when they get a bunch of the same HDD model in stock.

I was having a lot of trouble keeping port forwarding stable before this change with protonvpn too. Probably the best change I’ve seen with gluetun so far!

Yes, if a port is set in the port forwarding section for the qbittorrent preferences in the webui (once one is set it stays until changed), the green globe means it’s working.