Panel.ini Configuration File
Certain aspects of the behavior of both Plesk and various Plesk extensions cannot be managed via the GUI, XML API, or the command line. Instead, they are governed by entries in the
panel.ini configuration file. For example, by editing this file, you can:
- Forbid logging in to Plesk using 'root' or 'Administrator' credentials.
- Hide an IP address registered in Plesk, so that it does not appear in the interface and cannot be assigned to subscriptions or resellers.
- Specify a custom URL for the Extensions Catalog, and so on.
panel.ini file can be found here:
- (Plesk for Linux)
- (Plesk for Windows)
If the file is missing on your server, create an empty file at the specified location and name it
panel.ini. You can also rename the
panel.ini.sample file found in the same directory to
panel.ini. This way, the file will contain a number of pre-configured settings you can use for reference.
Configuring Settings in panel.ini
To configure settings via the
panel.ini file, you need to edit it in either of the two ways:
- Edit the
panel.inifile using a text editor.
Install the Panel.ini Editor extension and use it to edit the
panel.inifile in the Plesk GUI.
Regardless of the option you choose, to configure one or more settings via the panel.ini file, you need to add entries to it according to the following pattern:
[Section name] Setting name = Value
Note: If a setting accepts a boolean ('yes' or 'no') value, you can use either 'true', 'on', or 'yes' to enable it, and 'false', 'off', 'no', or 'none' to disable it.
Changes take effect immediately after saving the file. There is no need to restart any services.
For example, to disable IP Address Banning (Fail2Ban), add the following lines to the panel.ini file:
[fail2ban] enabled = false
As a result, IP Address Banning (Fail2Ban) disappears from the Security group on the Tools & Settings screen, and you can no longer manage it via CLI commands.
Every setting that can be configured via the
panel.ini file belongs to a pre-defined section. To customize a setting, you must place it in the
panel.ini file within the section to which it belongs. Do not include any individual section more than once. If you want to customize multiple settings belonging to a single section, include it once and place all settings you want to customize within it.
For example, to customize the URL for the application catalog and to enable application catalog customization, add the following lines to the
[aps] catalogUrl = "http://example.com" catalogsCustomization = on
To configure settings via the Panel.ini Editor extension, go to Extensions > My Extensions > Panel.ini Editor > Open.
Here, on the "Viewer" tab, you can see the complete list of all settings that can be managed via the
panel.ini file, broken down by section. The "Setting" column displays the machine-readable parameter name, and the "Value" column displays its currently assigned value.
Parameters that have been added to the
panel.ini file are shown in bold. For parameters whose value has been customized, the default value is displayed in parentheses next to the currently assigned one. For example, on the screenshot below, the parameter
catalogUrl has been assigned the value
http://example.com instead of the default one (
To search for a specific parameter, click the button to open the search menu.
To edit the
panel.ini file, go to the "Editor" tab and add entries to it, as described above.
Restoring the Default Settings
To restore a setting customized via the
panel.ini file to its default value, open the file for editing and either remove the corresponding line or comment it out by adding the ';' character at the beginning of the line, like this:
[fail2ban] ; enabled = false
The setting reverts to the default value immediately after saving the file.
To restore all settings customized via the
panel.ini file to their default values, do one of the following:
- Log in to the server via SSH or RDP and remove or rename the
- Open the Panel.ini Editor extension and click Reset to defaults.
Here are some customization user scenarios that can be implemented via the panel.ini file. Note that the list is not exhaustive. The behavior of certain Plesk extensions can be customized via the panel.ini file - refer to the extensions' documentation for details.
- Disable logging in to Plesk using the root or administrator credentials
- Specify which MySQL privileges must be available to the different database user roles, or deny certain MySQL privileges to all database users
- Customize Let's Encrypt settings, such as the number of days before expiration when the certificate is scheduled for auto-renewal, or the size of the RSA private key
- Resell Plesk extensions from your own online store
- (Plesk for Linux) Disable the system updates tool, or allow enabling the installation of potentially unsafe updates
- Disable extensions' promos
- Protecting against clickjacking
- Protecting against open redirect
- Restricting remote access via XML API
- Hiding icons of social networks of Social Login