Identify which setting controls the site

Start with the hosting account, domain and PHP handler actually serving the request. An account-level choice and a control-panel domain setting can refer to different parts of the configuration. Record both before changing either.

Check the result in the website environment

A shell command may show a different PHP environment from the one serving a website. Use a temporary, access-controlled diagnostic appropriate to the application and remove it afterwards. Avoid leaving public diagnostic pages that reveal server details.

Change one variable at a time

Confirm the application requirements, select a supported PHP version and review required extensions. Test the affected website before rolling a change across other accounts. Keep a route back to the previous working configuration.

Keep licensing separate from configuration

A CloudLinux activation issue and a PHP-handler configuration issue need different investigation. Use LicenseCage documentation for the license, and consult the panel and CloudLinux documentation for the applicable PHP configuration.

A practical example

A customer can select a PHP version in one interface while a domain continues to use another handler. That can occur when account-level preferences, domain settings and the panel's PHP integration are separate. Check what the affected website is actually using before assuming the selection failed, and remove any temporary diagnostic page after the test.

Checks to make

  • Identify the exact account and domain, rather than checking an unrelated website.
  • Compare the account's PHP choice with the domain-level handler and panel settings.
  • Verify the extensions and configuration required by the application under that handler.
  • Retest the affected request after changes and inspect the relevant error log.

Making the decision

Document the relationship between account defaults and domain overrides in your hosting policy. A server-wide PHP change may affect customers who were not part of the incident. Prefer a scoped adjustment after confirming how your panel and CloudLinux integration applies it.