this post was submitted on 19 Dec 2024
31 points (94.3% liked)

Selfhosted

40672 readers
325 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 2 years ago
MODERATORS
 

For instance how can I use my *.domain.com SSL certs and NPM to route containers to a subdomain without exposing them? The main domain is exposed.

you are viewing a single comment's thread
view the rest of the comments
[–] ComradeMiao@lemmy.dbzer0.com 1 points 5 hours ago (2 children)
[–] possiblylinux127@lemmy.zip 2 points 2 hours ago* (last edited 2 hours ago)

I don't get it. Npm is a package manager. It doesn't handle certificates.

You need a DNS service like route 53 (AWS) or similar where let's encrypt connects via an API and creates the DNS token.

[–] MangoPenguin@lemmy.blahaj.zone 1 points 5 hours ago

Then you're all set, issue certs over DNS-01 challenge in NPM, and create records in your local DNS server that point to the NPM IP for each domain you want to use.