QUIC.cloud may potentially be blocked by the origin server. This is a problem, since QUIC.cloud acts as a proxy service for your domain, and requires access for uncached requests.
To ensure QUIC.cloud is not blocked by the origin server, it’s ideal that the QUIC.cloud IPs be added to an ignore-list or allowlist. Please note that this IP list may be changed on a weekly basis as nodes are added or removed.
First, we recommend that you add the IPs as “Trusted” in your LiteSpeed WebAdmin Console. Navigate to Configuration > Server > Security, scroll down to Access Control, and add the IPs to the Allowed List. The letter
T added after the IP (no space) indicates that it is Trusted. So, your list would look something like this:
If your server is using Imunify360, BitNinja, or a web application firewall, you should allow the IPs in these places as well.
With Imunify360, the QUIC.cloud IPs are automatically included on the allowlist, and you don’t have to worry about anything. To verify, you can find the IPs located in
The latter path may vary depending on the web server and control panel used.
BitNinja maintains a list of allowed IPs, but we recommend you verify that this is actually true for your server. If necessary, you can manually allow the QUIC.cloud IPs in Bitninja.
Config Server Firewall (or) CSF
If CSF is your primary firewall, you can add our IPs to the csf.ignore file in the lfd- Login Failure Daemon section within the CSF Dashboard (accessible from the Plugins section in WHM/Plesk).
Alternatively, you can add the list directly to the
/etc/csf/csf.ignore file, and restart CSF to allow the changes to take effect.
If your server is not using any server-level firewall, or the IP’s are allowlisted already, be sure to check any application level firewall that may be in use (such as Wordfence for WordPress). It should include a similar allowlist function.