ooof thanks for sharing, I deploy Caddy for HTTP/3 which is useful for $job and I roll my own builds with some plugins so I haven't jumped to 2.7 yet
Just upgraded to #Caddy 2.7.2 on FreshBSD.org. It didn't last very long:
Successfully started Caddy (pid=15076) - Caddy is running in the background
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x907c10]
Looks like it's HTTP/3 related, which I've disabled for now: https://github.com/caddyserver/caddy/issues/5680
Imagine inventing a programming language in 2009 and it still does this sort of thing...
Discussion
No replies yet.