Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
litespeed_wiki:config:enable_quic [2019/01/09 20:51] Lisa Clarke [Possibly Google Chrome not enabling QUIC by default] |
litespeed_wiki:config:enable_quic [2019/01/24 17:55] qtwrk [How to Open UDP Port 433 at the Firewall] |
||
---|---|---|---|
Line 11: | Line 11: | ||
- | ===== How to Open UDP Port 433 at the Firewall ===== | + | ===== How to Open UDP Port 443 at the Firewall ===== |
[[https://en.wikipedia.org/wiki/QUIC|QUIC]] runs a stream-multiplexing protocol over Transport Layer Security (TLS) on top of UDP instead of TCP. Be sure you've enabled the port with both TCP //and// UDP. Most of the time, TCP 443 is enabled. | [[https://en.wikipedia.org/wiki/QUIC|QUIC]] runs a stream-multiplexing protocol over Transport Layer Security (TLS) on top of UDP instead of TCP. Be sure you've enabled the port with both TCP //and// UDP. Most of the time, TCP 443 is enabled. | ||
Line 89: | Line 89: | ||
==== Possibly Google Chrome has not enabled QUIC by default ==== | ==== Possibly Google Chrome has not enabled QUIC by default ==== | ||
- | At some point we noticed that Google Chrome decided to temporarily disable QUIC by default. Some users explicitly have to enable QUIC under ''chrome://flags''. This may not be the case for you, but it's a good idea to check whether QUIC is enabled in Chrome. | + | At some point we noticed that Google Chrome decided to temporarily disable QUIC by default. Some users explicitly have to enable QUIC under ''<nowiki>chrome://flags</nowiki>''. This may not be the case for you, but it's a good idea to check whether QUIC is enabled in Chrome. |
+ | |||
+ | ==== Possibly bad cached SSL certificates ==== | ||
+ | Sometimes, especially when the site in question has encountered an SSL/TLS error before, Chrome will save the certificate in cache and cause QUIC to be unable to establish a connection. In this case, it can simply be fixed by clearing the browser cache. |