492
submitted 1 month ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 48 points 1 month ago

Browsers barf at non https now. What are we supposed to do about certificates?

[-] [email protected] 10 points 1 month ago

@solrize @thehatfox get a free wildcard cert for your domain and use it just like any other. nothing new, nothing different. I have those running on LAN-only hosts behind a firewall and NAT with no port punching or UpNP or any ingress possible.

if you don't want to run a private CA with automated cert distribution (also simple with ansible or a few tens of LOC in shell or python), the LetsEncrypt is trivial and costs nothing -- still requires one to load the cert and key onto a server though, which is 2/3 of the work vs private CA cert management.

[-] [email protected] 3 points 1 month ago

How do you propose to get LetsEncrypt to offer you a certificate for a domain name you do not and cannot control?

[-] [email protected] -3 points 1 month ago

@JackbyDev Why would that be a question at all? Buy a domain name and take care of your dns records.

that's an odd way to say that you don't own any domains. that's step one, but does it even need to be said?

[-] [email protected] 3 points 1 month ago

You cannot buy .internal domains. That's my point.

[-] [email protected] 3 points 1 month ago* (last edited 1 month ago)

Private CA is the only way for domains which cannot be resolved on the Internet

load more comments (44 replies)
this post was submitted on 08 Aug 2024
492 points (99.0% liked)

Selfhosted

39275 readers
238 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