Skip to main content

Quic Cloud - ERROR 520 The QUIC.cloud server waw349-hyb-worker.quic.cloud was not able to connect to the site's origin server.

Nermin

Hello,

for the last couple of days I am having issues with Quic.Cloud. From Friday to be precise.

I've contacted their support and they are saying everything is fine on their end. They even accessed my server and disabled some rules in ConfigServer ModSec Control (33303, 77316861, 77350256). This is the response I got from them "I want to clarify that the issue is not from our end, it is the firewall (imunify and ModSec) and they are blocking our connection. Please temporarily disable and check if the issue is resolved or not, and then reach out to your hosting provider and they will be able to help you out further."
I went back and forth with them trying to resolve this but no luck there.

The issue is happening when somebody tries to access domain.com/wp-admin or wp-login. Not always, but sometimes it does. Then I have to refresh page two or three times, and it loads it normally. I have 120 websites on server, and customers are now starting to complain. When I do Bypass CDN in Quic.Cloud panel it loads web sites just normally.

Server has Immunify360 with just it's own rules enabled in ModSecurity™ Vendors.

Does anybody have some idea what could I do in order to resolve this issue?

Litespeed Cache plugin installed versions are between 5.7.0.1 and 6.0.0.1.

I do not want to go back to Cloudflare, since I bought LiteSpeed Web Server, and all websites are running Litespeed caching plugin. I am using Cloudlare as DNS manger and CNAME to Quic.Cloud. I've disabled Bot fight mode in all Cloudflare websites.

I've added IP 146.59.68.239 from Quic.Cloud to Cloudflare allow WAF list.

I've created whitelist.txt in /etc/imunify360/whitelist/ and added all Quic Cloud IP addressees but same thing happens.

My server: OS AlmaLinux v8.9.0 STANDARD standard, cPanel Version 116.0.9. 256GB RAM, 40 CPU, SSD drives in hardware RAID 1.

 

 

Comments

4 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  I'm not sure on this one since we don't provide support for Quic.cloud.  Did they say *what* in the firewall is blocking the connection?  If you disable ModSecurity completely, as a temporary test, does that fix the issue? 

    0
  • Andrew

    Nermin open a ticket at CloudLinux instead, as I recall Quick is implemented with their solution so they could be in better position assisting you.

    Andrew N. - cPanel Plesk VMWare Certified Professional
    Do you need immediate assistance? 20 minutes response time!*
    EmergencySupport - Professional Server Management and One-time Services

    0
  • Ryan Nash

    Same issue here. Did you ever get this solved?

    0
  • Nermin
    • Edited

    Hello, what I have found is to disable QUIC Backend and it works.
    Also, couple of times it happened but it was Quic cloud error in their data centers. They told me to disable some regions, and override traffic thru other regions until they resolve the issues at their end

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post