I think something's off with the http/3 option in the SSL panel.

Some clients were reporting issues w/ insecure connection errors on some of the websites. I noticed all of them were on iOS, and seemed to be using either the Google-app's built in browser or Chrome.

I’m not exactly sure what’s happening but looking into it, it seems like the site loads the first time, and has a header indicating http/3 support. On subsequent visits it then tries to connect over http/3, and fails resulting in the insecure connection error. Most browsers gracefully fall back to h2 but the Google browsers on iOS do not.

Checking the site on various desktop browsers works all the time, but devtools always shows h2 as the protocol instead of h3.

http3check.net shows that http/3 is supported, but then returns a 404 not found error.

Removing the old certificate and creating a new one with http/3 turned off clears the error on iOS Chrome - though it is quite persistent as I think the original header gets cached.

Edit w/ info on how to reproduce the error

This seems to be a reliable way to reproduce the error:

• Setup a site with a new SSL + enable HTTP/3
• Visit the website on iOS Chrome → works just fine
• Force quit Chrome and re-open
• Visit the site again → insecure connection error

The handful of sites I'm running that had HTTP/3 turned off already work fine. Any of the sites that have HTTP/3 on consistently fail when doing the above steps.