Cant Make QUIC Get Working

Discussion in 'General' started by Deepblue, Jul 31, 2017.

  1. Deepblue

    Deepblue Active Member

    Hello,
    I've enabled Quic form LS Web Server Admin Panel
    [​IMG]
    And i've opened 443 port for udp from firewall and csf
    iptables -A INPUT -m state --state NEW -p udp --dport 443 -j ACCEPT

    [​IMG]
    And here is the result (its blue, not green)
    [​IMG]
    What am i doing wrong?
     
  2. mistwang

    mistwang LiteSpeed Staff

    it usually takes another refresh to let chrome switch from HTTP/2 to QUIC.
     
    Deepblue likes this.
  3. Deepblue

    Deepblue Active Member

    I've refreshed the page many times with CTRL+F5 and CTRL+SHIFT+R still no effect it doesnt works.
     
    Last edited: Jul 31, 2017
  4. mistwang

    mistwang LiteSpeed Staff

    sometimes, you need to close chrome and open again. it remember the last QUIC failure and wont try again.
     
  5. Deepblue

    Deepblue Active Member

    I've done that too couple of times still no luck :(
     
  6. mistwang

    mistwang LiteSpeed Staff

    Are the working one and the two non working domains using the same IP?
     
  7. Deepblue

    Deepblue Active Member

    The working one also stopped to working, i even cant see its working on here LS forum. Dont know what is going on.
    Btw no, each website uses a different ip.
     
  8. mistwang

    mistwang LiteSpeed Staff

    Looks like google is doing something to the chrome. my chrome's QUIC was disabled all of sudden.
    You can go to chrome://flags/, change "Experimental QUIC protocol" from "Default" to "On" .
    If you use different IP, you need to check "netstat -anp" to make litespeed is listen on UDP <IP>:443 .
     
    Deepblue likes this.
  9. Deepblue

    Deepblue Active Member

    Thank you very much, after enabling Experimental QUIC protocol from Chrome it seems to be working now. Could you confirm it for me please? I've sent you my website link via p.m.
    Regards
     
  10. Deepblue

    Deepblue Active Member

    Today its suddenly stopped to working again, i havent done any changes why this is happening?
     
  11. Hedloff

    Hedloff Well-Known Member

    Could you also send the website in pm to me and I can also check it from here?
    We also had the same issue, but the solution was to change from Default to ON and then it started to work again for us.
     
  12. Michael A

    Michael A Administrator Staff Member

  13. Hedloff

    Hedloff Well-Known Member

    Thanks for your update Michael :)
    Do you know anything about when and if other browsers will support QUIC?
     
  14. Michael A

    Michael A Administrator Staff Member

    At the moment I think it is available for Chrome, Chromium, and Opera (not enabled by default). No idea when FireFox etc will follow suit.
     
  15. Deepblue

    Deepblue Active Member

    Its really weird. Quic is enabled/on at both site (Chrome and LS Web Admin Panel) though that sometimes it works sometimes suddenly stop to working and then work again. This happening over and over again.

    [​IMG]
     
  16. mistwang

    mistwang LiteSpeed Staff

    chrome remember to use QUIC for a domain for a day or so.
    The next day, you try access the site, the first request could be in HTTP/2, next request will switch to QUIC protocol.
     
  17. Deepblue

    Deepblue Active Member

    How i can make the next request? By restarting the browser or what?
     
  18. mistwang

    mistwang LiteSpeed Staff

    force refresh, or click a link to reload, the page maybe cached by the browser, you need to press "CTRL" or "SHIFT" to load the page.
     
  19. Deepblue

    Deepblue Active Member

    Unfortunately none of these works. Still indicator is blue, i've refreshed the page so many times with CTRL+F5 and CTRL+SHIFT+R.
    Also i tried load the page with CTRL and SHIFT, thats not working aswell.

    Edit: Just realized that i'm getting this error at my LS Web Admin Panel:

    [​IMG]
     
  20. mistwang

    mistwang LiteSpeed Staff

    When I access the site, the second refresh will change the color to green.
    If there is a failure with QUIC, chrome will remember it and not try QUIC when you refresh. close chrome completely, then start again, chrome will try QUIC again.
    We need to figure out the invalid ACK issue if it happen repeatedly.
     

Share This Page