Issues with cron CSS

  • Resolved Fred17

    (@f14m07)


    1 year, 3 months ago

    Hi,

    I have queues that don’t empty. I’ve used the button to force CRON several times and I’ve emptied the queues too. They then form again.

    I often see this type of line in the PHP error log file:

    [05-Dec-2024 06:15:03 UTC] Erreur d’événement de replanification de tâche pour le crochet litespeed_task_ucss. Code d’erreur : could_not_set. Message d’erreur : La liste des évènements planifiés n’a pas pu être sauvegardée.. Données : {“schedule”:”litespeed_filter”,”args”:[],”interval”:60} [05-Dec-2024 06:45:04 UTC] Erreur d’événement de replanification de tâche pour le crochet litespeed_task_vpi. Code d’erreur : could_not_set. Message d’erreur : La liste des évènements planifiés n’a pas pu être sauvegardée.. Données : {“schedule”:”litespeed_filter”,”args”:[],”interval”:60} [05-Dec-2024 07:15:03 UTC] Erreur d’événement de replanification de tâche pour le crochet litespeed_task_avatar. Code d’erreur : could_not_set. Message d’erreur : La liste des évènements planifiés n’a pas pu être sauvegardée.. Données : {“schedule”:”litespeed_filter”,”args”:[],”interval”:60} [05-Dec-2024 09:15:04 UTC] Erreur d’événement de replanification de tâche pour le crochet action_scheduler_run_queue. Code d’erreur : could_not_set. Message d’erreur : La liste des évènements planifiés n’a pas pu être sauvegardée.. Données : {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60} [05-Dec-2024 09:30:03 UTC] Erreur d’événement de replanification de tâche pour le crochet litespeed_task_ccss. Code d’erreur : could_not_set. Message d’erreur : La liste des évènements planifiés n’a pas pu être sauvegardée.. Données : {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}

    I also regularly see this type of error in other logs:

    213.159.1.75 – – [30/Nov/2024:16:32:42 +0100] “POST /?rest_route=/litespeed/v1/notify_ucss HTTP/1.1” 401 96 “-” “Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html) Chrome/112.0.0.0 Safari/537.36”

    /?rest_route=/litespeed/v1/notify_ucss with http 401.

    So I don’t understand what is blocking the recovery of these queues?

    I am using the advanced preset. Nothing else specific.

    Thanks for your answer

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support qtwrk

    (@qtwrk)

    1 year, 3 months ago

    for that error message, it’s okay to ignore , but that 401 is indeed blocking CSS generation

    it could be due to proxy server and how it detects IP , please check this topic

    Thread Starter Fred17

    (@f14m07)

    1 year, 3 months ago

    Well, I have already read the topic, and I have already change the line in the php file. I changed it again after your last update.
    I’d like to make it clear that I’m not talking about obtaining the key, as stated at the beginning of the linked topic.
    I’ll see if it changes anything and come back to this post.

    Plugin Support qtwrk

    (@qtwrk)

    1 year, 3 months ago

    all our API calls, generate domain key , ucss generation , ccss genration , LQIP/VPI , image optm …are using WP REST API with IP verification

    it’s same case , the IP verification may failed due to proxy

    Thread Starter Fred17

    (@f14m07)

    1 year, 3 months ago

    Hello,
    I’m here to let you know that I no longer have any problems. The cause of my problems was that I had renamed my plugins directory to improve security and added the definition of constants in wp-config.php (‘WP_PLUGIN_DIR’ and ‘WP_PLUGIN_URL’).
    I think you’re working on the assumption that the plugins directory hasn’t been renamed.
    Perhaps you need to make some improvements?
    In any case, everything’s fine now and I hope that others will find it useful.
    Best regards,

    Plugin Support qtwrk

    (@qtwrk)

    1 year, 3 months ago

    I must say that thought has never come across my mind

    I assume it’s done as this doc ?

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

The topic ‘Issues with cron CSS’ is closed to new replies.