Plugin Support
qtwrk
(@qtwrk)
Hi,
could you please provide the report number ?
you can get it in toolbox -> report , click “send to LiteSpeed”
in Note, you can also provide the domain that gives you 524
Best regards,
Thread Starter
9itish
(@9itish)
Hi @qtwrk
I have sent two reports from two domains reporting error 520 and 524.
The Report numbers are: VBGINODB for error 520 and CVQYBSXX for error 524.
I have also sent the domain name in the notes for both reports. π
Plugin Support
qtwrk
(@qtwrk)
Hi,
I have re-enabled QC on both sites, and tested from 3-4 different location and all OK on me , please verify ?
Best regards,
Thread Starter
9itish
(@9itish)
Hi @qtwrk
The websites seem alright now. I was able to hit private QC cache for the webpage I visited.
If possible could you please explain, what caused this issue?
Thanks. π
Plugin Support
qtwrk
(@qtwrk)
Hi,
I do not know , not without seeing it first hand…
Best regards,
Thread Starter
9itish
(@9itish)
Hi @qtwrk,
The 520 error has again started appearing on the website. Would it be possible for you to take a quick look and see what’s wrong?
I will try to keep the website in this state for a few hours. I hope you get this message before that. π
Thanks.
Plugin Support
qtwrk
(@qtwrk)
Hi,
it still loads fine on me.
Could you please indicate which node you’ve connected to ?
you can get it in HTTP response header, looking for “x-qc-pop”
Best regards,
Thread Starter
9itish
(@9itish)
@qtwrk Yes, it started loading without any issues after I posted the comment here.
It seems to be appearing “randomly”. Here are all my response headers:
HTTP/2 304 Not Modified
x-powered-by: PHP/7.3.21
pragma: no-cache
x-frame-options: SAMEORIGIN
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
content-type: text/html; charset=UTF-8
etag: "143371-1599041845;br"
vary: Accept-Encoding
x-qc-cache: hit,private
date: Wed, 02 Sep 2020 10:19:07 GMT
server: LiteSpeed
x-qc-pop: AS-SG-61
alt-svc: quic=":443"; ma=2592000; v="43,46", h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-27=":443"; ma=2592000, h3-28=":443"; ma=2592000, h3-29=":443"; ma=2592000
X-Firefox-Spdy: h2
I will post my response headers again if the error pops-up in the future. π
Thanks.
-
This reply was modified 5 years, 10 months ago by
9itish.
Thread Starter
9itish
(@9itish)
The problem lasted for 2-3 hours this time and pages started loading normally about half an hour after I posted my comment. I did not make any changes on my end this time.
Before that, when I originally started posting in this thread, it persisted for about 10-12 hours.
Plugin Support
qtwrk
(@qtwrk)
Hi,
Well, For QC issue as it may requires more quicker/faster response , it is better if you can join our Slack community , where you can receive more real-time information and communication.
Best regards,