@schiffheimlich
Nothing here yet.
Nothing here yet.
May 12 · 2 min read · A client reached out with a weird TLS problem. Their Caddy certificate kept expiring even though Caddy should automatically renew it. No errors in the logs. Everything looked fine from Caddy's side. The cert was just... expired. We went through the u...
Join discussion
May 10 · 2 min read · When you spin up a new VPS or cloud instance, the first SSH connection is a trust problem. Your client has no prior record of the server host key, which means any man-in-the-middle attack between you and that machine will succeed silently. Nobody tel...
Join discussion
May 9 · 2 min read · Here's a fun one. A few weeks back a developer was testing Cursor with Claude hooked up to their Railway account. They wanted to clean up some old staging resources, typed something like 'remove the old test deployment,' and watched in horror as the ...
Join discussion
May 8 · 2 min read · Here's a problem that keeps me up at night when I'm spinning up new VMs: that very first SSH connection to a fresh server. There's no host key in known_hosts yet, so you get that nasty 'WARNING: POSSIBLE DNS REBINDING ATTACK' message, and more import...
Join discussion
May 7 · 3 min read · A TLS certificate expired on a Caddy instance. The site was up, DNS was resolving, and Caddy was running. The cert just... lapsed. The issue turned out to be systemd-resolved. What happened The server was running systemd-resolved as its DNS resolver,...
Join discussion