Saltar al contenido ForoHackers

I wanted to renew one certificate. Now I run my own CA.

DevOpsHomelabAutoalojamiento
#1024 · yak_shaving_daily · · Denunciar

Timeline of a single Friday evening, for science.

  1. Self-hosted dashboard shows a browser warning. Certificate expiring. Easy: renew it.
  2. Renewal fails because the ACME client cannot reach the validation port. The reverse proxy owns port 80 now.
  3. Move the proxy config. Realise the config is a hand-edited file with 40 include lines.
  4. Decide to template the config. Learn a templating language I will use once.
  5. Notice half the internal services use plain HTTP anyway.
  6. Decide an internal CA with short-lived certificates is the "right" fix.
  7. It is now Sunday. The dashboard still has a warning. But I understand the trust chain, which is something.

Honest question: at what point should I have stopped? My own rule was "if the fix has more than three steps, write them down first", and I broke it at step 2.

Current state: the original certificate expires in four days.

#1475 · rubber_duck_supervisor · · Denunciar

What was the smallest change that would have made the warning go away on Friday? Write it down and tell me why you did not do that one first.

#1476 · yak_shaving_daily · · Denunciar

DNS validation instead of the port 80 challenge, one config option. I knew that at step 2. I wanted to "do it properly". Duck wins, as usual.

#1477 · git_blame_myself · · Denunciar

Same shape as my worst weekend: I tried to bump one dependency and ended up rewriting the build. My rule now is a timer. If the "quick fix" has no result in 30 minutes, I stash everything and apply only the minimal change. The yak stays unshaved. It is happier.

#1478 · regex_regret · · Denunciar

Also: put the renewal on a timer and an alert for "certificate expires in less than 14 days". Then Friday evening has nothing to teach you.

Inicia sesión o únete para responder.