Selfhosted

60542 readers

350 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. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )

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

How to get local SSL and use your public domain for local internal subdomains? (lemmy.dbzer0.com)

submitted 2 years ago by ComradeMiao@lemmy.dbzer0.com to c/selfhosted@lemmy.world

30 comments fedilink hide all child comments

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

[–] wildbus8979@sh.itjust.works 16 points 2 years ago* (last edited 2 years ago) (2 children)

You can use the DNS verification method. Either using nsupdate with bind or what ever protocol your DNS provider and favorite ACME (certbot, acme, lego, etc) utility supports. As long as your DNS server is publically reachable that will work, even if the subdomain itself doesn't exist publically.

[–] thumdinger@lemmy.world 6 points 2 years ago (1 children)

This is what I do as well. I have a public DNS record for my internal reverse proxy IP (no need to expose my public IP and associate it with my domain). I let NPM reach out to the DNS provider to complete verification challenge using an account token, NPM can then get a valid cert from Let’s Encrypt and nothing is exposed. All inbound traffic on 80/443 remains blocked as normal.

[–] fine_sandy_bottom@lemmy.federate.cc 3 points 2 years ago

This is the way.

Vastly superior to local dns.

[–] just_another_person@lemmy.world 2 points 2 years ago (2 children)

This is specifically info about LetsEncrypt, not general SSL.

[–] wildbus8979@sh.itjust.works 6 points 2 years ago* (last edited 2 years ago)

Yes my answer is for use with Let's Encrypt.

[–] fine_sandy_bottom@lemmy.federate.cc 2 points 2 years ago (1 children)

I don't really understand what you're getting at. The answer to OPs question is to use letsencrypt like everyone else.

[–] just_another_person@lemmy.world 3 points 2 years ago (2 children)

They literally didn't mention LE at all.

SSL is not LetsEncrypt, if you didn't know.

[–] Max_P@lemmy.max-p.me 4 points 2 years ago

To add: a lot of cert providers also offer ACME so while the primary user of ACME is LetsEncrypt, you can use the same tech and validations as LetsEncrypt on other vendors too.