View a hosting account's technical sheet

Open the service in Hosting and go to Technical sheet. On a multi-account plan, first open the client's account: the inventory belongs to that account, not to the whole reseller plan.

The sheet is read-only. It gathers information obtained from the server and splits it into tabs:

• PHP, with the default version and the version of each website and where it comes from.
• Domains, with the document root and the application detected.
• Cron, with the schedule and command of each scheduled task.
• Forwarders, with the configured destinations.
• FTP, with the accounts and their directories.
• ModSecurity, with the status for each domain.
• Permissions, with the paths worth reviewing.
• Account, when available, with the general details and DNS brought in from the old Settings page.

Each website's PHP version

The PHP tab shows your hosting's default version and, below it, each website and each folder with its own version. For each one you can see the version it uses and where it comes from: the default version, its own version set in its .htaccess (with the file that sets it) or one inherited from a parent folder. If a website runs on a version its application doesn't declare as compatible, the row says so.

The sheet doesn't change anything. To change a website's version, open its row: it takes you to its page in PHP, with a compatibility study, a check and a way back. Manage PHP opens the full PHP screen and Change in cPanel opens the direct tool, which doesn't include that check.

Update the inventory

The header shows when the account was read. Click Update if you've just created a domain, a task, an FTP user or any other item and it doesn't appear yet. The update may take a while; don't repeat changes in cPanel just because the previous reading is still showing.

Share information for a review

The sheet describes a reading of the account; it isn't proof that each website works or a backup you can restore from. After changing a setting, also check the affected application.

Before attaching screenshots to a ticket or sending them to a collaborator, review the cron commands and the paths: they may contain private data or access parameters. Share only the tab and the details needed for the problem.