Wordpress LScache Plugin: QUIC.cloud CDN Error 520 and 524
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, I am getting errors on all my QUIC.cloud websites. There are four different websites and none of them is working with QUIC.cloud CDN turned ON. QUIC.Cloud FAQs page (https://quic.cloud/faq/) suggests that I should contact my webshost in case of 520 error to whitelist all the IPs. I contacted them and they told me that none of the IPs are blacklisted. The FAQ page also suggests that I should contact LiteSpeed in case of 524 errors. Could someone please help me figure out how to resolve this issue? Thanks. 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, Hi @CacheCrawler 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. 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, Hi @CacheCrawler 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. Hi, I do not know , not without seeing it first hand? Best regards, Hi @CacheCrawler, The 520 error has again started appearing on the website. Would it be possible for you to take a quick look and see whats wrong? I will try to keep the website in this state for a few hours. I hope you get this message before that. Thanks. Hi, it still loads fine on me. Could you please indicate which node youve connected to ? you can get it in HTTP response header, looking for x-qc-pop Best regards, @CacheCrawler 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. 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. 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,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference