Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter Fred17

    (@f14m07)

    Last Report Number: ZCCLBUOJ

    Last Report Date: 07/16/2026 17:25:04

    Plugin Support litetim

    (@litetim)

    @f14m07
    Thank you for report and I am sorry for the problem you have
    I checked the Network tab from Dev Console and I see image: /wp-content/uploads/2026/01/xEtonell-spyassim-vueautre-voilier-150×150.jpeg.webp.pagespeed.ic.HT4XLvV72T.webp has 404 status.
    The thing is that both have an x in front.

    I checked the report and I see that server is changing CSS/JS/Images src by adding .pagespeed.***
    It comes from a server module: Pagespeed.
    Please try disabling that, clear cache and test the change.

    Thread Starter Fred17

    (@f14m07)

    I have no access to litespeed module serveur. Why it works and sudenly it doesn’t.

    Thread Starter Fred17

    (@f14m07)

    I saw I have the issue on safari and firefox but not in chrome.

    Thread Starter Fred17

    (@f14m07)

    two images have the x before the name, one is visible, not the other.

    Thread Starter Fred17

    (@f14m07)

    In the media library, I clicked on ‘Restore from backup’ and the image file became visible. So what is the problem? Is the optimised file deleted at some point?

    Plugin Support litetim

    (@litetim)

    @f14m07 If it worked before and now is not working, that means something changed on your site(updated, new plugins).

    Thread Starter Fred17

    (@f14m07)

    I have this PHP warning today:
    PHP Warning:  unlink(/home/taeq4768/vogue-et-reve.fr/wp-content/litespeed/js/d94471dbe99f9381f91b8e0d7fb3e963.js.tmp): No such file or directory in /home/taeq4768/vogue-et-reve.fr/wp-content/plugins/litespeed-cache/src/optimizer.cls.php on line 156

    Plugin Support litetim

    (@litetim)

    @f14m07 try Purge CSS/JS and Purge All

    Thread Starter Fred17

    (@f14m07)

    I’d tried, but without success.

    Plugin Support litetim

    (@litetim)

    @f14m07 I visited the site and I do not see the error: not JS file or image

    From what I see the errors are fixed.
    I think the error appears from a second cache layer that is not updating when LSC is changing cache.

    Please confirm my finding.

    Thread Starter Fred17

    (@f14m07)

    Maybe a TTL problem that I haven’t identify. Thanks for your support, you can close this issue.

    Plugin Support litetim

    (@litetim)

    I can close the topic, but if you need further help, just reply here.

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

You must be logged in to reply to this topic.