404 page errors

  • Resolved SimonFullSteam

    (@slidstershadowprocomau)


    11 months ago

    Hi,

    I have an issue on this website that’s been very hard to pin down, but I think now it may be Litespeed cache related, although it could be that Litespeed Cache is just a symptom not the cause, I’m not sure.

    What happens;
    At some point over night in the early hours of the morning on seemingly random days some pages get served with a 404 error and WordPress forward traffic to the closest available URL.

    So /rsa/ -> /rsa-101/

    The pages are still published and available for editing in the back end, so you can see them as soon as you login.

    We have been resaving Permalinks to fix it, but this time we fixed by just clearing the Litespeed cache using Purge All.

    The website is on shared cpanel Litespeed server and it’s using Quic Cloud.

    Could you please take a look at any relevant logs around that time that I might not have access to?

    Thanks

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support litetim

    (@litetim)

    11 months ago

    @slidstershadowprocomau
    Hello
    there are 2 things that stood out for me:
    – time of happening: do you have some cron that run over the night? maybe they change some URL or statuses and the links are accessed only in the morning
    – clearing LSCWP fixed it: this will happen only if some changes are done and there is no cache clear.

    As a developer: after each page settings change is done, is recommanded to do a Purge all. You can use this action:
    do_action('litespeed_purge_post', $post_id);

    Thread Starter SimonFullSteam

    (@slidstershadowprocomau)

    11 months ago

    Thanks for your quick reply.

    I have checked CRON jobs and manually run them all to try to recreate but go nowhere.

    On this site there was a conflict with a CPT slug and a page name which is now fixed. I’m wondering if Litespeed could have cached this somewhere that’s not cleared by a normal purge.

    Anyway, we’ve decided to rebuild the URL structure which should fix the problem. It would have been nice to get to the bottom of it, but no use in wasting time.

    Marking as Resolved

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

The topic ‘404 page errors’ is closed to new replies.