justaulia

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [LiteSpeed Cache] Invalid WP API response WordPress gave an unexpected response
    Thread Starter justaulia

    (@justaulia)

    7 months, 2 weeks ago

    Thanks for your reply!
    Now the debug log has appeared, and I’ve shared it here:
    🔗 https://pastebin.ubuntu.com/p/XTtkn3sYJ3/

    From the debug log, it seems node 65.109.39.175 failed SSL verification (self signed certificate) — could this node be using an outdated CA store not recognizing the Let’s Encrypt E7 chain?

    Other nodes are working normally and can upload UCSS/CCSS without any issues.

    Forum: Plugins
    In reply to: [LiteSpeed Cache] Invalid WP API response WordPress gave an unexpected response
    Thread Starter justaulia

    (@justaulia)

    7 months, 2 weeks ago

    Hi @litettim

    I’ve followed all the steps you suggested:

    1. Added the provided code snippet to my functions.php (ensured it runs only once).
    2. Enabled Debug mode in the LiteSpeed Cache Toolbox.
    3. Added rest_route=/litespeed to the Debug URI Includes field.

    After doing that, I ran the Run CCSS Queue Manually option. It still shows 82 pending CSS and none of them were uploaded.

    Interestingly, when rest_route=/litespeed is active, there are no debug logs generated at all. But when I remove rest_route=/litespeed from the Debug URI Includes, the logs appear normally (though they seem to be general logs, not related to this CCSS issue).

    So it looks like when the /litespeed route is added, something prevents the debug log or the CCSS process from running properly.

    Could you please check what might be blocking the REST API connection or why the CCSS queue remains stuck despite following all the steps?

    Thank you for your help!

    Best,
    justaulia

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