Selfhosted

60253 readers

592 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

486

Let’s Encrypt Begins Supporting IP Address Certificates (linuxiac.com)

submitted 11 months ago by KarnaSubarna@lemmy.ml to c/selfhosted@lemmy.world

63 comments fedilink hide all child comments

Who benefits from this? Even though Let’s Encrypt stresses that most site operators will do fine sticking with ordinary domain certificates, there are still scenarios where a numeric identifier is the only practical choice:

Infrastructure services such as DNS-over-HTTPS (DoH) – where clients may pin a literal IP address for performance or censorship-evasion reasons.
IoT and home-lab devices – think network-attached storage boxes, for example, living behind static WAN addresses.
Ephemeral cloud workloads – short-lived back-end servers that spin up with public IPs faster than DNS records can propagate.

you are viewing a single comment's thread
view the rest of the comments

[–] Allero@lemmy.today 16 points 11 months ago (1 children)

F I N A L L Y

Now tell me it supports IPv6 and I'll be the happiest man alive

[–] LifeInMultipleChoice@lemmy.world 0 points 11 months ago* (last edited 11 months ago) (2 children)

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?

[–] Vorpal@programming.dev 8 points 11 months ago (1 children)

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.

[–] LifeInMultipleChoice@lemmy.world 2 points 11 months ago

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

[–] Allero@lemmy.today 1 points 11 months ago (1 children)

Can't it automatically be renewed?

[–] LifeInMultipleChoice@lemmy.world 1 points 11 months ago* (last edited 11 months ago) (2 children)

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

[–] Allero@lemmy.today 3 points 11 months ago

Yay!

[–] Allero@lemmy.today 1 points 11 months ago

Yay!