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!
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CF | CloudFlare |
| DNS | Domain Name Service/System |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
4 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.
[Thread #6 for this sub, first seen 19th Jul 2023, 10:30] [FAQ] [Full list] [Contact] [Source code]
Good bot.
great bot
THE BEST bot
MVP bot
Wireguard (if you can open udp ports)
That's what I'm using, though I've used wg-easy, which made the setup, well, easy.
Yup, WG easy works pretty well
People seem to like and recommend Tailscale. I have not gotten to setting it up. My setup involves reverse proxy with treafik and my services in docker. Any suggestions on how what I need to do would be welcome.
This is the exact script I use to install tailscale on my VPN server
curl -fsSL https://tailscale.com/install.sh | sh
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf
sudo sysctl -p /etc/sysctl.conf
tailscale up --advertise-exit-node --advertise-routes=192.168.0.0/24,192.168.2.0/28,192.168.5.0/24,192.168.10.0/24Thank you for message, i appreciate the effort.
Where I struggle is the part where i need to expose my subnet within Tailscale. I don’t have any machineip:port delegated to the services anymore.
I got a domain name through CF, and have traefik generate unique url links as *service.mydomain.com that routes it to the specific service running in docker on my localmachine. It also takes care of certificates. Calling that service url only works within the local network.
In my docker compose set up, I removed all the ports as I dont access the services via ip:port. I hope this makes sense to you.
So it seems I need to configure Tailscale in such a way I can tunnel to my home network and then make the service.mydomain.com call. And that is where it got too complicated for me right now.
I also fail to understand if I need to run Tailscale native or in (the same) docker env.
You can run tailscale client on the host, not in a container. Then for the domain names, create a DNS record either in the public DNS (or I think you can do it in the internal tailscale DNS) that points a wildcard for your subdomains (*.domain.com) to the IP of the container host within the tailnet. Do "tailscale --status" on any device joined to the tailnet to see the IP addresses inside the tailnet. Then all of the devices will make their DNS request to either your upstream DNS or the internal one, they get the response back that they need to send their http request to the container host within the tailnet, it sends on the default 80 or 443 ports for http and https respectively, and then your reverse proxy handles the rest.
hi, i finally found some time to dig into this. Oddly, I think I got a functioning setup, although it did a bit differently in the end. If you may, please advise if I indeed reached completion, or I have it set suboptimal.
Open for any suggestions on this hacked attempt.
Update: yes found an issue. I can only access the services with tailscale enabled. I suspect the rewrite is causing an inproper pass through without the tunnel, as that the tailscale ip cannot be reached.
Update 2: I changed to rewrite to the local ip address instead, similar to 192.168.68.110. I think it works now when accessing within the local network without tunnel and externally with the tunnel.
Seems like you got it to work, I'm not sure about traefik requiring that cname for ssl, our setup does not. But yes the way we've done it does require that tailscale is always enabled. Even when on lan. If you've managed to setup both LAN and tailscale connections for one thing that's pretty cool.
I've been using it for maybe a year now and it's been rock solid. Highly recommended.
tailscale 100 times over
I've never had issues with my plain old OpenVPN setup
Was running Wireguard and am now in the process of changing over to Tailscale (Headscale).
It uses Wireguard for the actual connections but manages all the wireguard configs for you.
Why have you decided to switch?
Getting the configs to work with my personal devices was already a little finicky but doing that for not-so-technical family members was starting to be a bit too much work for me.
I'm hoping that Headscale will cut that down to pointing their app at the server and having them enter their username and password.
I came here to say exactly this - WireGuard is great and easy to set up, but it gets harder as you add more people, especially less technical ones, as getting them to make keys and move them around etc becomes a headache. Tailscale also minimizes the role of the central server, so if your box goes down the VPN can still function. Tailscale can also do some neat stuff with DNS that’s pretty nifty.
One thing that helped a ton with that for Wireguard (for either you or anyone else reading this) is: You can generate QR codes for a peer's full Wireguard config! So you can create the images on your computer and then a non-technical user can just scan the code to get configured.
i have pivpn (wireguard+pihole) running on a pi zero and it is rock solid
I installed OpenWrt on my home router and set up wireguard on it. If you have dinamic IP address assigned by your ISP, like me, you also have to setup a dynamic dns updater on the router. I use duckdns.org. Then you have to open the port for wireguard on the router. Here's a video guide on how to do it: https://www.youtube.com/watch?v=Bo2AsW4BMOo
Here is an alternative Piped link(s): https://piped.video/watch?v=Bo2AsW4BMOo
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source, check me out at GitHub.
My MikroTik has built in WireGuard functionality so it was an easy pick 😁
PiVPN. single line install script. Couldn’t be easier. Now if you have a shitty ISP like yours truly that can prevent you from being able to.
Tailscale all the way.
Check out Slack Nebula.I personally like it very much and used it to build a software-defined WAN to support my family's needs. I use a point to point WireGuard tunnel between my VPS and my home network to support self-hosted instances of Mastodon and Lemmy.
Not many people here use openmediavault it seems, but Its wireguard plugin is super nice.
Check netmaker for wireguard vpn if you want a ui, but its straightforward to set it up manually.
While I’ve never used it personally I’ve heard good things about cloudflare tunnel.
Depends on the use case. Cloudflare tunnels are great for accessing services, but not your network. I have a dockerised vscode instance behind a cloudflare tunnel attached to a personal domain that uses white listed emails as authorisation. Fantastic set up, can access my coding environment from anywhere with an internet connection as long as I can click the verification link in my emails.
To access my network itself though, wireguard is better. I just use pivpn (coupled with pihole for on the go adblock) on a rpi.