Selfhosted

40708 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

submitted 3 days ago by ComradeMiao@lemmy.dbzer0.com to c/selfhosted@lemmy.world

29 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 15 points 3 days ago* (last edited 3 days 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 3 days 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 3 days ago

This is the way.

Vastly superior to local dns.

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

This is specifically info about LetsEncrypt, not general SSL.

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

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

[–] fine_sandy_bottom@lemmy.federate.cc 2 points 3 days 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 3 days 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 3 days 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.