Quic Cloud connection is causing cache issue

ushnahareem
(@ushnahareem)

1 week, 3 days ago
Hi Support!

I am experiencing an issue after connecting my WordPress website to QUIC.cloud. When QUIC.cloud CDN is enabled and the website is connected, the following problems occur:
- The website design/layout breaks.
- An older version of the website is displayed.
- Recent content and design changes do not appear.
- Purging the WordPress and LiteSpeed caches does not consistently resolve the issue.
- When QUIC.cloud is disconnected or bypassed, the current website loads correctly.
It appears that QUIC.cloud may be serving stale cached files, including old HTML, CSS, or JavaScript resources. Could you please check:
1. Whether the domain is correctly connected to QUIC.cloud.
2. Whether DNS/CDN settings are pointing to the correct origin server.
3. Whether an old CDN cache is still being served.
4. Whether CSS or JavaScript optimization is causing the layout to break.
5. Whether there is a cache conflict between LiteSpeed Cache, QUIC.cloud, the hosting cache, or another CDN.
6. Whether the correct SSL certificate and domain variation are configured.
The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Support litetim
(@litetim)

1 week, 3 days ago

@ushnahareem please send a report to Litespeed, from LSCWP => Toolbox => Report => click on “Send to Litespeed” and share the ID generated.

What do you mean by old HTML, CSS, JS? Does the design changed?

Thread Starter ushnahareem
(@ushnahareem)

1 week, 2 days ago

Hi, the design does not permanently change. The issue occurs intermittently after connecting the website to QUIC.cloud.

Sometimes the CSS generated or optimized by LiteSpeed Cache does not load, causing parts of the page to lose styling or the entire layout to appear broken. After clearing or regenerating the LiteSpeed CSS cache, the design may return to normal, but the issue can happen again.

This may be related to stale or unavailable generated CSS files, such as UCSS or CCSS, being served through QUIC.cloud. The original CSS files and the website content are still present.

I’ve sent the LiteSpeed report, see details below:

Last Report Number: MXQMWMHY

Last Report Date: 07/29/2026 04:53:58

Plugin Support litetim
(@litetim)

1 week, 2 days ago

@ushnahareem
There are a few things that you must look into:
– I see that QC services are disabled in plugin(no API key). Please disconnect QC from plugin and reconnect it.
– in htaccess there are some left overs from Caching by SG-Optimizer. Please remove everything in between:
# Leverage Browser Caching by SG-Optimizer AND # END GZIP
– In htaccess there is broken rule too: RewriteRule[ ^profan-industries/?$ https://profan….. Also some links are to www site others to non-www.

After the domain is linked go to QC account, choose the site from your list. Go to CDN => Purge All CDN Cache
Please make sure these things work as expected and we can debug further
Plugin Support litetim
(@litetim)

1 week, 2 days ago
@ushnahareem I was checking your site and I see it broken.
Make sure site link is correct. From: WP -> Settings -> General
Coming back to www vs non www settings.

Access to font at ‘https://profan.com.au/wp-content/uploads/2016/05/Montserrat-ExtraBold.woff’ from origin ‘https://www.profan.com.au’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
Failed to load resource: net::ERR_FAILED cat_services.jpg:1
Access to font at ‘https://profan.com.au/wp-content/uploads/2016/05/Montserrat-ExtraBold.ttf’ from origin ‘https://www.profan.com.au’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

Try setting these links to ON in QC:
Map Both www/non-www
Auto Redirect www/non-www
From QC => site => CDN => CDN config
- This reply was modified 1 week, 2 days ago by litetim.
Plugin Support litetim
(@litetim)

1 week ago

@ushnahareem any udpates here?

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Tags