WordPress Website crashes when PHP version update to 8.* from 7.4.33

  • The website was created by someone else many years ago, and I am currently working on it. The site is running on the latest versions of WordPress and MySQL. However, when attempting to upgrade the PHP version to 8.*, I encountered a 500 error.

    I have already deactivated all plugins and switched to the default WordPress theme, Twenty Twenty-Four, but the error persists. Could anyone provide assistance with this issue?

    And the website is hosted on Site Ground Sever.

    Please find screenshot of error on this link.

    Thank you in advance for the help.

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

  • The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.

    Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://www.ads-software.com/support/article/debugging-in-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.

    In both cases you should be able to see what the cause is in the logfile.

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    Hi @threadi

    Thank you for you quick responce.

    I have already checked in hosting area for error log, but it is blank. Just getting few messages in Access Log. That you can find below:

    “GET / HTTP/2.0” 500 0 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36” | TLSv1.3 | 0.044 0.049 0.049 MISS 0 NC:000000 UP:SKIP_CACHE_EXPIRED

    “GET / HTTP/2.0” 500 0 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36” | TLSv1.3 | 0.045 0.050 0.051 BYPASS 0 NC:200000 UP:-

    “PURGE /* HTTP/1.1” 200 169 “-” “SiteGround Cache Flusher” | TLSv1.3 | – – 0.000 – 0 NC:000000 UP:-DT

    “PURGE /* HTTP/1.1” 200 168 “-” “SiteGround Cache Flusher” | – | – – 0.000 – 0 NC:000000 UP:-DT

    Also, when I tried to debug website using wp-config file, I didn’t get any error. Even I have checked php_errorlog file, there is also no error reported.

    Thank you,

    threadi

    (@threadi)

    With debugging activated, a log file called “debug.log” should be created under /wp-content/. If this is actually empty, a much more serious error occurs before WordPress is executed. In this case, you should contact your host’s support team.

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    Sure, I will check with support team about this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.