Title: Manually run ccss queue
Last modified: June 20, 2025

---

# Manually run ccss queue

 *  Resolved [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/)
 * Hi,
 * Is it new practice to have to wait 24 hours to manually execute the ccss queue?
 * Best regards

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

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521480)
 * there is a daily limit on quota for it , if you have exceeded the quota , then
   you may need to wait for its daily reset , otherwise it does not have any “wait”
   to execute
 *  Plugin Support [litetim](https://wordpress.org/support/users/litetim/)
 * (@litetim)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521498)
 * [@joy0114](https://wordpress.org/support/users/joy0114/) 
   we increased the waiting
   time between requests. But we did not incresed to 24h.Only time it gets to 24h
   is when server cannot connect to your site after a few tries
 *  Thread Starter [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521835)
 * Hi,
 * 203 requests since the beginning of the month, I don’t think it’s a quota issue…
   Even if I don’t know how much the daily quota is.
    A few requests before yesterday,
   yesterday and again today for new publications, but nothing significant in number(
   15 / 20 ?). I was talking about a 24h wait, because there’s a countdown in seconds.
   I noticed this while the count was at about 21h, so I concluded that it was started
   for 24h ..
 * I’ll look at the latest ip Quic.cloud.
    Maybe I don’t have the latest.
 *  Thread Starter [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521839)
 * Well, apparently it’s not an ip problem.
    I’ve even got one more authorized on
   my side: 147.78.3.13
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521845)
 * please provide the report number , you can get it in toolbox -> report -> click“
   send to LiteSpeed”
 * as well as a screenshot on wp-admin -> LiteSpeed Cache -> Dashboard
 *  Thread Starter [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521851)
 * Hi [@qtwrk](https://wordpress.org/support/users/qtwrk/) ,
 * Last Report Number: VINRHBBN
 * Last Report Date: 06/20/2025 21:50:16
 * I think I’ve got a similar issue the the last post of this forum [LiteSpeed Cache: WordPress gave an unexpected response](https://wordpress.org/support/topic/litespeed-cache-wordpress-gave-an-unexpected-response/)
 * Because, Quic.cloud dasboard >> notice gives me this line:
    `2025-06-20 11:34:
   15 my-website.tld Invalid WP API response WordPress gave an unexpected response
   when notified with CCSS results from node 69.50.92.101. Check WP API is properly
   configured.`
 * So I read this page: [Solving WordPress REST API issues](https://docs.quic.cloud/troubleshooting/restapi/)
 * I added code to my functions.php
 * And I have got an answer:
 *     ```
       {
         "remote_ip": "My-private-IP",
         "x_forwarded_for": "Null",
         "proxy_remote_addr": "Null"
       }
       ```
   
 * The page is long… many more tests to do I think ….
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521856)
 * the connection looks alright since you have 2 nulls
 * please try go to toolbox -> debug setting -> debug to ON , debug level to advance,
   debug include URI , add `ccss` ,
 * then in toolbox -> log view -> clean up existing log
 * now try to manually trigger the execution again , wait for 10 , 15 minutes , 
   then share the log via [https://pastebin.ubuntu.com/](https://pastebin.ubuntu.com/)
 *  Thread Starter [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521873)
 * Some difficulties to find out my Ubuntu password …
    Need to create another account,
   but some difficulties to retrieve the Ubuntu email … some days are just like 
   that. For now, I have to sleep… More informations tomorrow.
 * Thanks for your help.
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18521875)
 * oh, no worry ,you can use any of these kind of sharing site , or even put it 
   on your own site for a downloadable text file
 *  Thread Starter [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18522386)
 * Hi,
 * Well, I got out of my 24-hour prison, but I was “incarcerated” again … in forcing
   ccss cron.
 * So I did what you told me.
    And when I clicked on “force cron” (ccss section 
   of the Litespeed plugin dashboard), I got this error at the top of page: `LiteSpeed
   Cache: WordPress gave an unexpected response when notified with QUIC.cloud service
   results. Check WP API is properly configured. Check your QUIC.cloud dashboard
   for more details.`
 * Then, a few minutes later, here’s the resulting log:
 * [Link to log](https://galileo.dream-box.org/nextcloud/index.php/s/dYFggsq36La2qzY)
 * I can’t use the “Execute ccss queue” button on the “Page optimization” page, 
   as the button is greyed out and indicates the countdown….
    `"Exécuter CCSS file
   d’attente manuellement Available after 80783 second(s"`
 * This behavior happened just after I updated Woocommerce to 9.9.5 and the Litespeed
   plugin to 7.2.
 * Thanks again for all your help !
 * Best regards
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18522407)
 * alright
 * please create a ticket by mail to `support at litespeedtech.com` with reference
   link to this topic , we will investigate further.
 *  Thread Starter [joy0114](https://wordpress.org/support/users/joy0114/)
 * (@joy0114)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18522423)
 * Ok, Thank you for your time.
    Best regards

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

The topic ‘Manually run ccss queue’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 12 replies
 * 3 participants
 * Last reply from: [joy0114](https://wordpress.org/support/users/joy0114/)
 * Last activity: [11 months, 1 week ago](https://wordpress.org/support/topic/manually-run-ccss-queue/#post-18522423)
 * Status: resolved