500 Error After 21st December 2025 (PHP 8.1 Removal)

If your website started showing a 500 Internal Server Error on or after 21st December 2025, this is most likely related to the removal of PHP 8.1, which has now reached end of support.

As advised in the email sent at the end of November, all websites previously running on PHP 8.1 have been automatically upgraded to PHP 8.2.

If your site was not tested prior to this change, please follow the steps below.


Step 1: Check for – and remove – the ini_set workaround

Under PHP 8.2 and above, this workaround is no longer required as we now provide a server-side solution.

Please check your site’s configuration file, for example:

  • WordPress: wp-config.php

Look for the following code:

 
# PHP 8 fix for ini_set being disabled function ini_set() { return; }

If this code is present, it should be removed.
Leaving this workaround in place may cause unexpected behaviour or contribute to a 500 error.

After removing the code, save the file and test your website again.


Step 2: Check the error logs

If the issue persists after removing the workaround (or if the workaround is not in the config file), the next step is to review the website’s error logs to identify the cause.

How to access error logs in cPanel:

  1. Log in to your client area

  2. Go to Services > My Services

  3. Click the green Active button next to the relevant service

  4. Click Login to cPanel from the left-hand menu

  5. Open File Manager

  6. Click on the logs directory

  7. Locate the file ending in .error.log

The error log will usually indicate:

  • Plugin or theme compatibility issues

  • Deprecated or removed PHP functions

  • Code that requires updating for PHP 8.2

This information can be used to resolve the issue or passed to your developer.


Step 3: Need further assistance?

If you do not have a developer or would like help resolving the errors, our Design Team may be able to assist.

  • Design work is chargeable

  • Please raise a support ticket and include:

    • The affected domain name

    • Confirmation that the issue began after 21st December 2025

    • Any relevant error messages from the .error.log file

Providing as much detail as possible will help the team investigate more quickly.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

What is the path to perl?

The path to perl in your scripts should be set as:/usr/bin/perl 

What is the absolute path to my webspace?

The absolute path to your website root directory is: /home/username/public_html/Username should...

What is the path to sendmail?

The path to sendmail to be used in your scripts is:/usr/sbin/sendmail 

PHP memory limit exceeded

Very occasionally, when running certain more advanced or demanding PHP based scripts on your...

I need a PHP setting changed

We aim to have PHP on our servers configured to achieve a balance between the majority of...