Getting HTTP/3 to work on localhost is not the same as getting HTTPS to work
on localhost. A cert that gives you a green padlock over TCP can still leave the
browser silently refusing to ever speak HTTP/3 to the same origin. This writes up
why, how to diagnose it, and what actually fixes it.
It's browser-agnostic in principle but the sharp edges below are Chromium's (Chrome/Edge/Brave); other browsers differ, so test them separately.

