Issue With Domain Key & QUIC.cloud Tasks
-
Hi, so I’ve been pulling my hair over this issue for the past week. Please bear with me while I describe the situation in detail.
There are two sites: syllabi.in (HOST-A running on LiteSpeed) & picstreak.com (HOST-B on OpenLiteSpeed). Except for the hosting, everything is the same. Both are proxied on Cloudflare, similar DNS records, no firewall rules, no mod-security nothing extra. Even same theme and codes in functions.php, and same plugins. Both sites also throw 401 errors when you try to access the LiteSpeed token (/wp-json/litespeed/v1/token). In fact, picstreak was hosted on HOST-A till a month ago, then we migrated it to the new host, so we only changed the A record in DNS.
Here’s the strange part:
syllabi.in has no issues fetching the domain key in LS Cache plugin, despite the Rest API token being seemingly forbidden/401. Happy story till here. Cloud operations like image optimization work fine too. Cloudflare is enabled and proxy is ON.
picstreak.com, on the other hand, can not get the domain key provisioned and cloud tasks have stopped working. When we “pause site on Cloudflare” though, it is able to get a domain key, and I’m guessing QUIC-related things work normally. Tried adding a Cloudflare firewall rule to allow all QUIC.cloud IPs, but no luck. Toggled “Development Mode” on Cloudflare, no luck. The only thing that works is pausing Cloudflare.
We can not disable Cloudflare, but what’s more important is, how is syllabi.in managing to work just fine with QUIC.cloud in similar setup? Can it have something to do with OpenLiteSpeed? If there is some filter or code snippet I can use or some setting to keep Cloudflare enabled while allowing the site to work gracefully with QUIC.cloud, it would be really helpful.
The only thing I have not tried is logging into HOST-B’s OpenLiteSpeed WebAdmin panel and enabling showing Client IP in the header instead of showing Cloudflare’s IPs. I’ll be doing that now, but I don’t think this will fix it. Will post an update if it does.
Meanwhile, if you can figure what’s causing this strange issue, I’ll be grateful.
The topic ‘Issue With Domain Key & QUIC.cloud Tasks’ is closed to new replies.