LVE Manager is a plugin for most popular control panels including cPanel, Plesk, DirectAdmin and ISPmanager (InterWorx coming soon). It allows you to control and monitor limits, and set limits on per package bases.
LVE Manager is installed by default on most servers. If it is missing you can always install it by running:
$ yum install lvemanager
CloudLinux Installation Wizard allows you to easily install and set up CloudLinux OS components on your server with cPanel, Plesk or DirectAdmin.
As you have CloudLinux OS installed, navigate to CloudLinux LVE Manager in your control panel. CloudLinux Installation Wizard starts automatically if lvemanager
package is installed for the first time (not updated).
To start setting up your CloudLinux OS, click Start Wizard, otherwise click Skip Wizard, and you will be redirected to the LVE Manager Dashboard.
Note
Installation statuses of all components are duplicated inside their corresponding boxes on the Dashboard. All Wizard actions are available there as well. Dashboard will be automatically updated as soon as the installation process finishes.
The next step is selecting required components to be installed.
Click Finish and Install to complete installation or click Skip Wizard to go back to the Dashboard.
You can find a complete description of the CloudLinux components below.
A virtualized per-user file system encapsulates each customer into a ‘cage’ preventing them from seeing each other files and viewing sensitive information (e.g., system files)
Toggle the sliders to enable CageFS by default for new and/or existing users.
Note
CageFS is a requirement for PHP Selector operation.
It is the fastest and most reliable way to serve PHP pages for Apache web-servers, a drop-in replacement for SuPHP, FCGID, RUID2, and ITK.
LSAPI requires CRIU to operate and we also recommend you to use mod_suexec. You can find details in our documentation.
Monitors MySQL usage to throttle abusers, preventing server overload and improving overall performance.
Note
MySQL Governor can be automatically installed only with cPanel/WHM and DirectAdmin - use CLI instructions available here in all other cases.
We recommend you to create a full database backup before the MySQL Governor installation.
Allows end users to create Node.js applications and select the specific version of Node.js and other parameters.
Here you can choose versions to be installed and the version to be used as default.
Allows end users to select the specific version of Ruby they need.
Here you can choose Ruby versions to be installed.
Allows end users to select the default version of Python and set the required versions for installation.
Here you can choose Python versions to be installed.
Allows end users to select the specific version of PHP they need, with over 120 PHP extensions to choose from.
Go to LVE Manager settings to set up PHP Selector options and parameters. Read more in the PHP Selector documentation.
Note
CageFS should be enabled for PHP Selector to operate.
When the components to be installed are selected and configured, and installation is started, you will be redirected to the LVE Manager | Dashboard.
Installation status is displayed throughout the process in the Dashboard. Click Installing to show modules installation state.
All installed modules are displayed on the Dashboard. When installation is completed successfully, you will see the following status.
If you decide to remove failed module or a module to be installed by clicking the (X) button, a confirmation dialog will appear.
After confirming the action, the module will disappear from the list.
If module installation fails, the Installing button changes to Warning and the module indicator will turn red.
If module auto-installation fails, you will see that the module indicator turns yellow.
In this case, you can download a log for details and try to install the module again.
In case of a fatal error, you will see the following warning.
You can contact our support team for further assistance anytime by submitting a ticket in our helpdesk system.
cPanel LVE Manager administrator interface allows monitoring and managing limits for hosts end users, managing packages and monitoring statistics.
Administrator credentials allow controlling limits for host users.
Log in as administrator to get access to the following functionality:
For more details, please go to the ImunifyAV documentation.
In the LVE Manager UI we use the following color codes for notifications:
The following actions are available in the action notifications (error, success)
The following actions are available in the system notifications (information, warning):
Note
Available starting from LVE Manager 4.0-26.8
CloudLinux dashboard provides a quick overview of statistics and all administrative information for server administrators.
Go to LVE Manager | Dashboard.
The Cloudlinux Dashboard provides the following information:
Node.js Selector status (Enabled/Disabled/Not installed) — displays a current status of the Node.js Selector.
To manage Node.js Selector, click Manage. You will be redirected to LVE Manager | Options | Node.js Selector.
Click Install to install Node.js Selector, you will be redirected to LVE Manager | Options | Node.js.Selector.
Default version — the current default version of Node.js set in your system. Click Manage to change the default version account wide.
Applications — number of installed/all applications for the account.
Ruby Selector status (Enabled/Disabled/Not installed) — displays a current status of the Ruby Selector.
To manage Ruby Selector, click Manage. You will be redirected to LVE Manager | Options | Ruby Selector.
Click Install to install Ruby Selector, you will be redirected to LVE Manager | Options | Ruby Selector.
Applications — number of installed/all applications for the account.
Python Selector status (Enabled/Disabled/Not installed — displays a current status of the Python Selector.
To manage Python Selector, click Manage. You will be redirected to LVE Manager | Options | Python Selector.
Click Install to install Python Selector, you will be redirected to LVE Manager | Options | Python Selector.
Applications — number of installed/all applications for the account.
Note
cl_statistics_enabled=1
parameter to the /etc/sysconfig/cloudlinux
file.Choose Current usage tab to monitor users resource usage at the moment displayed in the table.
Current usage table provides the information on the usage of Speed, memory, IO, IOPS, Number of Processes, and Entry Processes.
Resource usage values are being refreshed every 10 seconds which is set in Auto-refresh field. You can refresh the table manually by clicking Refresh now or you can freeze the values by clicking pause button. Usage values will not change until the next manual refresh.
Tick Hide MySQL usage checkbox to hide the information on MySQL usage.
To expand the list of users click on the number above and in the dropdown choose the number of user to be displayed on the page.
The list of users can be filtered by Username and Domain.
Hoster can view all types of users:
But hoster can only manage:
To manage Reseller’s end users hoster should login as a reseller.
Choose Users tab to view the list of all users in the system and manage their limits.
Note
A hoster can view the list of resellers’ end users and their limits, but can not manage resellers’ end users limits (if those are set by reseller).
The following filters are available:
Also, you can search user by his Username, domain or LVE ID in the Search field.
Click pencil icon in Actions column to edit limits for a particular user. The following actions are available:
Click Save to save changes or Cancel to close the pop-up.
Click on History symbol to view the history of a particular user resource usage. Choose time frame to view the history for a particular time period.
Note
If CageFS is disabled, group actions are not available. See how you can enable CageFS:
View users with enabled CageFS
To view users with enabled CageFS, click Show only >> Users with CageFS enabled
Disable CageFS for several users
To disable CageFS for several users, do the following.
Choose Statistics tab to view end users, resellers and resellers’ end users limits usage statistics.
The following parameters can be displayed in the statistics table:
Click Show and select columns from the drop-down to set which parameters should be displayed in the table.
Statistics table can be filtered by:
Click Manage to choose type of users to be displayed - End users, Resellers, Resellers’ end users or Resellers’ end users (no Reseller limit) by ticking checkbox in the drop-down.
Click chart symbol in the View column to view the detailed resource usage history for a particular account. Use timeframe drop-down to view the history for a particular period of time.
The following sections are available to set the required options:
A hoster can set email notifications for panel administrator, reseller customer, and resellers’ customers in cases of limits faults. Choose Options tab to manage LVE Faults email notifications.
The following types of notification are available:
Tick checkboxes to include required limits to the notifications:
Set a number of faults required for the notification to be sent for:
Set the frequency of email notifications sending to:
Allows to reset inode limits and show/hide end-user inode usage.
Allows to manage user interface settings:
Allows to manage MySQL Governor settings.
MySQL Governor Mode of operation
MySQL Governor restrict type mode
Unlimit users automatically in
Allows to unlimit users automatically if they don't hit the limits during the specified number of seconds/minutes/hours/days.
Restricted time periods
User restriction time period for different levels of restriction and the timeout to apply a higher restriction level.
User maximum connections
The number of simultaneous connections of a restricted user (in the LVE mode).
Path to script
To be triggered when account is restricted.
MySQL Governor restrict-log file URL and format
MySQL Governor error-log file URL and logging level
Kill slow SELECT queries
Gather data for detailed statistics
Tick if yes.
Log restricted user's queries
Tick if yes.
Allows to manage CageFS settings:
Allows to enable/disable and manage Node.js Selector.
See more:
Allows to enable/disable and manage Python Selector.
See more:
When you've done with settings, click Save Changes to apply changes.
Packages tab allows setting the limits for as many users as you need by editing packages of proper limits. Each account belonging to a proper package adheres to those limits.
Note
Limits from the package will not be applied if the package’s owner differs from the owner of the account you’re trying to apply limits to. Default limits will be applied instead.
Choose Packages tab to view and modify:
To modify package limits click on a pencil symbol in Actions column in a particular package row. The following limits for this package are available for setting:
When limits are set click Save to apply changes or Cancel to close the window.
Selector tab allows controlling PHP Selector settings.
Enabled
or Disabled
from the dropdown list to enable or disable PHP Selector.Choose default modules from the list for a proper PHP version or for native.
Note
You can also use PHP Selector CLI
Go to cPanel admin interface → LVE manager → Selector
Selector tab has two sub tabs: Main settings and Domains.
Admin can filter the list:
If an admin clicks Use PHP selector in the Action table, the PHP version for a domain in MultiPHP Selector is changed to the system default version and php-fpm
is disabled. Users' websites will use the version set in CloudLinux PHP Selector (user interface). Group operation also can be used.
You can see the following errors in the Domains tab.
Solution
Initialize CageFS in the Options tab (see installation instructions).
Solution
Enable CageFS in the Users tab (see installation instructions).
Solution
If you cannot see Diagnostic tool notifications, you can restart it. Then you can fix the issues using these instructions.
The diagnostic tool allows to catch some issues. You can start diagnostic by clicking Run diagnostic button.
The most popular errors and solutions:
Solution: install mod_suexec
(see instructions here) and then run the following command:
cagefsctl --force-update
Solution: correct the file format via SSH.
php-fpm
enabled.Solution: see installation instructions for cPanel users
Solution: see installation instructions for cPanel users
In the LVE Manager v.6.0.6-1 the diagnostic tool can not catch problems with CageFS. See installation instructions for cPanel users.
Hoster interface allows to enable and disable Python Selector and manage individual Python versions.
Go to LVE Manager → Options Tab → Python Selector.
A list of installed Python versions is displayed. There are several columns in the list.
To display all changes immediately click Refresh.
To enable Python Selector move a slider to Enable and complete the action by clicking Agree or click Cancel to close the popup. To disable Python Selector move a slider back to Disable.
Note
If you disable Python, all users won't be able to manage their applications
Note
Python Selector icon in end user interface is hidden when Python is disabled.
In the list of installed Python versions you can enable and disable, install and delete, and set a particular Python version as a default.
To enable particular Python version do the following:
To disable particular Python version do the following:
To install particular Python version do the following:
To delete particular Python version do the following:
Note
It is impossible:
Note
You can set a particular Python version as a default version in the CloudLinux installation wizard during the first installation.
To make a particular Python version as a default version, do the following:
Note
It is impossible to make disabled Python version as a default version
To view and operate with the list of domains with Python versions click a number in the Applications column for a particular Python version. A section with a list of Domains for particular Python version will be displayed.
Domains are displayed by three. To load more domains click Load More button.
To change Python version for a particular application do the following:
Note
All packages of the application(s) will be re-installed.
Note
You can also use Python Selector CLI
See also: Python Selector client plugin
Hoster interface allows to enable and disable Node.js, and manage individual Node.js versions.
Go to LVE Manager → Options Tab → Node.js Section. A list of installed Node.js versions is displayed. There are several columns in the list.
To display all changes immediately click Refresh link.
Note
If you disable Node.js, its version for all your applications will not be changed, but you can not add a new application to this version.
Note
Node.js Selector icon in end user interface is hidden when Node.js is disabled.
The list of installed Node.js versions allows to enable and disable, install and delete, and set a particular Node.js version as a default.
To enable particular Node.js version do the following:
To disable particular Node.js version do the following:
To install particular Node.js version do the following:
To delete particular Node.js version do the following:
Note
It is impossible:
To make a particular Node.js version as a default do the following:
Note
It is impossible to make a disabled version default.
To view and operate with the list of domains with Node.js versions click on a number in the Applications column for a particular Node.js version. A section with a list of Domains for particular Node.js version will be displayed.
Domains are displayed by three. To load more domains click on Load More button.
To change Node.js version for a particular application do the following:
Note
All packages of the application(s) will be re-installed.
Note
You can also use Node.js Selector CLI
See also: Node.js Selector client plugin
Since alt-mod-passenger version 5.3.7-3 we have included support for the PassengerAppLogFile directive.
Syntax: PassengerAppLogFile path
Default: PassengerAppLogFile path-to-passenger-log-file
Context: virtual host, htaccess
By default, Passenger log messages are all written to the Passenger log file. With this option, you can have the app specific messages logged to a different file in addition. In alt-mod-passenger , you can use it in the context of a virtual host or in the htaccess file.
See also: Node.js Selector CLI tools.
Website monitoring tool is a new tool that collects the statistics of the domains' availability and responsiveness, as well as errors that occur when accessing these domains. An admin can get email reports with the statistics. The website monitoring tool uses the simple curl request like curl http://domain.com
to get domains’ statistics.
PHP Slow Site analyzer is a new tool that generates daily reports for the server administrator with information about the top N slow PHP-based domains and URLs. Slow Site analyzer tracks all PHP-based requests and selects slow ones by certain rules.
Note
Slow Site analyzer is not available for CloudLinux 6.
Installation
To install the tool, run the following command:
yum update lvemanager
Warning
For now, there is no any possibility to remove the alt-php-ssa
and cl-web-monitoring-tool
packages so that the Website monitoring tab will be removed. This possibility will be added in the future releases.
You can turn off the Website monitoring, PHP Sites Analyzer in the Settings subtab, so sites statistics will stop collecting and there will be no additional load on the server.
You can configure the Website monitoring tool and Slow Site analyzer and view the daily reports in the LVE Manager -> Website monitoring tab.
There are Main, PHP Site analyzer, and Settings subtabs here.
This subtab views the latest report (for the previous day) of the Website monitoring tool.
Remember that report is created every 24 hours and all changes in configuration (the Settings tab) or in the list of domains will be applied for the next 24 hours (from midnight).
Total number of requests - requests that were sent to all domains, existing on the servers
Successful requests - the number of requests for all domains with
Requests with errors - the number of requests for all domains which status code is not 200
Not started requests due to short check interval - this metric is used to adjust configuration. If it is not equal 0, an admin should increase the value of Requests sending interval, because the tool does not fit into this interval to send requests to all domains.
Slowest websites in 24h and Websites with most errors in 24h - in these sections you can find the number of domains that was exposed here.
Note
The Slow Site analyzer is not available for CloudLinux 6.
This is an example of a report from the Slow Site analyzer. The report shows the number of slow requests per domain and its URLs and the average duration of each slow URL.
You can find the explanation of the Slow requests density in period here.
Here, an admin can configure the Website monitoring and the PHP Site analyzer.
Note
All settings which was changed after starting Website monitoring and Slow site analyzer will be applied for the next 24h (from midnight).
To enable or disable Website monitoring, use the following slider.
HTTP 408
error.To enable or disable the Slow site analyzer, use the following slider.
Note
Slow Site analyzer is not available for CloudLinux 6.
We try to find the most interesting requests for the optimisation from all number of requests to domains during 24 hours. The Density threshold parameter helps to find the most visited URLs and the most popular requests.
A density threshold is a numerical measure of some type of correlation, meaning the power of the statistical relationship between slow requests and all requests to the domain. If this parameter is enabled then the resulting table will contain slow requests that have exceeded the specified threshold. Requests with the highest density are usually the most distributed per day and are considered valuable to users, thus interesting for optimization.
Slow requests that represent bursts of activity and are weakly related to all activity per domain typically have a low density and will be weeded out.
Email notifications are created by the Web monitoring tools.
Example of the Web monitoring tools report.
Example of the PHP Slow site analyzer report.
Q: Does this feature consume a lot server resources for collecting website and PHP data? If I enable it can this slow down the server?
A: The load depends on the number of websites and the Website monitoring tool settings. Basically, the Website monitoring should not create a significant load and you can keep it always on.
Q: Can I change the default value to 10, for example for the "Top N slow websites to show" setting?
A: This number is simply the number of the slowest responding sites. All sites are sampled during the day. When generating a report, all sites' responses are sorted by response time from highest to lowest, and to make the report readable, only the first N sites are taken. You can specify N as all existing sites or only the 5 slowest. This number does not affect the server load, it only affects the report that will be visible in the UI or emailed to the administrator.
Q: What would you recommend: to enable the Website monitoring tool for some days and then disable or I can keep it always turned on?
A: The load depends on the number of websites and the Website monitoring tool settings. Basically, the Website monitoring tool should not create a significant load and you can keep it always on.
Reseller interface is designed to manage limits for resellers’ end users, to monitor statistics and the history of resource usage and to modify reseller’s end user packages limits.
Log in under a particular reseller credentials to have access to the following functionality:
WARNING
Reseller can manage all his end users via Reseller Interface. Reseller cannot manage INODE or MYSQL limits, neither his own nor for his users.
Current usage table provides the information on the usage of the following:
Resource usage data is being refreshed every 10 seconds which is set by default in Auto-refresh field. You can set Auto-refresh time by choosing the value from the drop-down.
You can refresh the table manually by clicking Refresh now or you can freeze the values by clicking pause button.
Usage values will not change until the next manual refresh. To unfreeze click on unpause button. The countdown will continue.
WARNING
Reseller cannot manage INODE or MYSQL limits. Neither his own, nor for his users.
The bottom line star in the table displays the total reseller resource usage. It means, that all the usage of resellers’ end users and of his own is displayed as a summary for each parameter.
Choose Historical Usage tab to view reseller and resellers’ end users resource usage history and faults. The list of users can be filtered by Timeframe.
When reseller’s end user reaches the limits set by hoster for the reseller, this will be displayed on the chart.
Note
In this case reseller’s end user would not necessarily reaches his limits set by the reseller. These faults are not displayed on the chart.
On the Historical Usage page the reseller is also able to see the list of Top 5 Reseller’s end users (based on resource usage, for the same period as charts/overall usage). Click History in the Actions column to view resource usage statistics for particular user.
Click LVE Statistics on the top of the Top 5 list to go to the Statistics page to view or manage the rest of users.
Choose Users tab to view and manage the list of all resellers’ end users and resource usage limits provided for them. The following limits are available for the resellers’ end users:
You can filter the list by Username, Domain, LVE ID.
Tick Show only ignored users to display only users with MySQL Governor disabled.
Click on a pencil icon in Actions column to edit limits for a particular user. The following actions are available:
Choose Statistics tab to view resource usage limits statistics.
Statistics table can be filtered by Timeframe, Limit, Top LVEs, LVE approaching limit, Fault LVE.
The following parameters are displayed:
Use Charts in the View column to view detailed resource usage charts for a particular period of time.
For example, 7 days period chart.
Choose Options tab to set user email notifications for resellers’ end users.
In LVE Faults email notifications section tick appropriate checkboxes to set the required type of notification.
In Faults to include section tick checkboxes to include particular limits to email notifications.
In Minimum number of Faults to notify section enter the number of faults required for the notification to be sent for reseller and customer. You can also set the reseller notification frequency.
Set the frequency of sending the reseller email notifications in Notify Reseller Every ... days/hours/minutes/seconds section.
Click Save Changes to apply changes.
Choose Packages tab to view and modify limits for reseller’s packages.
Click pencil icon in a package row to set the following limits for a package:
When limits are set click Save to apply changes.
Note
Requires LVE Manager 2.0-33+
It is possible to apply branding to the LVE Plugins in cPanel end users’ interface. To brand the cPanel end users' interface please do the following:
Create a script that will patch LVE Manager files (with branding data, for example, image and logo) after every update of lvemanager rpm
package;
Locate this script in /usr/share/l.v.e-manager/branding_script
;
Make this script executable by running the command:
chmod a+x /usr/share/l.v.e-manager/branding_script
When done, the branding script will be executed while every update of lvemanager package and all branding changes will be applied in the end user’s interface.
Note
Modifying the LVE Manager WHM plugin (/usr/local/cpanel/whostmgr/docroot/cgi/CloudLinux.cgi
) via branding_script
is not allowed.
Since version 1.0-4 LVE Manager acquired a feature of adding user messages to PHP versions*. To add a message, you should create a file in /opt/alt/phpXX/name_modifier
with a message that you want to be shown to a user.
For example, if you need to add the following message Don't use this PHP version
to PHP version 4.4, you should create the following file:
/opt/alt/php44/name_modifier:
echo 'Don`t use this php version' > /opt/alt/php44/name_modifier
As a result, LVE Manager will automatically pick up this message and will show it in web-interface to administrator (see Figure 1.1 for cPanel, Figure 1.2 for DirectAdmin) and to user (see Figure 2.1 for cPanel, Figure 2.2 for DirectAdmin). You can add messages to other PHP versions this way as well.
![]() |
Figure 1.1 cPanel LVE Manager (administrator) |
![]() |
Figure 1.2 DirectAdmin LVE Manager (administrator) |
![]() |
Figure 2.1 cPanel LVE Manager (user) |
![]() |
Figure 2.2 DirectAdmin LVE Manager (user) |
Note
*For cPanel and DirectAdmin only.
Client resource usage plugin for cPanel, Plesk, and DirectAdmin allows host’s end users to view and monitor resource usage.
Go to your control panel and click CPU and concurrent connection usage.
Here you can see three tabs:
Go to the Dashboard tab to see the general condition of your site. If your site is limited, you can see this on the Dashboard with the resource you are limited over. To see detailed information about resource usage, click Details.
If your site is not limited, you will see the plain Dashboard.
Go to the Current Usage tab to see the detailed information about resource usage on your server.
Note
It's possible to add the normalized_user_cpu = N
value to the /etc/sysconfig/cloudlinux
file. So you can see for example CPU Usage X/200 (%) in the scenario where a user's LVE CPU limit is 200%. If the value is equal to Y
, CPU Usage cannot get greater than 100%.
The Current Usage table displays resource usage.
Warning
Inodes usage is displayed if it is enabled and Inodes limits are set for the user. cPanel only.
You can filter charts and the Usage table by timeframe and time unit (day, hour, minute).
The following resources are displayed in charts:
All charts have the color legend:
You can also see the Faults chart with all faults for all resources.
The Usage table displays information on each resource usage sorted by timeframe and time unit.
Use controls below the table to navigate through it.
Go to the Snapshot tab to see server snapshots with processes list and database and HTTP queries.
You can choose a date and a snapshot to display in the table.
In case when a CloudLinux user hits LVE limits, appropriate faults are generated and lvestats package generates server processes snapshot. Snapshot is a list of running applications and a list of running MySQL queries right after the faults happened.
Snapshots allow users to investigate the reason of account hitting its limits. Several snapshots are generated for each incident. An incident is a state when faults are generated in a close time period. The time period is configurable. By default, if faults are generated in 300 seconds time period, we consider them as a single incident.
The snapshot configuration options are available in
/etc/sysconfig/lvestats.config/SnapshotSaver.cfg
period_between_incidents = 300
by default, time in secondssnapshots_per_minute = 2
by default, maximum number of snapshots per minutemax_snapshots_per_incident = 10
by default, maximum number of snapshots for an incidentTo access Snapshots you can also use lve-read-snapshot utility.
Note
The list of processes in a snapshot is close but not similar to the real processes list when faults were generated. It happens because of delay when the faults are happened and the snapshot is taken by the system.
The list of MySQL queries is an output of a query:
SELECT command, time, info FROM information_schema.processlist
WHERE user = '%username';
Displays information on processes in the selected snapshot.
Displays information on database queries in the selected snapshot.
Displays information on HTTP queries in the selected snapshot.
Note
Python Selector icon in end user interface is hidden when Python is disabled
End User interface allows end users to setup and manage Python for their web applications.
Go to cPanel → Software Section → Setup Python App.
Web Applications page is displayed.
There are several columns in the list:
Click Create Application to create an application. The Create Application tab opens.
Specify the following:
passenger_wsgi.py
;application
;Optionally, add environment variable. To do so, click Add Variable and specify variable name and value, then click the Done or Cancel to close an adding form.
To delete or edit environment variable, click Bin or Pencil for the required variable.
To start a stopped application do the following:
To stop a started application do the following:
To restart a started application do the following:
To remove application do the following:
To edit application do the following:
The following actions are available:
NAME.py
file.Click Save to save all changes or Cancel to close the tab.
For details see How to migrate an application to the new Python Selector
Note
You can also use Python Selector CLI
Note
Node.js Selector icon in end user interface is hidden when Node.js is disabled.
End User interface allows end users to setup and manage Node.js for their web applications.
Go to cPanel → Software Section → Setup Node.js App.
Web Applications page is displayed.
There are several columns in the list.
To start a stopped application do the following:
To stop a started application do the following:
To restart started application do the following:
To remove application do the following:
To edit application do the following:
The following actions are available:
Note
You can also use Node.js Selector CLI
End user interface allows end users to setup and manage Ruby for their web applications.
Go to cPanel → Software Section → Setup Ruby App.
Setup Ruby application page is displayed.
Here you can do the following:
End user interface allows end users to select and manage PHP extensions and options for the particular PHP version.
Go to cPanel → Software Section → Select PHP Version.
PHP Extensions page opens.
Here you can choose extensions for the particular PHP version, the current PHP version and reset to default.
To manage PHP options, click Switch to PHP options.
All changes are saved automatically.
allow_url_fopen
. Allows PHP file functions to retrieve data from remote locations over FTP or HTTP. This option is a great security risk, thus do not turn it on without necessity.display_errors
. Determines whether errors should be printed to the screen as part of the output or if they should not be shown to a user.error_reporting
. The error reporting level.file_uploads
. Allows uploading files over HTTP.include_path
. The list of directories where scripts look for files (similar to system's PATH variable). To separate directories, use a colon (:
) For example: .:/dir/inc:/usr/lib/php
log_errors
. Tells whether to log errors. By default, errors are logged in the server's error log. Use the error_log directive to specify the path to your own log file.mail.force_extra_parameters
. Additional parameters for the mail() function used to send mail. For example, to use your custom Sendmail configuration: -C /dir/conf.cf
max_execution_time
. The maximum time in seconds a script is allowed to run before it is terminated.max_input_time
. The maximum time in seconds a script is allowed to parse input data.memory_limit
. The maximum amount of memory in bytes a script is allowed to allocate. Set the value to -1 to have no memory limit (not recommended). Use shortcuts for byte values: K (kilo), M (mega), and G (giga). For example, 128M.open_basedir
. The list of directories used to limit the files that can be opened by PHP. If the file is outside the specified directories, PHP scripts will refuse to open it. To separate directories, use a colon. For example: /dir/upload:/usr/tmp
.post_max_size
. The maximum size in bytes of data that can be posted with the POST method. Typically, should be larger than upload_max_filesize
and smaller than memory_limit
. Use shortcuts for byte values: K (kilo), M (mega), and G (giga). For example, 16M.session.save_path
. The directory where PHP writes session data (files). For example: /dir/tmp
short_open_tag
. Allows the short form of the PHP open tag.upload_max_filesize
. The maximum size in bytes of an uploaded file. Use shortcuts for byte values: K (kilo), M (mega), and G (giga). For example, 128M.The My Domains tab contains a list of user’s domains to visualize which PHP Selector is used by domain.
A user can configure a domain to use CloudLinux PHP Selector.
Note
If php-fpm
is enabled for a domain the only administrator can set it to disable.
You can change LVE Manager settings for a server manually via cPanel/WHM or, if you have many servers, you can change LVE Manager settings for them in the config file.
You can modify the following options in the config file /var/cpanel/cpanel.config
directly for example via Puppet.
lve_hideextensions | Hides (when =1) range of php extensions for user in Select PHP version |
lve_hideuserstat | Hides (when =1) LVE statistics in cPanel Stats Bar (UI) |
lve_showinodeusage | Displays (when =1) used inodes in cPanel (UI) |
lve_hide_selector | Turns off UI PHP Selector (Select PHP Version option) |
lve_enablerubyapp | Displays (when =1) Ruby Selector in user’s interface (UI) |
Note
It is not allowed to change lve_enablepythonapp
option in the config file directly.
You can use cloudlinux-selector
utility to change lve_enablepythonapp
option:
cloudlinux-selector set --json --interpreter=python --selector-status=enabled
Or you can change it via WHM -> LVE Manager -> Options -> Python Selector -> Python
After modifying the config files directly, you should execute the following command to apply changes:
/usr/share/l.v.e-manager/utils/dynamicui.py --sync-conf=all
Note
LVE Manager 1.0-9.8+
cPanel LVE Extension allows to control LVE limits for packages via cPanel hosting packages control interface and via cPanel WHM API . It simplifies integration with existing billing systems for cPanel (like WHMCS for example).
To add LVE Settings to standard cPanel package, go to Packages | Add a Package.
Note
You can find the information on how to add a package in official cPanel documentation on the link: https://documentation.cpanel.net/display/ALD/Add+a+Package
Tick LVE Settings in the bottom of the page to open LVE Settings form.
You can specify the following options:
Note
Your changes to LVE Settings will appear in the system after a little while.
Speed Settings | Maximum CPU usage for an account. Must be in the range 1 - 100 (but obligatory > 0 ) if old format is used; use % or Mhz\Ghz to set CPU limit as speed; Type DEFAULT to use default value. |
Memory Settings | Pmem - Maximum physical memory usage for an account. Vmem - Maximum virtual memory usage for an account. Must be a positive number. Postfix allowed only in KGMT . Type DEFAULT to use default value. Type 0 for unlimited resource. |
Max entry proc Settings | Maximum number of entry processes (concurrent connections) for an account. Must be a positive number. Type DEFAULT to use default value. Type 0 for unlimited resource. |
Nproc Settings | Maximum number of processes usage for an account. Must be a positive number. Type DEFAULT to use default value. Type 0 for unlimited resource. |
IO Settings | Maximum I/O (input/output) usage speed for an account. Is measured in Kb/s . Must be a positive number. Type DEFAULT to use default value. Type 0 for unlimited resource. |
IOPS Settings | Maximum IOPS (input/output operations per second) usage for an account. Must be a positive number. Type DEFAULT to use default value. Type 0 to unlimited resource. |
Click Add to apply your changes.
You can edit limits in any convenient for you way - in Edit a Package section, in the LVE Manager or even via WHM API.
Edit a Package
To edit package extensions, go to Packages | Edit a Package. Choose a package from the Package list and click Edit.
LVE Manager
To edit package extensions, go to LVE Manager | Server Configuration | CloudLinux LVE Manager | Packages and click pencil (edit) icon.
WHM API
To learn how to work with package extensions limits using WHM API, please read the official cPanel documentation: https://documentation.cpanel.net/display/SDK/Guide+to+Package+Extensions+-+Data+Behavior+and+Changes
Here you will find the instructions and common techniques used to integrate your software with CloudLinux.