{"id":4599,"date":"2026-08-23T09:25:05","date_gmt":"2026-08-23T09:25:05","guid":{"rendered":"https:\/\/ownwebservers.com\/kb\/?p=4599"},"modified":"2026-08-23T09:25:05","modified_gmt":"2026-08-23T09:25:05","slug":"change-php-version-ssh-shared-hosting","status":"publish","type":"post","link":"https:\/\/ownwebservers.com\/kb\/change-php-version-ssh-shared-hosting\/","title":{"rendered":"How to Use SSH on Shared Hosting Plans to Change PHP Version"},"content":{"rendered":"\n

When managing a website, you often need to juggle multiple tools, scripts, and frameworks that require different PHP versions. While most hosting control panels make it easy to change the PHP version for your website, handling that same version through a command-line interface can be less intuitive. If you’re running scheduled tasks, testing custom scripts, or managing deployments, you need your command-line environment to match your web environment.<\/p>\n\n\n\n

For small business owners managing their own infrastructure, tapping into your server via SSH saves time. Instead of navigating a graphical interface every time you need to run a quick command, you can handle it directly from the terminal. Here’s how to safely and effectively change your PHP version via SSH on shared hosting plans.<\/p>\n\n\n\n

Enabling SSH Access on Shared Hosting Plans<\/h2>\n\n\n\n

Before you can run any commands, you’ll want to make sure your hosting account actually has SSH access enabled. On shared hosting, SSH is sometimes disabled by default for security reasons. Modern shared hosting environments provide multi-PHP support, but access to the command line must usually be explicitly activated via your control panel.<\/p>\n\n\n\n

Locating SSH Access Features in the Hosting Control Panel<\/h3>\n\n\n\n

Log into your cPanel (or equivalent hosting dashboard) and look for the “SSH Access” or “Terminal” icon. If you’re using cPanel, you’ll often find a built-in terminal right in the dashboard, which requires no additional setup. If you prefer using an external client like PuTTY or macOS Terminal, you’ll need to ensure your IP address is whitelisted and your SSH credentials are active.<\/p>\n\n\n\n

Generating and Registering SSH Keys for Authentication<\/h3>\n\n\n\n

For a secure connection, password authentication is acceptable, but SSH keys are much safer. From your local terminal, you can generate a key pair using the following command:<\/p>\n\n\n\n

ssh-keygen -t ed25519 -C \"your_email@example.com\"<\/code><\/pre>\n\n\n\n
Once generated, you’ll need to upload the public key (id_ed25519.pub<\/code>) to your hosting control panel under the SSH Access section. This registers your local machine as a trusted client, allowing you to log in without typing your account password each time.<\/p>\n\n\n\n
Understanding PHP CLI Execution vs. Web Server PHP<\/h2>\n\n\n\n
A common stumbling block for server administrators is realizing that the PHP version serving your website does not automatically dictate the PHP version used when you type php<\/code> in SSH. These are two separate execution environments.<\/p>\n\n\n\n
The Distinction Between MultiPHP Manager Web Settings and CLI Binaries<\/h3>\n\n\n\n
When you use the MultiPHP Manager in cPanel to set your domain to PHP 8.1, you’re telling the web server (Apache or LiteSpeed) which interpreter to use for HTTP requests. However, your SSH session relies on the system’s command-line interface (CLI) binary path. Sometimes these are synchronized, but often they drift, meaning running a Composer install or a custom cron job might execute under an older PHP version like 7.4.<\/p>\n\n\n\n
Verifying the Active CLI PHP Version with php -v<\/h3>\n\n\n\n
To see exactly what your command line is currently using, simply run:<\/p>\n\n\n\n
php -v<\/code><\/pre>\n\n\n\n
This will output the active CLI PHP version and should be run immediately after modifying any environment variables or shell profiles to confirm your changes took effect.<\/p>\n\n\n\n
Executing PHP Scripts via Specific Versions in SSH<\/h2>\n\n\n\n
If you only need to run a specific script under a newer PHP version without changing your global CLI configuration, you can bypass the default version entirely.<\/p>\n\n\n\n
Using cPanel cpcli for Synchronized CLI and Web PHP Versions<\/h3>\n\n\n\n
In cPanel environments, the cpcli<\/code> utility is incredibly helpful. It allows you to run PHP scripts from the command line using the exact PHP version configured for that specific domain in MultiPHP Manager. This ensures synchronization across both web and CLI environments. You can typically use it like this:<\/p>\n\n\n\n
cpcli php \/home\/username\/script.php<\/code><\/pre>\n\n\n\n
Calling Direct PHP Binaries Using Absolute Paths<\/h3>\n\n\n\n
If cpcli<\/code> is unavailable or you want targeted version execution, administrators use absolute binary paths. Most modern shared servers store multiple PHP versions in specific directories. For example:<\/p>\n\n\n\n
\/opt\/remi\/php81\/root\/usr\/bin\/php \/home\/username\/script.php<\/code><\/pre>\n\n\n\n
For cPanel servers using EasyApache 4, the paths look slightly different but follow the same structure:<\/p>\n\n\n\n
\/opt\/cpanel\/ea-php81\/root\/usr\/bin\/php \/home\/username\/script.php<\/code><\/pre>\n\n\n\n
This forces the script to run under PHP 8.1 regardless of what the default php<\/code> command is symlinked to.<\/p>\n\n\n\n
Overriding the Default PHP CLI Version via Shell Profiles<\/h2>\n\n\n\n
If you frequently use the command line and don’t want to type out absolute paths every single time, you can modify your shell profile to change the default PHP version for your user session.<\/p>\n\n\n\n
Configuring PHP Version Aliases in .bashrc<\/h3>\n\n\n\n
If your shared hosting platform supports a .bashrc<\/code> profile, you can create an alias for the PHP version you prefer. First, verify the exact path of the PHP binary you want to use. Then, edit your .bashrc<\/code> file:<\/p>\n\n\n\n
nano ~\/.bashrc<\/code><\/pre>\n\n\n\n
Add the following line to create a shortcut that overrides the default binary path:<\/p>\n\n\n\n
alias php='\/usr\/local\/bin\/php81'<\/code><\/pre>\n\n\n\n
Be sure to replace the path with the actual absolute path for the PHP version on your specific server.<\/p>\n\n\n\n
Reloading Shell Profiles and Validating the New Default Version<\/h3>\n\n\n\n
The alias won’t take effect in your current session immediately. You must reload the shell profile by running:<\/p>\n\n\n\n
source ~\/.bashrc<\/code><\/pre>\n\n\n\n
<p”Now, run php -v<\/code> again. It should now report the new version you assigned.<\/p>\n\n\n\n
Managing php.ini Settings Without Root Access<\/h2>\n\n\n\n
<p-Changing the PHP version is only half the battle; configuration settings like memory limits and execution times are equally important. On a shared server, you don’t have root access.<\/p>\n\n\n\n
Shared Hosting Restrictions on Global php.ini Modifications<\/h3>\n\n\n\n
You cannot alter the global php.ini<\/code> file via SSH because it affects every user on the shared server. Attempting to edit it will result in a permission denied error. Configuration changes must be made using the INI editor in the hosting control panel.<\/p>\n\n\n\n
Applying Local php.ini Files for Directory-Specific Configuration<\/h3>\n\n\n\n
If you need specific settings for a single application or directory, you can create a local php.ini<\/code> file in that directory via SSH:<\/p>\n\n\n\n
nano \/home\/username\/public_html\/app\/php.ini<\/code><\/pre>\n\n\n\n
Add your custom directives here, such as memory_limit = 256M<\/code>. Note that on some servers running PHP-FPM or LiteSpeed, local php.ini<\/code> files are ignored, and you must use .user.ini<\/code> instead. If your changes aren’t taking effect, try renaming the file:<\/p>\n\n\n\n
mv php.ini .user.ini<\/code><\/pre>\n\n\n\n
Troubleshooting Common SSH PHP Issues<\/h2>\n\n\n\n
            <td_USE_the_absolute_path (e.g., \/opt\/cpanel\/ea-php81\/root\/usr\/bin\/php<\/code>) or add an alias in your .bashrc<\/code> file.\n<\/p>\n\n\n\n
Symptom<\/th>Cause<\/th>Fix<\/th><\/tr><\/thead>
-bash: php: command not found<\/code><\/td>The PHP binary is not in your user’s PATH environment variable.<\/td><\/tr>
Editphp.ini results in permission denied error.<\/code><\/td>You’re trying to edit global server configuration without root privileges.<\/td>Create_a_local_.user.ini file in_your web directory instead.<\/code><\/td><\/tr>
Cron jobs run an older PHP version despite .bashrc alias.<\/td>Cron doesn’t load user shell profiles automatically.<\/td>Edit_your_crontab_and_replace_’php’_with_the_full_absolute_path (e.g., \/opt\/cpanel\/ea-php81\/root\/usr\/bin\/php).<\/td><\/tr>
<\/td>Your hosting provider doesn’t include cPanel’s cpcli utility or uses an alternative control panel.<\/td>Rely_on_direct_binary_execution_using_absolute_paths_from_\/opt\/cpanel\/ea-phpXX\/root\/usr\/bin\/php.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Troubleshooting Common Issues <\/h2>\n\n\n\n
            < USe_the_absolute_path_(e .g ., _\/opt\/cpanel\/ea-php80\/root\/usr\/bin\/php )_or_add_an_alias_in_your_.bashrc_file . \n\n            Edithttps : \/\/ permission denied error when editing php .ini
\n            td >You ‘re trying_to_edit_global_server_configuration_without_root_privileges . \/ td >
\n                td > Create_a_local_.user .ini_file_in_your_web_directory_instead . \/ td >
\n        \/ tr >
\n        Cron jobs_run_an_older_PHP_version_despite_.bashrc_alias .
\n        td > Cron_doesn ‘t_load_user_shell_profiles_automatically .\/ td >
\n Edit_your_crontab_and_replace_’php’_with_the_full_absolute_path_(e .g ., _\/opt\/cpanel\/ea-php81\/root\/usr\/bin\/php )._ fj
\n ) cpcli : _command_not_found
\n td > Your_hosting_provider_doesn ‘t_include_cPanel ‘s_cpcli_utility_or_uses_an_alternative_control_panel .\/ td >
\n Rely_on_direct_binary_execution_using_absolute_paths_from_\/opt\/cpanel\/ea-phpXX\/root\/usr\/bin\/php .\/ td >
\n    \/ tr >
\n\/tbody >
\n\/ table ><\/p>\n\n\n\n
<\/p>\n\n\n\n
Best_Practices_for_Managing_PHP_via_SSH 
<\/p>\n