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 [2018/09/04 18:51] Eric Leu [Checklist] |
litespeed_wiki:config:enable_quic [2019/01/15 14:51] Lisa Clarke [Possibly bad cached SSL certificates] |
||
|---|---|---|---|
| Line 82: | Line 82: | ||
| Looking to //disable// QUIC, or enable it at only the Virtual Host, or Listener Level? See [[litespeed_wiki:config:disable_quic|How to Disable QUIC on LiteSpeed Web Server]]. | Looking to //disable// QUIC, or enable it at only the Virtual Host, or Listener Level? See [[litespeed_wiki:config:disable_quic|How to Disable QUIC on LiteSpeed Web Server]]. | ||
| + | |||
| + | ===== Troubleshooting ===== | ||
| + | |||
| + | ==== CloudFlare doesn't support QUIC yet ==== | ||
| + | Please keep in mind that CloudFlare doesn't support QUIC yet at the time of this writing. If you are behind CloudFlare, please disable it before testing/using QUIC. | ||
| + | |||
| + | ==== 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 ''<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. | ||