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!
Tailscalar here. Use tailscale serve. It is a reverse proxy inside tailscaled. It will handle HTTPS certificates for you too. As an example, here's a sample HTTP server proxied to both my tailnet via tailscale serve and to the world with Funnel.
Also as far as I know you need to use Serve in order to use Funnel.
This does seem like the easiest option so far, i'll try to play around with this, thanks!
No prob! If you run into any problems, feel free to DM me or /u/tailscale@hachyderm.io. We're more than happy to help.
The easiest way I found is to use caddy which already has tailscale support and will fetch a certificate for hosts behind your tailnet address.
I might give Caddy a go if the response from @Mara doesn't work for me, thanks!
It's possible to host a dns server for your domain inside your tailnet, and offer dns responses like: yourwebserver.yourdomain.com = tailnetIP
Then using certbot let's encrypt with DNS challenge and api for your public dns provider, you can get a trusted certificate and automatically bind it.
Your tailnet users if they use your internal dns server will resolve your hosted service on your private tailnet ip and the bound certificate name will match the host name and everyone is happy.
There's more than one way though, but that's how I'd do it. If you don't own a domain then you'll need to host your own private certificate authority and install the root authority certificate on each machine if you want them to trust the certificate chain.
If your family can click the "advanced >continue anyway" button then you don't need to do anything but use a locally generated cert.
Note my bias as I work for Big VPN (Tailscale), but I don't think that teaching people to ignore security warnings is a good thing to do. The CA system is kind of a scam in general, but I think that at least in its current implementation it's better for us to encourage people are aware of those errors and what they mean.
As the sacred texts say: self-signed certificates beget the use of curl -k beget the use of self-signed certificates.
Yeah I also don’t want my folks to have to “ignore” the warnings either. So will defo have the https set up before giving them access.
Not possible without a domain, even just "something.xyz".
The way it works is this:
Now, to get that experience you need to meet those conditions. The machine trying to browse to your website needs to trust the certificate that's presented. So you have a few ways as I previously described.
Note there's no reverse proxy here. But it's also not a toggle on a Web server.
So you don't need a reverse proxy. Reverse proxies allow some cool things but here's two things they solve that you may need solving:
But in this case you don't really need to if you have lots of ips since you're not offering publicly you're offering over tailscale and both Web servers can be accessed directly.
Thanks for the detailed answer, I was able to solve my problem just with what /u/mara said suggested above :)
Yeah I do not have a domain. I did before but for some reason i struggled to wrap my head around reverse proxies and domains. And I prefer to not have to pay for yet another service as I'm just a student :P
You can get domains for a few dollars per year. Go to tld-list.com and sort by renewal price.
When I was in school, I used to pay for domains by doing online surveys that paid $1 per survey. Not sure if that's still a thing these days.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| HTTPS | HTTP over SSL |
| IP | Internet Protocol |
| SSL | Secure Sockets Layer, for transparent encryption |
| VPN | Virtual Private Network |
[Thread #183 for this sub, first seen 3rd Oct 2023, 10:55] [FAQ] [Full list] [Contact] [Source code]