[Resolved] Enable Quic

[Hedloff]

Hello,

I would like to enable Quic for all customers on our hosting servers, not just for one site.
In reference to your wiki it's not possible to setup:
https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:enable_quic

Is that something you will work on in upcoming versions? Or is it just the documentation that needs to be updated?

 

[mistwang]

There was some issue with enabling QUIC for Apache vhosts, please update to build 1 of 5.2, should have it addressed.

/usr/local/lsws/admin/misc/lsup.sh -f -v 5.2

 

[Hedloff]

I tried that, but didn't help.
I didn't create any listener or public ssl or private key, but that shouldn't be necessary!?

I got it working Forgot to open UDP port 443. Does IN/OUT need to be open?

Actually, webserver is restarting all the time now.
Checking lswcp I see:

[AutoRestarter] forking too frequently, suspend for a while!

Checking log:

tail -f /usr/local/apache/logs/stderr.log
2017-07-12 02:29:17.200 [STDERR] sh: gdb: command not found
mv: cannot stat `/tmp/lshttpd/core*': No such file or directory
2017-07-12 02:29:21.380 [STDERR] sh: gdb: command not found
2017-07-12 02:29:22.376 [STDERR] sh: gdb: command not found
2017-07-12 02:29:23.608 [STDERR] sh: gdb: command not found
mv: cannot stat `/tmp/lshttpd/core*': No such file or directory
2017-07-12 02:29:26.983 [STDERR] sh: gdb: command not found
2017-07-12 02:29:28.538 [STDERR] sh: gdb: command not found
mv: cannot stat `/tmp/lshttpd/core*': No such file or directory
2017-07-12 02:29:31.196 [STDERR] sh: gdb: command not found
2017-07-12 02:29:33.559 [STDERR] sh: gdb: command not found

 

[Hedloff]

Sites went down and I got ERR_QUIC_PROTOCOL_ERROR.
So I had to manually downgrade to 5.1.7 trough SSH as GUI didn't work.

 

[Hedloff]

On another server webserver just keep restarting so I had to downgrade to 5.1.7 again and that fixed the issue. I didn't test Quic on that server.
So 10 other servers are working fine (without Quic) for now.

I also forced update to latest version of 5.2 on a server that had 5.2 and quic enabled. Then sites stopped working, so now I downgraded that version to 5.1.7 again and everything is fine.
One thing that I noticed is that temp url of server (mod_userdir) is now giving 404 error as it also should. I have a ticket with cPanel about this on litespeed servers. As we don't have mod_userdir activated temp urls should give 404 and it does now after downgrade to latest version (5.1.7)!

Hope you get bugs sorted out quick

 

[mistwang]

Would like to try a debug build on your server, it probably take less than 5 minutes to figure out what is wrong with the core dump.

 

[Hedloff]

We're sending you some core files, hope you find out what all the issues are and get them fixed

 

[mistwang]

Actually, I just uploaded 5.2 build 2, it should fix the crash related to QUIC.

 

[Hedloff]

Seems to be working great now Will check on other servers aswell.
Thanks!

 

[Hedloff]

Got one more question about this. I have only enabled QUIC and didn't setup any listener or anything else, but it seems to be working.
I also checked firewall (CSF) and UDP port incoming/outgoing for port 443 is not added, but it still seem to work without it?

Do we need to add/open port 443 on UDP incoming/outgoing?

 

[m00ster]

I am still experiencing crashes with build2 accessing a website with QUIC enabled.

I can provide access to the server if you would like to debug.

Thanks!

 

[MikeF]

Something is up with the cPanel crap. It seems to not allow me to enable QUIC. I have followed everything at https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:enable_quic?s[]=quic

And I am STILL not seeing it running, not even on the port 7080 admin console. WTF? Instead Im seeing HTTP2-enabled (blue not green on the indicator). I have tried EVERYTHING and its still not working.

 

[Hedloff]

I just enabled QUIC here:

• Navigate to WebAdmin Console > Configuration > Server > Tuning.
• On the same page, scroll down to Security Features
• Set Enable QUIC to Yes

Nothing more. Not even in CSF firewall and it works on all sites for the servers I have enabled this on.

Thanks for updating your wiki/docs LiteSpeed, but it still needs a bit improvement I think
I did notice that your main page was down for a while earlier today because of QUIC

 

[Amin Soltani]

I have this problem too. i enabled QUIC from tuning and 443 port in UDP in and out. but it doesn't work in my websites.

what should i do to solve it ?

 

[Penelope Watson]

actual cause of this error is unknown. It is assumed that it may be triggered by the misconfigured Google Chrome’s settings, some software conflict, connection problems, and similar issues. Luckily, it’s easier to fix ERR_QUIC_PROTOCOL_ERROR bug in a quite easy manner. For that, you have to perform the steps provided down below. (SOLVED)
https://www.errorsolutions.tech/error/err_quic_protocol_error/
Solution 1. Disable Experimental QUIC protocol