Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My websites stopped working after a cPanel update

Short answer

cPanel and WHM can upgrade itself, and cPanel states you cannot downgrade between major versions or release tiers. So the fix is to find what changed, not to roll back. Write down the exact version and time, keep the update report, and ask your server's administrator to check PHP, mail and web server settings.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Several sites went down or show errors right after the server updated.
  • Email stopped working on the same day.
  • A site that ran for years now shows a PHP error.
  • My hosting company says the update was automatic.
  • The server administrator says it cannot be rolled back.

Why does this happen?

  1. Updates can run automatically

    cPanel applies available security updates for your current major version every hour through a scheduled job, even when version updates are set to manual. Servers on the RELEASE tier that upgrade automatically to a new major version wait several business days, chosen at random, so the day of the change may not be the day anyone expected it.

  2. There is no way back to the old major version

    cPanel states that you cannot downgrade a cPanel and WHM installation between major versions or between release tiers. That is why cPanel advises staging upgrades on a test system before updating production.

  3. The server may be on a risky release tier

    cPanel has five public tiers, LTS, STABLE, RELEASE, CURRENT and EDGE, and says to use EDGE only for testing in a controlled environment. A production server on a fast tier gets new versions sooner.

  4. Very old servers jump a long way at once

    cPanel warns that very old versions may have problems and may need an upgrade through an intermediate version first. A server that was left alone for a long time changes a lot in one go.

  5. The sites depended on old software

    An update can change the PHP versions on offer, mail settings and web server behavior. Old sites that relied on the earlier behavior then break.

What can I do about it today?

  1. Write down what you seeList which sites, which pages and which error messages, with the time you first noticed. Screenshots help.
  2. Ask the administrator for the update reportcPanel states that the atd daemon emails a report if the post-update health check finds errors. Ask whoever runs the server to forward it, and to say which version the server is on now.
  3. Do not try to downgradeBecause cPanel does not support it, attempts to roll back by hand can make things worse.
  4. Check whether the problem is one site or all sitesOne broken site points to that site's PHP version or settings. All sites and email together point to the server.
  5. Tell customers if they are affectedA short, honest message on social media or your phone line is better than silence while it is being fixed.
  6. Make sure a backup exists before further changesAsk the administrator to confirm that a recent copy of your sites and mail exists, kept away from the server.

When should I bring someone in?

  • Mail or customer-facing sites have been down for more than a few hours.
  • The person who set the server up is gone and nobody can log in to WHM.
  • The server is old and the same thing will happen at the next upgrade.

How do I handle it?

  1. Read what changed on the serverI check the update log, the installed versions of PHP, the web server and the mail service, and compare them with what the sites expect.
  2. Find the first thing that failsI start from the error log of one broken site and work back to the setting or version behind it.
  3. Fix forward, one site at a timeSince the update cannot be undone, I move each site to a PHP version it runs on, repair settings, and test each one before the next.
  4. Restore mail earlyMail comes back before the minor site problems, with a test message sent and received.
  5. Set up the next upgrade safelyI write down a checklist for the next update: a copy of the server, a test run and a time window, so it does not arrive as a surprise.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can the update be undone?

cPanel states you cannot downgrade between major versions or between release tiers. Work forward by fixing what changed.

Why did it update without anyone asking?

Security updates for the current major version are applied every hour by a scheduled job, and servers can be set to upgrade automatically. Whoever runs the server can see the setting in WHM's update preferences.

Is my data lost?

Usually not. An update changes software, not your files. Still, confirm that a separate backup exists before anyone changes anything else.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.