Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Conversation

Notices

Embed this notice
Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Friday, 01-Aug-2025 08:43:24 JST Jan Wildeboer 😷:krulorange:

New (long and nerdy) blog post: "Be the LetsEncrypt in your homelab with step-ca" at https://jan.wildeboer.net/2025/07/letsencrypt-homelab-stepca/ where I explain my homelab setup with its own CA (Certificate Authority) on RHEL 10 (Red Hat Enterprise Linux) machines.
Replies to this toot will show up as comments on the blog post.
#SelfHost #CA #x509 #RHEL #LetsEncrypt
In conversation about a year ago from social.wildeboer.net permalink
Attachments
1. Domain not in remote thumbnail source whitelist: jan.wildeboer.net
  
  Be the LetsEncrypt in your homelab with step-ca
  
  So you have a Cute Homelab and you want to use it to secure your services and containers with x509 certificates? But your homelab isn’t on the internet, so you can’t simply use LetsEncrypt? Well. You can become your own LetsEncrypt and hand out certificates with certbot. You “just” need to run your own CA (Certificate Authority). Sounds frightening and complicated? It kinda is, but not really when you use step-ca, an open source solution that you can run in a container.
- Embed this notice
  Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Friday, 01-Aug-2025 20:43:13 JST Jan Wildeboer 😷:krulorange:
  - Mauricio Teixeira 🇧🇷🇺🇲
  @badnetmask Good point! I have added a "policy" block to limit cert creation. I hope it is correct? I tested it on my setup and it seems to do what I expect.
  
  In conversation about a year ago permalink

Public

Conversation

Notices

Feeds