Gah, of course Chrome would do a major update right after I say that on HN – the QUIC protocol is in motion and latest Chrome probably only supports the newest version(s) of QUIC, which I suspect Caddy will support in the next release.
So this is why quic isnt working for me? Im also getting this http://puu.sh/sWEZj/ea069f3ecf.png on my version. I made a post on this forum a few days ago about quic because im doing my thesis on the comparison of quic+http2 vs http1.1/tcp so if its broken it basicly means im screwed? Or is there a way i can get it to work? (Assuming it hasnt been patched yet i seem to also have 0.9.3)
Edit: It is ofcourse also possible im simply screwing things up on my end.
Its pretty late here but since i was still awake and saw that the new patch is here i wanted to try it out and see if my quic is working now. It does not seem to be working but maybe i am missing something.
The setup seems to be correct from what i understand. Maybe it is enabled but im just looking at the wrong things?
I get this with page inspecting http://puu.sh/sX2sS/051d26ce58.png and no active events at chrome://net-internals/#events&q=type:QUIC_SESSION%20is:active
Is there something obvious im missing? Is it working for anyone else?
Ow, i didnt know that! I do hope thats the problem. Im not really sure why its unsecure though. Im using tls self_signed in the caddy file is this why its not showing up as valid? When i enter my email adress i can see ERR_SSL_PROTOCOL_ERROR in the google chrome console but im not really sure where to look for a better run down of what went wrong. Maybe because i dont have an account with that email with “a trusted CA”? Is there someway i can tell my browser to trust certificates from that ip/server, could i get it to work like that?
Wel it seems like it might not be the fault of the certificate. I was able to allow the self signed certficate but still no luck with quic. http://puu.sh/sX7mM/2036e124a0.png . Pretty darn lost on why its not working now but its 01:30 here in belgium and i have classes tomorrow so im off to bed and il worry about it some more tomorrow afternoon.
Because your system doesn’t trust self-signed certificates. Even if your browser does, the QUIC library needs to trust it as well through your system roots.
You could always download the certificate while the server is running and add it to your trust store, but you’ll have to do it again when you restart the server; better yet, can you use a real hostname?
I think i did it correctly but still no luck. I followed this guide on how to add a certificate to the trusted root certification authorities store for my local machine Manage Trusted Root Certificates | Microsoft Docs but im still getting this http://puu.sh/sXyTp/ef45fedd97.png im not sure if i need to do it somewhere else aswell. Maybe the quic library thing you talked about still doesnt trust it ?
I assume its working for you so i must still be doing something wrong. Maybe what i did still doesnt make it count as a " real, trusted certificate" but im not sure how to make it a real trusted certificate if thats the case
Hmm interesting, at first it didnt work for me because of a plugin called “Cache killer”. When that plugin is disabled i do get quic on your website. Disabling it did not seem to help my site however so there still seems to be a problem on my end.
Im happy to say this https://github.com/mholt/caddy/issues/1432 finally fixed it for me. So for people who are having trouble getting quic to work and stumble upon this thread, disable all your chrome plugins (one plugin makes quic not work for me) and it seems like u cant get it to work with a self singed certificate.
What did you do to fix it Anton? The issue that had a solution for you seems to be deleted … I enabled quick in caddy startup command, opened port 443 UDP on router and firewall and I enabled the quic flag in Chrome (v56).
In the response headers I see quic but a chrome plugin states it’s not quic enabled (which it does show in gmail and Matt’s website (https://matt.life/))
