this post was submitted on 16 Feb 2024
40 points (84.5% liked)

Selfhosted

40050 readers
854 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] BrianTheeBiscuiteer@lemmy.world 1 points 8 months ago (3 children)

Is this only for public facing services then? I have little desire to expose my services except through tailscale or something like that.

[–] double_oh_walter@feddit.nu 3 points 8 months ago* (last edited 8 months ago) (1 children)

No! If you have a domain and can do DNS* verification you can get fully functional certificates to use on your internal network.

*Doesn’t have to be DNS, but then you’d need to expose http to the internet for verification.

[–] BrianTheeBiscuiteer@lemmy.world 1 points 8 months ago

Reading a post on the LE forum it sounds like smallstep might be closer to what I need.

[–] lemmyvore@feddit.nl 2 points 8 months ago

The alternative is to offer the Let's Encrypt bot access to your DNS service, typically in the form of an API token which you revoke after the bot verifies the domain. Access to the API is not needed for subsequent cert refreshes, only the first time.

The bot (or the proxy you use) needs to support the API of the DNS you use, naturally, but they support a wide variety of the most well-known ones.

[–] vividspecter@lemm.ee 1 points 8 months ago

Just to add to the other comments, you probably want to use a wildcard cert so you don't need to individually certify each subdomain (or expose them at all).