F I N A L L Y
Now tell me it supports IPv6 and I'll be the happiest man alive
this post was submitted on 06 Jul 2025
478 points (99.2% liked)
Selfhosted
49440 readers
852 users here now
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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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!
founded 2 years ago
MODERATORS
Maybe I'm not understanding it but I can't see what I would use this for due to the 6 day issue period. Bringing a NAS up to copy data for a couple days is the only real use case I find for home users.
Because even if you pay for a static external IP from your ISP, this doesn't support using such for longer than that period right?
Let's Encrypt is meant yo be used with automated certificate renewal using the ACME protocol. There are many clients for this. Both standalone and built into e.g. Caddy, Traefik and other software that does SSL termination.
So this specific concern doesn't really make sense. But that doesn't mean I really see a use case for it either, since it usually makes more sense to access resources via a host name.
Thanks! I'll look into that, this could be useful for me then after all. This is why it's always good to ask questions
Can't it automatically be renewed?
Not sure, I just saw the 6 day thing in the article, that would be nice though
Edit: vorpal says you should be able to using ACME https://programming.dev/comment/17987211
Yay!
Yay!
This could go a long way towards fighting online censorship. One less issue when an authoritarian overreach gets your domain seized. Pretty awesome.
I would read layman discussions about why this (by context?) is good.
Domains need to be registered annually and DNS servers are needed to route traffic to them. But using an IP directly, you don't need to worry about domain registration issues that can brick your systems, and you don't have to worry about DNS providers knowing about your traffic (or maintaining your own private dns).
If it's not a user trying in a memorable domain, an IP serves much better.
I never understood why we don't use IP certificates to encrypt the domain with SNI.
What do you mean?
In much simpler terms:
Think of an IP address like a street address. 192 My Street.
There might be multiple businesses at one street address. In real life we address them with things like 1/192 My Street and 2/192 My Street, but there's no direct parallel to that in computer networks. Instead, what we do is more like directing your letter to say "Business A c/o 192 My Street". That's what SNI does.
Because we have to write all of that on the outside of the envelope, everyone gets to see that we're communicating with Business A. But what if one of the businesses at 192 My Street is highly sensitive and we'd rather people didn't know we were communicating with them? @bjoern_tantau@swg-empire.de's proposal is basically like if you put the "Business A" part inside the envelope, so the mailman (and anyone who sees the letter on the way) only see that it's going to 192 My Street. Then the front room at that address could open the envelope and see that the ultimate destination is Business A, and pass it along to them.
There's Encrypted Client Hello, supported by major browsers that does the SNI encryption. It's starting to be fairly widely supported.
192 My Street
Except that with street addresses there is such a lack of inconsistency on how they work and are written that it is funny
Currently before establishing an encrypted connection to a webserver the domain is sent to the webserver unencrypted so that the server can choose the appropriate certificate to use for encryption. That is called SNI, Server Name Indication.
Of course that's a privacy risk. There are finally protocols to fix this but they aren't very widespread and depend on DNS over HTTPS.
I think issuing certificates based on the IP and sending the domain name encrypted based on that certificate could have fixed this issue ages ago.
Can I get a cert for 127.0.0.1 ? /s
If you can get their servers to connect to that IP under your control, you've earned it
Nothing a ski mask and a little mission impossible can’t fix :)
This would actually be useful for local testing of software during development.
How many bits is a /s mask?
i
Is that the same i as the squareroot of -1?
load more comments
(1 replies)
The down votes are from people who work in IT support that have to deal with idiots that play with things they dont understand.
nah, I was once an idiot who didn't understand so idgaf
Yeah, the unfortunate part about internet security is that everyone has to start somewhere. And that means there’s always a newbie making dumb mistakes that they don’t even realize are dumb. It’s not a personal failing, unless they fail to learn from it.
It’s unfortunate they don’t know what /s means
It obviously means "secure"
We do, it's just that those users will also often go "nah, I'm just joking!" then do some shit anyways.
load more comments
(4 replies)
That's kind of awesome! I have a bunch of home lab stuff, but have been putting off buying a domain (I was a broke college student when I started my lab and half the point was avoiding recurring costs- plus I already run the DNS, as far as the WAN is concerned, I have whatever domain I want). My loose plan was to stand up a certificate authority and push the root public key out with active directory, but being able to certify things against Let's Encrypt might make things significantly easier.
load more comments
(12 replies)
Its like self signed certs with the convience of a third party
Maybe kinda, but it's also a third party whose certificates are almost if not entirely universally trusted. Self-signed certs cause software to complain unless you also spread a root certificate to be trusted to any machine that might use one of your self-signed certs.
view more: next ›