Software and Service Settings
Manage Apache, PHP versions, extensions, handlers and php.ini, install system packages and updates, and tune Apache, PHP, the FTP server, the database server and the services that run on the server.
This page covers the Software section of the admin menu (Web Stack Manager, PHP versions and extensions, php.ini, System Packages, Web Applications, system updates) and the pages of the Service Settings section for Apache, log rotation, the panel's web service, the FTP server, services and monitoring, PHP and the database server. The mail server (Exim) and mailbox server (Dovecot) settings are described with the other mail tools.
Long tasks such as installing packages run in the background, one at a time. The page that started a task shows its progress at the top; you can also follow it under Background Task Queue.
Web Stack Manager (Apache and PHP)#
In the admin area, open Software → Web Stack Manager (Apache and PHP) (/admin/stack). This page manages Apache and PHP as one "web stack".
- Installed Now sums up what the server runs at the moment: the Apache worker model (MPM), the PHP versions and extra packages. Show every package lists each part, for example
php83-php-intlormod_deflate. - Change opens the customize wizard starting from what is installed now (see "Customizing the web stack").
- Save as a profile stores what is installed now as a profile of your own, under the name you type. You can apply it later, or download it and upload it on another server to give both the same stack.
- Profiles lists the built-in profiles and your own (see "Web stack profiles").
- More web server settings links to PHP extensions, the PHP version of each domain, PHP settings, the php.ini editor, Apache configuration and Apache status.
- PHP handlers sets how Apache runs PHP for each PHP version (see "PHP handlers").
PHP comes from the Remi repository, one set of packages per version (for example php83-php-fpm, php83-php-gd). Every installed PHP version always has the base parts: PHP-FPM, the command line, mysqlnd, mbstring, xml, gd, opcache and zip. PHP 7.4 and 8.0 to 8.5 can be installed side by side.
Good to know:
- A PHP version that websites use, or that webmail and phpMyAdmin run on, is never removed by a profile or the wizard. It is kept and the task log says so.
- If Apache does not answer, the page shows a notice; try again a moment later.
Web stack profiles#
In the admin area, open Software → Web Stack Manager (Apache and PHP) and scroll to Profiles. A profile is a saved set of: an Apache worker model, the Apache modules to load, extra Apache packages, and the PHP versions with their extensions.
The built-in profiles (marked "intoPanel") are:
- intoPanel Default: event worker model, compression and browser caching, PHP 8.2 and 8.3 through PHP-FPM with bcmath, intl, soap, sodium and process.
- intoPanel Default + PHP 8.4: the default with HTTP/2 (mod_http2) and PHP 8.4 as well.
- All PHP Options + OPcache: PHP 8.1 to 8.4 with every common extension.
- Worker MPM: the threaded worker model with PHP 8.3.
- Prefork MPM + FastCGI: the prefork model with mod_fcgid, for websites that run PHP as FastCGI.
Profiles you saved are marked "custom". Each profile has these buttons:
- Apply installs and removes packages until the server matches the profile, switches the worker model, loads or unloads modules and reloads Apache. The progress shows at the top of the page.
- Change opens the profile in the customize wizard.
- Download saves the profile as a JSON file.
- Delete (custom profiles only) removes it.
To bring a profile from another server, use Upload a profile, choose the JSON file and click Upload.
Good to know:
- A profile name is 1 to 61 letters, digits, spaces and
. _ + ( ) -, and may not be the name of a built-in profile. You can keep up to 100 profiles of your own. - If a profile names packages this server cannot have, the profile shows a notice listing them; they are left out when it is applied.
- Applying a profile the server already matches does nothing ("nothing to change").
Customizing the web stack#
In the admin area, open Software → Web Stack Manager (Apache and PHP) and click Change on Installed Now or on a profile. The wizard has seven steps; nothing changes on the server until you click Apply Changes on the last one. Use the search box to find a package on the current step.
- Process Model (MPM): choose event (best with PHP-FPM), worker or prefork.
- Web Server Modules: tick the optional Apache modules to load. Modules that websites, PHP, HTTPS, ModSecurity or the panel need are always loaded and not listed.
- Choose PHP Versions: tick the versions to have. When you tick a new version, the wizard offers to install the extensions your other versions already have (Yes, with These Extensions or No, Base Extensions Only). When you untick an installed version, it warns you how many websites use it and whether webmail and phpMyAdmin run on it.
- Extensions per Version: tick extensions for each chosen version.
- Ruby, Python and Node.js: nothing to install here; these run through Web Applications.
- Other Software: extra Apache packages such as mod_http2, mod_fcgid, mod_security or mod_md.
- Check and Apply: review the list of changes and click Apply Changes.
Instead of applying, you can type a name and click Save as profile to keep the choice for later.
Good to know:
- Before you remove a PHP version that websites use, move them to another version under PHP Version per Domain. Before you remove the version webmail and phpMyAdmin run on, move them under PHP Versions. Otherwise that version is kept.
- Removing a PHP version removes all of its extensions too.
PHP handlers#
In the admin area, open Software → Web Stack Manager (Apache and PHP) and scroll to PHP handlers. A handler is how Apache runs PHP for the websites of one PHP version.
- PHP-FPM keeps a pool of PHP processes per website running. It is the fastest, comes with the panel and supports every feature.
- CGI (suEXEC) starts a PHP process for every request, as the account's user. Simple and strict, but slow.
- FastCGI (mod_fcgid) is like CGI but keeps the processes for the next requests. It must be installed first: click Install on its row (or Remove to take it away).
To change a handler:
- In the table of PHP versions, find the version. The table shows how many websites use it.
- Choose the handler in the list.
- Click Apply.
The configuration of every website on that version is rewritten and Apache is reloaded. If Apache does not accept the new configuration, the websites go back to the handler they had.
Good to know:
- With CGI and FastCGI a website's own PHP settings still apply, but per-website PHP extensions and the slow-request trace only work with PHP-FPM.
- When Account Isolation is switched on, PHP runs through PHP-FPM only, and Account Isolation cannot be switched on while a version uses CGI or FastCGI.
- mod_fcgid is kept while any PHP version still uses it.
PHP Versions#
In the admin area, open Software → PHP Versions (/admin/php). The menu items PHP Modules and PHP Versions and Extensions open the same page.
The table lists every PHP version the panel offers (7.4 and 8.0 to 8.5), whether it is installed and how many websites use it.
- Install installs a version with its base parts (PHP-FPM, command line, mysqlnd, mbstring, xml, gd, opcache, zip) and starts its PHP-FPM service.
- Remove removes a version. The button is disabled while websites use it.
- Extensions opens the extensions of an installed version. Each extension can be installed or removed with one click; the base extensions are marked "part of every version" and cannot be removed one by one. The extensions offered are bcmath, gd, intl, mbstring, soap, xml, opcache, mysqlnd, pgsql, ldap, imap, gmp, tidy, sodium, process, zip, imagick, redis, memcached, apcu, igbinary, mongodb, ssh2, yaml and ioncube-loader. Not every extension exists for every version; the task log says so if one cannot be installed.
Webmail and phpMyAdmin run on one PHP version, marked "panel" in the table. To move them, choose a version under Run webmail and phpMyAdmin on and click Move. They need PHP 8.1 or newer; the panel adds the extensions they need to that version first. When you remove the "panel" version, they move to the newest other installed version from 8.1 on by themselves; if there is none, install one first.
Good to know:
- Moving websites between versions is done under PHP Version per Domain.
- To change several versions and extensions in one go, use the customize wizard of the Web Stack Manager.
PHP Extensions#
In the admin area, open Software → PHP Extensions (/admin/mtool/php-extensions). This page decides, per PHP version, whether each installed extension is loaded for every website or only for the websites that ask for it.
- Choose the PHP version and click Show.
- The table lists the installed extensions, with the settings file each one comes from.
- for every website: the extension is loaded everywhere. Click Make optional to change that.
- optional, per website: only websites whose owner ticks it load it. Clients do this in the client area on the PHP Versions page. Click Load for every website to change it back.
- part of the engine: built into PHP; it cannot be made optional.
- To add an extension, type its package name under Install an extension (for example
imagick,redis,ioncube-loader,memcached) and click Install for PHP x.y. The packagephpXY-php-NAMEis installed from the server's PHP package source and loaded for every website.
Good to know:
- Make rarely used or heavy extensions optional, so that only the websites that need them pay for them.
- Some extensions are needed by others or by nearly every application; they stay loaded for every website.
- Per-website extensions work with the PHP-FPM handler only.
PHP Version per Domain#
In the admin area, open Software → PHP Version per Domain (/admin/mtool/php-domains). The table lists every website on the server (main domains, addon domains and subdomains) with its account and current PHP version. Domain aliases follow the website they belong to and are not listed.
To move websites to another PHP version:
- Tick the websites. The box in the header ticks all of them.
- Under Put the ticked websites on, choose the PHP version.
- Click Apply.
Clients can also choose the PHP version of their own websites in the client area.
Good to know:
- Use this page before you remove a PHP version: a version that websites still use cannot be removed.
- Only installed versions are offered. Install more under PHP Versions.
PHP Configuration#
In the admin area, open Service Settings → PHP Configuration (/admin/tuning?only=php). The menu item Software → PHP Settings per Version opens the same page. These are the server's standard PHP values for all PHP versions.
The settings are memory_limit, upload_max_filesize, post_max_size, max_execution_time, max_input_time, max_input_vars, display_errors, short_open_tag, allow_url_fopen and date.timezone. Leave a field empty to use PHP's own default. Values are checked: for example memory_limit is 16M to 2048M, upload_max_filesize and post_max_size up to about 2 GB, max_execution_time 1 to 3600 seconds.
Under Functions switched off for every website you can tick exec, passthru, shell_exec, system, proc_open, popen, pcntl_exec, show_source, symlink, link, dl, mail and putenv. These stay off for every website; clients cannot switch them on.
Click Apply to PHP to save. Each change is tested; if PHP refuses it, the previous settings stay.
See Suggested Settings works out values for this server from its memory, processors, load and disk. Review the list, untick what you do not want and click Apply the Ticked Settings. Suggestions are general advice for a hosting server of this size.
Good to know:
- Clients can set their own values per website within the same bounds.
- These settings are also written into each version's php.ini; see php.ini Editor.
php.ini Editor#
In the admin area, open Software → php.ini Editor (/admin/phpini). Choose the PHP version and click Open.
php.ini of PHP x.y shows the version's php.ini file itself. Edit it and click Save and reload PHP x.y. The file as it was before your first change is kept beside it as php.ini.intopanel-orig. If PHP does not start with what you saved, the previous file is put back.
Extra lines kept apart from php.ini is a separate box for additions, one name = value per line (lines starting with ; are comments). They apply to every website on that version and are kept in their own file. Saving an empty box removes that file.
Set among the common PHP settings shows the values that come from PHP Configuration. They are read last, so for the same setting they win over a line in the extra box.
Good to know:
- The ten common settings (memory_limit, upload_max_filesize and so on) are shared by all versions. Change one in php.ini and the common settings take it over and apply it to the other versions; change one among the common settings and it is written into each php.ini too.
- A website's own PHP settings from the client area still take precedence for that website.
- The editor accepts up to 256 KB for php.ini and 32 KB for the extra lines.
System Packages#
In the admin area, open Software → System Packages (/admin/mtool/install-packages). Here you can install operating system packages without a terminal.
- Type part of the package name (2 to 60 characters) and click Search.
- The results show each package's name, version and description. Installed packages are marked Installed.
- Click Install next to the package you want. The package is installed with whatever it depends on; the progress shows at the top of the page.
Only the first 200 matches are shown; type more of the name to narrow the list.
Packages come from the operating system's repositories set up on the server. This page only installs; to remove a package, use the Terminal. For Apache and PHP packages, use the Web Stack Manager instead, so the panel knows about them.
Repair the Package Database#
In the admin area, open Software → Repair the Package Database (/admin/mtool/rebuild-rpm). This rebuilds the list the server keeps of its installed packages (the RPM database).
Use it when installing or updating packages fails with database errors, for example after a crash or power loss during an update, or when the package manager reports a damaged database.
- Make sure no other long task is running, such as a System Update or a package install.
- Click Repair now. The progress shows on the page.
- When it has finished, try the install or update again.
Nothing is installed or removed; only the list is rebuilt from the packages that are on the disk.
Web Applications#
In the admin area, open Software → Web Applications (/admin/mtool/app-manager). Hosting accounts can run Node.js, Python and Ruby applications on their websites from the client area (Web Applications). Each account starts its applications as its own user, behind Apache. Here you install the languages and versions you want to offer.
The Web Applications: languages table lists:
- Node.js 18, 20, 22 and 24. Install downloads the version from nodejs.org and checks it against the published checksum. For an installed version, Update to the newest x.x fetches the latest release of that major version. Several versions can be installed side by side.
- Python 3.9, 3.11, 3.12 and 3.13, from the operating system's own packages. Not every Python version is offered for every release.
- Ruby: the system's version, from the operating system's packages. One version per server.
Applications on this server lists every application of every account: account, name, language and version, address, port and status (Running, Stopped, Failed or Restarting).
Good to know:
- How many applications an account may have is the "Passenger applications" limit of its package. The feature can also be left out of a package.
System Update#
In the admin area, open Software → System Update (/admin/updates). The menu item Update System Software opens the same page. It lists the updates available for the operating system: package name, new version and the repository it comes from.
To install them:
- Check the list.
- Click Install all updates. The server runs a full package upgrade; the progress shows on the page.
Updates come from the operating system and the other repositories the server uses. Services that are updated restart briefly.
If earlier updates need a server restart to take effect (for example a new kernel), the page says so. Restart at a quiet time under Restart the Server Safely.
Good to know:
- You cannot pick single packages here; it is all or nothing.
- This updates the operating system. Updates of the panel itself are under Update intoPanel, see Appearance, Languages and intoPanel.
Apache Configuration#
In the admin area, open Service Settings → Apache Configuration (/admin/apache). This page leads to the Apache settings that apply to the whole server, outside individual websites:
- Main Apache Settings: frequently used global directives.
- Folder Index Files (DirectoryIndex): which file names serve as a folder's index page.
- Custom Apache Directives: your own directives at three points of the configuration.
- Memory Limit for Apache Programs: RLimitMEM for programs Apache starts.
- Connection settings (quick form): the short form on the service settings page with Timeout, KeepAlive, KeepAliveTimeout, MaxKeepAliveRequests, ServerTokens and ServerSignature. Click Apply to Apache to save; Apache tests each change.
- Reserved IP Addresses: addresses that are not given to accounts.
- Log Rotation: how often web server logs are rotated.
Every change is tested by Apache before it is used. When Apache refuses it, nothing changes and you are told why.
The Apache worker model and modules are chosen in the Web Stack Manager. Apache's live status is under Apache Status, see Status and Monitoring.
Main Apache Settings#
In the admin area, open Service Settings → Apache Configuration and click Main Apache Settings (/admin/apache/global). For most settings, "Default" leaves the value to Apache.
- SSL Cipher Suite and SSL/TLS Protocols: the ciphers and TLS versions browsers may use over HTTPS. Keep TLSv1.2 on to work with all current browsers.
- OCSP Stapling (SSLUseStapling): sends proof that the certificate is not revoked, which speeds up the first visit.
- ExtendedStatus: shows more about each request on the Apache Status page.
- LogLevel: how much goes into the error logs (system default: warn).
- LogFormat (combined) and LogFormat (common): the format of the access logs. Do not change them unless you know the effect; data transfer figures and statistics read these logs.
- TraceEnable: whether Apache answers TRACE requests. Off is the safe choice.
- ServerSignature and ServerTokens: how much Apache tells visitors about itself.
- FileETag: which file properties make up the ETag used for caching.
- Options for the Root Folder: options for
Directory "/". - Worker numbers: StartServers, MinSpareServers, MaxSpareServers, ServerLimit, MaxRequestWorkers, MaxConnectionsPerChild, KeepAliveTimeout, MaxKeepAliveRequests (can be unlimited) and Timeout. Each is Default or a number of your own.
- Keep-Alive: lets a browser fetch several files over one connection.
Safe Symbolic Links is always on: a website follows a link only when the link and its target belong to the same account.
Click Save. Apache tests the result; if it refuses, nothing changes.
Folder Index Files and Custom Apache Directives#
In the admin area, open Service Settings → Apache Configuration.
Folder Index Files (DirectoryIndex) (/admin/apache/index) sets the file names that serve as a folder's index page. Write one name per line, most important first; the first one that exists in a folder is shown. Click Save, or Back to the default to restore the standard list. The order is written into every website, which takes a moment on a server with many websites.
Custom Apache Directives (/admin/apache/includes) adds your own directives at three points:
- Before the Main Section: read before all other settings of the panel and the websites.
- Before the First Website: read right before the first website (VirtualHost) entry.
- After the Last Website: read after the last website and after the panel's own settings, so what stands here wins.
Each box has its own Save button. Each save is tested by Apache first; when Apache refuses the text, the previous version stays in use and you are told what was wrong.
Good to know:
- Use custom directives with care: they apply to every website on the server.
Memory Limit for Apache Programs#
In the admin area, open Service Settings → Apache Configuration and click Memory Limit for Apache Programs (/admin/apache/memory). This sets Apache's RLimitMEM: a memory limit for each program Apache starts, not for all of them combined. It keeps the server more stable at the cost of a little speed.
- Choose On, at and enter the limit in MB (at least 64), or choose Off.
- Click Save.
The page shows the limit now set and a value suggested for this server.
Good to know:
- PHP runs in its own PHP-FPM pools with the memory limit set under PHP Configuration. This limit covers CGI programs started by Apache itself.
Log Rotation#
In the admin area, open Service Settings → Log Rotation (/admin/mtool/log-rotation). The web server's logs (one visitor log and one error log per website, plus Apache's own) are closed and started afresh at the interval you choose. Old files are kept beside them in /var/log/httpd.
Settings:
- Rotate: every day, every week or every month.
- Old log files to keep: 1 to 366.
- Also rotate when a log is larger than (MB): 0 means no size limit.
- Compress old log files: saves disk space.
Click Save. Example: "every week" and "4" keep about one month of logs.
Good to know:
- Data transfer figures are counted as the logs are written, so rotating does not lose them.
- In the client area, the visitor log pages show the current file.
- The same settings are reachable as Keeping Web Logs under Account Tools.
Panel Web Service Settings#
In the admin area, open Service Settings → Panel Web Service Settings (/admin/panel). This page is about the certificate the panel itself uses for HTTPS.
Current certificate shows whether it is self-signed or trusted, who issued it, the names it is valid for and when it expires. Browsers show a warning for a self-signed certificate.
To get a free trusted certificate from Let's Encrypt:
- Choose the hostname you will open the panel with, for example
panel.example.com. Its DNS A record must already point at this server, and it must not be a client's website. - Enter it under Panel hostname and click Get certificate. This takes up to a minute; keep the page open.
- From then on, open the panel as
https://your-hostname:port/.
The certificate renews automatically. The same page is reachable as Network → Panel Certificate.
FTP Server Settings#
In the admin area, open Service Settings → FTP Server Settings (/admin/tuning?only=ftp). These settings apply to the FTP server, Pure-FTPd.
MaxClientsNumber: most simultaneous connections in total (up to 1000).MaxClientsPerIP: most connections from one address (up to 100).MaxIdleTime: minutes before an idle connection is closed (1 to 60).MaxLoad: server load above which downloads are refused.MaxDiskUsage: disk percentage (50 to 99) above which uploads are refused.DisplayDotFiles,ProhibitDotFilesWrite: show hidden files; forbid writing them.AntiWarez: refuse downloads of files that anonymous users uploaded.AllowUserFXP: allow server-to-server transfers.KeepAllFiles: users cannot delete or overwrite files.NoRename: users cannot rename files.DontResolve: do not look up names of connecting addresses.
Yes/no fields take yes or no. A field left empty keeps the value the FTP server has now. Click Apply and restart the FTP server.
See Suggested Settings offers values worked out from the server's memory, processors, load and disk; untick what you do not want and click Apply the Ticked Settings.
Services and Monitoring#
In the admin area, open Service Settings → Services and Monitoring (/admin/services). The table lists the server's main services: web server (Apache), database (MariaDB), DNS (BIND), mail (Exim), mailboxes (Dovecot), spam filter (SpamAssassin), FTP (Pure-FTPd), firewall (CSF/LFD) and one PHP-FPM service per installed PHP version. Each row shows the status: Running, Not running or Failed.
- Switched on: the service runs and starts with the server. Unticking it stops the service at once.
- Watched: the panel checks the service every five minutes. If it has failed, you are told by email, and it is started again if Start failed services again automatically is ticked under Alert Contacts.
Tick or untick the boxes and click Save.
To restart, start or stop a single service, open its page under Restart a Service in the menu.
Good to know:
- A service that is not switched on cannot be watched.
- Stopping web, mail or database services takes websites and mail offline until you switch them on again.
- Service Status shows the watched services at a glance.
Database Configuration#
In the admin area, open Service Settings → Database Configuration (/admin/tuning?only=mariadb). The menu item Databases → Database Server Settings opens the same page. These settings apply to the MariaDB server.
Fields include max_connections, innodb_buffer_pool_size, max_allowed_packet (up to 1024M), wait_timeout, interactive_timeout, max_connect_errors, open_files_limit, table_open_cache, thread_cache_size, key_buffer_size, tmp_table_size, max_heap_table_size, the join, sort and read buffer sizes, innodb_log_buffer_size, innodb_flush_log_at_trx_commit, slow_query_log, long_query_time, performance_schema and sql_mode. Leave a field empty to use MariaDB's own default. Sizes are written like 512M.
Click Apply and restart MariaDB. MariaDB tests the change; if it refuses, the previous settings stay.
See Suggested Settings works out values from the server's memory, processors, load and disk. After the database has run for six hours, its own figures are taken into account too. Untick what you do not want and click Apply the Ticked Settings.
Good to know:
- Applying restarts the database, which interrupts websites for a few seconds.
- The InnoDB buffer pool may use up to 70% of the server's memory; the page shows how much memory the server has.
Something missing? Ask in the community or open a ticket.