this post was submitted on 29 Dec 2023
91 points (93.3% liked)

Selfhosted

39964 readers
532 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
[–] [email protected] 0 points 10 months ago* (last edited 10 months ago)

You are completely correct...for normal certs. Internal domains require a wild card cert with DNS challenge.

This video explains how to set it up with traefik

https://youtu.be/liV3c9m_OX8

I'd bet caddy can do something similar.

Basically you have:

  1. Seafile.domain.com -> has it's own cert
  2. *.local.domain.com -> has its own cert but the * can be anything and the same cert can be used for anything in place of the star as many times as you want and therefore doesn't need to be internet accessible to verify. That way vaultwarden.local.domain.com remains local only.