01 / Platform and software / C.02How it works
C.02

PHP version manager

You manage PHP versions across every server from one list. Each row shows how many sites are stuck on an end-of-life PHP version, and you move them to a newer one in a single pass. Per-site version, extensions and php.ini settings live on the same screen.

Screen sheetC.02
Topic
C · Platform and software
Order
02 / 06
Points
06
Panel support
4 / 4 panels
02 / FigurePanel screen
Hover the numbers
app.ctapanel.com/phpPHP versions9 servers · 1,042 sitesMove EOL sitesSites1,042Active branch947Security only54End of life41no patchesServerSitesVersion spreadDefaultEOLweb01.fra2148.313web02.fra1988.3—web01.ams968.216rs01.nyc748.312Active branchSecurity fixes onlyEnd of lifeMove 41 sites to PHP 8.3?An incompatible extension becomes visible immediately, so the action is marked destructive.MoveCancel01020304
  1. 01End-of-life versionsVersions split into active, security-only and end of life; sites without patches are counted apart.
  2. 02Version spreadPer server: site count, each branch’s share and the load sitting on an end-of-life version.
  3. 03Server defaultThe MultiPHP Manager equivalent; newly created accounts inherit this version.
  4. 04Move in one goSites on an end-of-life version move to another one; the action is marked destructive.
Fig. 02 — PHP version manager
03 / What it does6 points

What it does.

You don’t log into a server to change one site’s php.ini. The settings are grouped in front of you, a value over its limit raises a warning, and you can go back to the default. Sites left on an end-of-life PHP version stop getting security patches, so the list counts them separately. Before a bulk move the panel warns you, because incompatible plugins show up the moment the version changes.

  1. The server list shows site counts, version spread and how many sites sit on an end-of-life branch. Each version is marked active, security only or end of life.

  2. The server default version (the MultiPHP Manager equivalent) is inherited by new accounts.

  3. Per-site settings: version, handler, php.ini directives, extensions and the FPM pool. Directives are grouped and warn you when a limit is exceeded.

  4. Handler options follow the panel, and a panel-less server is described by its systemd pool. Each panel also shows where the setting gets written.

  5. Move every site on an end-of-life version to another version in one go. The action is marked destructive.

  6. Reset php.ini to the package default.

04 / Panel-by-panel support4 / 4 panels

Which panels support it?

Capability PHP version and settings

  • yesManaged from the panel
  • yesManaged from the panel
  • yesManaged from the panel
  • yesManaged from the panel

Servers without a control panel have no account, reseller or mailbox management, because those come from the panel itself. Firewall, DNS, services and the terminal work over SSH. See the full table

05 / Platform and software6 screens

Platform and software

Every layer a site runs on top of.

06 / Get started14 days free · No card needed

Connect your first server today.

Free for 14 days, no card needed. Create your account, add your first server with an API token or an SSH key, and the panel starts filling in a few minutes later.

No setup fee · Cancel anytime · EU-hosted