Title: LQIP server error when running queue manually
Last modified: July 5, 2023

---

# LQIP server error when running queue manually

 *  Resolved [revivaltech](https://wordpress.org/support/users/revivaltech/)
 * (@revivaltech)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/lqip-server-error-when-running-queue-manually/)
 * Wasn’t able to find anything on these yet, point me int he direction if this 
   has come up already. Recently noticed LQIP queue backed up, and get these errors
   when I hit run manually:
   `Redetected node: Online node needs to be redetected``
   Failed to communicate with QUIC.cloud server: The current server is under heavy
   load. [server] https://node17.quic.cloud [service] lqipDismiss this notice.``
   Cloud Error: Please try after 4m 52s for service lqip.`

Viewing 1 replies (of 1 total)

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/lqip-server-error-when-running-queue-manually/#post-16873378)
 * please go to General page , click “redetect” then run it again

Viewing 1 replies (of 1 total)

The topic ‘LQIP server error when running queue manually’ 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/)

 * 1 reply
 * 2 participants
 * Last reply from: [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * Last activity: [2 years, 10 months ago](https://wordpress.org/support/topic/lqip-server-error-when-running-queue-manually/#post-16873378)
 * Status: resolved