Fast Hive shared hosting lets you choose the PHP version for each domain independently, and adjust PHP settings without a support ticket. Two cPanel tools do the work: MultiPHP Manager for the version, and MultiPHP INI Editor for the settings. This guide covers both, plus how to change version safely without taking your site down.
- PHP 8.2 (
ea-php82) - the current system default - PHP 8.3 (
ea-php83) - PHP 8.4 (
ea-php84) - PHP 8.5 (
ea-php85)
Checking which version you are on
- Log in to cPanel from My Products & Services.
- Under Software, open MultiPHP Manager.
- The top of the page shows the System PHP Version - the default set by the server administrator.
- The table below lists every domain on your account with its current PHP version and PHP-FPM status.
A domain showing inherit has no version explicitly set and simply follows the system default. That is a good place to be: it means you are moved forward automatically as the platform default advances.
Changing the PHP version for a domain
- In MultiPHP Manager, tick the checkbox beside the domain you want to change.
- Choose the version from the PHP Version dropdown.
- Click Apply.
- The change takes effect immediately. Reload your website and check it.
Upgrading PHP without breaking the site
Newer PHP is meaningfully faster and receives security patches that older versions do not. But an upgrade is a code change, so treat it like one.
- Take a backup first. A partial backup of the home directory from Files → Backup takes under a minute.
- Update your applications, themes and plugins before touching PHP. Most breakage comes from out-of-date extensions rather than from your own code.
- Move up one version at a time. 8.2 to 8.3, test, then 8.3 to 8.4. Jumping several versions at once makes it far harder to identify what broke.
- Test the parts nobody looks at - contact forms, checkout, login, file uploads, PDF generation, scheduled tasks. The homepage almost always survives; the payment callback is what fails.
- Check the error log at Metrics → Errors straight afterwards, even if the site looks fine. Deprecation warnings there are your advance notice of the next problem.
- If something breaks, set the version back, then fix the underlying code before trying again.
Changing PHP settings with MultiPHP INI Editor
Software → MultiPHP INI Editor has two modes.
Basic Mode
Select the domain, then adjust the common directives with simple form fields:
| Directive | What it does | When to change it |
|---|---|---|
memory_limit |
Maximum RAM one script may use | "Allowed memory size exhausted" errors |
upload_max_filesize |
Largest single file upload | Media library rejects large images or video |
post_max_size |
Largest total form submission | Must be equal to or larger than upload_max_filesize, or uploads still fail |
max_execution_time |
Seconds a script may run | Long imports or backups timing out |
max_input_vars |
Number of form fields accepted | Large menus or theme option pages silently losing settings when saved |
display_errors |
Shows PHP errors on screen | Temporarily, while debugging - never on a live site |
Change the value, then click Apply.
Editor Mode
Editor Mode gives you a text box for directives that Basic Mode does not expose. Add one directive per line:
max_input_vars = 5000
default_socket_timeout = 120
date.timezone = Europe/Londondisplay_errors on for a live website. Error messages reveal file paths, database names and occasionally credentials to anyone who can trigger them. Debug with it on briefly, then turn it off and read Metrics → Errors instead.
Raising limits is not always the answer
A memory or timeout limit is a symptom as often as it is a constraint. Before raising a number, ask what is consuming it:
- A plugin leaking memory will exhaust 512 MB just as happily as 256 MB.
- An import that needs 300 seconds usually needs a smaller batch size, not a longer timeout.
- Every PHP process is also counted against your account's Physical Memory Usage ceiling, so raising per-script limits can mean fewer requests run concurrently.
Raise the limit to get unblocked, then find the cause.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| White screen immediately after changing version | A fatal error in code incompatible with the new version. Set the version back, then check Metrics → Errors for the file that failed. |
| Site works, admin area is broken | A plugin is incompatible. Rename its folder in File Manager to disable it, then update or replace it. |
| Settings in INI Editor have no effect | You edited the wrong domain, or your application overrides the value in its own code (WordPress does this with WP_MEMORY_LIMIT). Check the application config too. |
| Uploads still fail after raising upload_max_filesize | post_max_size is still lower. It must be equal or larger. Some applications also enforce their own separate limit. |
| Menu or theme settings silently truncated on save | Classic max_input_vars symptom. Raise it to 5000 in Editor Mode. |
| A required PHP extension is missing | Extension availability varies by version. Open a ticket with Technical Support naming the extension and the PHP version. |
| Changes seem to revert on their own | The domain is set to inherit, so it follows the system default. Set an explicit version if you need it pinned. |
Frequently asked questions
Which PHP version should I use?
The newest version your application fully supports. Newer releases are faster and receive security fixes; older ones eventually stop being patched. If your software is current, there is rarely a reason to stay behind.
Will changing the version affect my other domains?
No. MultiPHP Manager sets the version per domain, so you can move one site to PHP 8.4 while another stays on 8.2.
Is there downtime when I switch?
The change applies immediately with no meaningful interruption. The risk is compatibility, not downtime.
What does PHP-FPM do?
PHP-FPM is a process manager that handles PHP requests more efficiently than the traditional handler, usually improving performance under concurrent load. Its status per domain is shown in the MultiPHP Manager table.
Can I use a PHP version older than 8.2?
Not on this platform. Versions below 8.2 no longer receive security updates, and running unpatched PHP puts your site and the server at risk. If you have an application that requires an end-of-life version, talk to Sales & Solutions about a VPS where you control the stack - and plan to update the application.
How do I see my full PHP configuration?
Create a file in public_html containing <?php phpinfo();, load it in your browser, then delete it immediately. It exposes a great deal about your server and should never be left in place.
