Start for free – your first 3 months are freeSee the offer

Troubleshooting

Error 500 – internal server error after an update or PHP change

Does the page show "500 Internal Server Error" or a white screen? Find the latest change, switch the PHP version back, turn off plugins, or restore safely from backup.

4 min readUpdated

On this page
  1. What the control panel can't do (yet)
  2. Frequently asked questions
  3. Which PHP version should I choose?
  4. Can I have different PHP versions for different websites?
  5. The error comes and goes. What does that mean?

Error 500 means the server ran into trouble while building the page. The cause is almost always a change: a new PHP version, an updated plugin or theme, or an edit to a PHP file. Find the change and undo it. Work through the steps from the bottom of the ladder up – most faults are fixed after the first three.

Troubleshooting ladder: what was changed, PHP version, plugin or theme, the error log, restore backup and support
Start at the bottom of the ladder
  1. Step 1: Find out what was changed

    Go to Security → Activity log. The Change log tab shows the latest changes on the whole account (all hostings), e.g. a change of PHP version, with the time and who made it. Choose Web hosting under Area to see only the hostings' changes, and Show more for older ones. Compare with when the error started.

  2. Step 2: Switch the PHP version back

    If someone changed the PHP version just before the error, go to Web hosting → PHP, choose the previous version under PHP version and press Save. You can choose between 8.2, 8.3 and 8.4.

    The PHP page with the PHP version drop-down and the Save button
    One PHP version applies to the whole hosting
  3. Step 3: Turn off plugins or theme

    If you use WordPress, open the files via Web hosting → Files or SFTP and rename the folder public/wp-content/plugins to e.g. plugins-slaaet-fra. If the site works now, it's a plugin. Give the folder its name back and rename one plugin at a time until you find the culprit. If that didn't help, do the same with the folder for your theme under wp-content/themes. The full walkthrough is in WordPress shows a white screen or error 500.

  4. Step 4: Read the error log

    The cause is usually in the log. Open the logs folder in your home folder with Web hosting → Files or your SFTP program. logs/php/error.log shows errors from PHP, and logs/<website>.error.log (e.g. main.error.log) shows errors from the web server. The bottom line is the newest.

  5. Step 5: Restore from backup

    Go to Web hosting → Backup. We take daily backups and keep them for 30 days. Choose the Web hosting, Database or Website tab and press Restore next to a backup from before the error.

    Restore backup with the Alongside option highlighted and an explanation that the current version stays untouched
    Restore alongside first, so you don't overwrite anything

    Choose Alongside (safe – nothing is overwritten) so you can compare without losing anything. If you're sure the backup is the right one, you can afterwards choose Overwrite the current one.

  6. Step 6: Contact support

    Write to support and write the time the error started and what was changed. If the whole site is down, say so in the subject line.

What the control panel can't do (yet)

The control panel doesn't show PHP's error log yet – it's a file in the logs folder (see the step Read the error log). If you use WordPress, you can also have the error written to a file with WP_DEBUG_LOG; see the step See the error message itself in WordPress shows a white screen or error 500.

Frequently asked questions

Which PHP version should I choose?

The newest one your website supports. First update WordPress, plugins and theme, then switch to 8.3 or 8.4. If errors appear, switch back.

Can I have different PHP versions for different websites?

Not at present. One PHP version applies to the whole hosting. PHP version per website is in development.

The error comes and goes. What does that mean?

It could be a heavy page, a plugin running out of memory, or lots of visitors at once. Note the times and send them to support, and we can see what happened on the server.

Didn't find the answer?

Reply within 1 working day · Mon–Fri 8:00–17:00 CET