Selfhosted
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:
- 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!
view the rest of the comments
Tailscale was updated with direct support for Mullvad, but since you already have Proton I'm guessing you wouldn't want to switch.
If you're using containers, you can have one container with your VPN and route traffic from specific containers through the VPN container. You can then have tailscale on the host system.
There's a quick guide on setting up the VPN part here. Tailscaile you set up normally.
I ended up doing this and it worked swimmingly! ✨
Big shout out to Gluetun VPN for making it so easy!
https://github.com/qdm12/gluetun
That's great to hear! Gluetun looks interesting, I'll check it out and maybe migrate if it works for me.
Have you figured out how to use the Mullvad VPN from Tailscale for a similar setup like you've linked? I cannot figure out how to get a tailscale docker container to properly connect to an exit node.
I have Tailscale directly installed on the host and I don't use Mullvad so I haven't tried that setup myself.
Looks like you would need to set the
TS_EXTRA_ARGSenvironment variable in your container to--exit-node= --exit-node-allow-lan-access=truewith the exit node name or ip of the Mullvad node. I haven't tried this myself though.I use a binhex-privoxyvpn container with a mullvad wireguard config in there. That's for my server and containers at least.
Do you know how it works with tailscale lock?
I haven't used that feature so I can't really say, but I don't see how it would affect it. You're not modifying anything on the tailscale side and you're not adding nodes to your tailnet, you only have the same one for the host system.
I subscribed to the mullvad addon to try it out and saw about 30+ mullvad nodes waiting to be signed, probably signed due to the lock. That got me thinking I probably want to configure the NACL so the mullvad nodes I allow on my tailnet are not able to initiate any connections to my other nodes. I didn’t see any documentation on my setup so cancelled the mullvad addon until I have time to dig into it more.