• Resolved marv2

    (@marv2)


    I noticed that when I’m logged in to the website and visit the front end of the website, I get a 503 on every page. The back end works fine.

    When I log out, everything is fine on the front end.

    Also if I disable the Litespeed Cache plugin, everything is fine.

    I tried clearing all caches multiple times,but it didn’t help.

    I also set “Cache logged in users” to No.

    Any idea what could be causing this?

    Thank you!

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hi,

    Please provide the LS report number. Please go to LiteSpeed Cache Toolbox –> [5] Report and click “Send to LiteSpeed”.

    Regards.

    Thread Starter marv2

    (@marv2)

    Hi,

    Here is the report number: BXAJYABM

    Plugin Support qtwrk

    (@qtwrk)

    if you disable cache plugin , then it won’t be any 503 error anymore ?

    Thread Starter marv2

    (@marv2)

    @qtwrk Correct.

    Plugin Support qtwrk

    (@qtwrk)

    what’s your server environment ? a shared hosting ? your own VPS or something ?

    Thread Starter marv2

    (@marv2)

    VPS on GridPane. Other sites on the server work fine.

    Plugin Support qtwrk

    (@qtwrk)

    503 error is usually due to PHP crash , please check if there is any PHP error log

    if you are using OLS, you may need to ask your provider to assist you to enable and obtain PHP error log

    Thread Starter marv2

    (@marv2)

    Wp-debug is enabled but there are no errors in the log.

    Plugin Support qtwrk

    (@qtwrk)

    no , not only that , but php setting’s error_log

    create a phpinfo page, looking for error_log file path

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I’m going to mark this topic “Resolved”, due to lack of activity.

    If you still need help, please feel free to re-open it.

    When re-open it, please also change the topic status to “not solved”

    Best regards,

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Getting 503 on frontend when logged in’ is closed to new replies.