News:

SMF - Just Installed!

Main Menu

Recent posts

Pages1 2 3 ... 10
#1
Others / NodeJS website randomly unavai...
Last post by senthil - Nov 29, 2025, 06:30 AM
Symptoms

  • Website with NodeJS returns a 500 internal server error occasionally

Cause

One of the randomly picked sockets is missing. The following could be seen in
/var/log/passenger/passenger.log:

Code Select
[ E 2023-01-22 17:06:07.0103 27101/T0 apa/Hooks.cpp:751 ]: Unexpected error in
mod_passenger: Cannot connect to the Passenger core at
unix:/tmp/passenger.20pAQXl/agents.s/core
Backtrace:
in 'Passenger::FileDescriptor Passenger::Apache2Module::Hooks::connectToCore()'
(Hooks.cpp:343)
in 'int Passenger::Apache2Module::Hooks::handleRequest(request_rec*)' (Hooks.cpp:622)
[ D 2023-01-22 17:06:09.2120 35164/Tk age/Cor/Con/TurboCaching.h:246 ]: Clearing
turbocache
[ D 2023-01-22 17:06:09.2120 35164/Tk Ser/Server.h:880 ]: [ServerThr.7] 1 new client(s)
accepted; there are now 1 active client(s)
[ D 2023-01-22 17:06:09.2122 35164/Tk age/Cor/App/Gro/SessionManagement.cpp:330 ]:
Session checked out from process (pid=35483, group=/var/www/vhosts/example.com
(production))
Resolution

Restart both apache2 and the NodeJS application to reload the passenger module and recreate the sockets.

#2
Others / Error in Plesk logs: Unable to...
Last post by senthil - Nov 29, 2025, 06:24 AM
Applicable to:

  • Plesk Obsidian for Linux

Symptoms

  • An error appears in /var/log/plesk/panel.log every day:
    Code Select
    ERR [panel] Unable to get key: Repository is not opened
  • Permissions on /etc/sw/keys/ directory and files in it are set accordingly to the Error in Plesk:
    SWKeyExFatalError: "Cannot open file" or "Permission denied"
    article
  • registry.xml files is present and solution steps from Plesk does not open: SWKeyExFatalError Repository is not opened do not take any effect.

Cause

Plesk bug with ID #PPPM-13853 which will be fixed in future updates.

Resolution

As a workaround, the error can be safely ignored.

#3
Others / Plesk menu 'Tools & Settings >...
Last post by senthil - Nov 29, 2025, 06:20 AM
Applicable to:

  • Plesk for Windows

Symptoms

  • On a Plesk for Windows server, the Plesk menu Tools & Settings > FTP Settings is not accessible:
    500 PleskUtilException
    winfwmng failed: The type initializer for 'psa.ip.device.InternetFirewall' threw an exception. Creating an
    instance of the COM component with CLSID {304CE942-6E39-40D8-943A-B913C40C9CD4} from the
    IClassFactory failed due to the following error: 800706d9 There are no more endpoints available from the
    endpoint mapper. (Exception from HRESULT: 0x800706D9). (Error code 1)
  • The same error can be found on attempt to open the menu Tools & Settings > Firewall.
  • In the Windows MMC snap-in Windows Firewall with Advanced Security, the following error is displayed
    instead of the firewall rules:
    Code Select
    There was an error opening the Windows Firewall with Advanced Security snap-in
    The Windows Firewall with Advanced Security snap-in failed to load. Restart the
    Windows firewall service on the computer that you are managing. Error code: 0x6D9.

Cause

Windows Server OS Firewall is not accessible via COM.

Resolution

Contact Microsoft Support for fixing issues with the Windows Server OS firewall.





#4
Others / Where can I find the full docu...
Last post by senthil - Nov 29, 2025, 06:13 AM
Question

Where can I find the full documentation of the WP Toolkit API?

Answer

To access the WP Toolkit API documentation, simply go to Tools & Settings > Remote API (REST) and click on WP
Toolkit REST API link. There you will find the documentation, usage examples and other info on WP Toolkit API.


#5
Others / How to configure a Linux serve...
Last post by senthil - Nov 29, 2025, 06:11 AM
Applicable to:

  • Plesk for Linux

Question

How to configure a Linux server with Plesk installed to meet PCI Compliance?

Answer

While the topic of achieving full PCI compliance for a server is a very broad one and is subject to change as the years go by,
the PCI Compliance Resolver utility is available from the Plesk installation directory and can shorten the process
of achieving PCI compliance on any server significantly.

It can disable weak SSL/TLS ciphers and protocols for web and e-mail servers operated by Plesk, and apply many other security changes, all of which are mentioned in more detail on the following page of the Plesk Obsidian documentation (along with other manual actions related to the process of achieving PCI compliance):

(Plesk for Linux) Tune Plesk to Meet PCI DSS

If you want to apply all of the mentioned security settings for all services listed on the page above, you should follow these steps:

  • Connect to the server via SSH
  • Execute the following command:
    Code Select
    # plesk sbin pci_compliance_resolver --enable all
Note: The currently known limitations of the PCI Compliance Resolver utility are listed below:

  • The protocols for qmail mail agent cannot be configured; therefore, qmail is not secure enough to satisfy PCI
    DSS. It is recommended to use Postfix instead.
  • Ciphers for qmail cannot be changed via Plesk utilities (though it is possible to change them via the
    configuration file).
  • TLSv1.1 and TLSv1.2 are not supported on CentOS 5, Red Hat Enterprise Linux 5, and CloudLinux 5.
    The DH parameter's size cannot be managed for Apache from OS vendor (CentOS 5, Red Hat Enterprise Linux
    5, CloudLinux 5).
  • SSL/TLS compression is not disabled on Debian 7 for ProFTPd, Dovecot, and Postfix.
#6
Webserver / Plesk websites are inaccessibl...
Last post by Suhitha - Nov 29, 2025, 04:13 AM
Question: Plesk websites are inaccessible with 504 Gateway Timeout with enabled firewall: : Connection timed out


Applicable to:

  • Plesk for Linux


Symptoms

  • If Nginx is enabled, all sites return the following error:

  CONFIG_TEXT: 504 Gateway Timeout error

  CONFIG_TEXT: 502 Bad gateway

  • Fail2ban is not installed or disabled;
  • Apache and nginx services are running;
  • There are the following records in /var/log/httpd/error_log:
Code Select
upstream timed out (110: Connection timed out) while reading response header from upstream
Code Select
AH00072: make_sock: could not bind to address 127.0.0.1:7080

  • There are the following records in /var/www/vhosts/example.com/logs/proxy_error_log:
Code Select
[error] 18625#0: *8 connect() failed (111: Connection refused) while connecting to upstream
Code Select
curl: (28) Failed to connect to 203.0.113.2 port 7081 after 129871 ms: Connection timed out


Cause

Firewall rules block local connection on port 7080 and 7081, or some rules block the server's IP Address, so Nginx is unable to connect to Apache.


Resolution

Check the Plesk firewall or "iptables"  utility and remove rules that block access to 7080 or 7081 ports or block access from the server's IP addresses

                                      Manage rules via Plesk Firewall

1.Install Plesk Firewall if it is not installed How to install Plesk Firewall

2.Go to Plesk > Tools & Settings > Firewall > Modify Plesk Firewall Rules >Add Custom Rule and allow 7080/7081 ports for all internal IP addresses for Incoming/Outgoing.



                              Adding rules directly from the server

1.To do this manually, connect to the server via SSH

Note: if direct SSH access to the server is not possible, contact server administrator for further assistance.

2.Add rules using the commands below:

# iptables -A INPUT -s 10.10.10.10 -p tcp -m tcp --dport 7081 -j ACCEPT
# iptables -A INPUT -s 10.10.10.10 -p tcp -m tcp --dport 7080 -j ACCEPT
# iptables -A OUTPUT -s 10.10.10.10 -p tcp -m tcp --sport 7081 -j ACCEPT
# iptables -A OUTPUT -s 10.10.10.10 -p tcp -m tcp --sport 7080 -j ACCEPT

NOTE: In addition, check any other similar tools and extensions installed on the server like Imunify360, DDoS Deflate Interface, or Bitninja for example if there are similar rules forbidding needed ports or blocking the server's IP addresses
#7
Webserver / After dist-upgrade Apache was ...
Last post by Suhitha - Nov 29, 2025, 01:55 AM
Question: After dist-upgrade Apache was upgraded from 2.2 to 2.4, Apache and cannot start


Applicable to:

  • Plesk for Linux



Symptoms

Note: the article is related to the issue that occurs after Apache upgrade (during dist-upgrade for example).

  • After failed Plesk upgrade on Debian OS with Apache version 2.4 installed, web server is not starting.
  • The following error messages appears:
Code Select
apache2: Syntax error on line 234 of /etc/apache2/apache2.conf: Syntax error on line 5 of /etc/apache2/conf.d/zz010_psa_httpd.conf: Syntax error on line 72 of /etc/apache2/plesk.conf.d/server.conf: No matches for the wildcard '*.conf' in '/etc/apache2/plesk.conf.d/ip_default', failing (use IncludeOptional if required)
Action 'configtest' failed.
The Apache error log may have more information.
Code Select
Invalid command 'Order', perhaps misspelled or defined by a module not included in the server configuration
Code Select
SSLSessionCache: 'shmcb' session cache not supported (known names: dbm,memcache). Maybe you need to load the appropriate socache module (mod_socache_shmcb?).
Code Select
The apache2 instance did not start within 20 seconds. Please read the log files to discover problems.
Code Select
[proxy_balancer:emerg] [pid 25870] AH01177: Failed to lookup provider 'shm' for 'slotmem': is mod_slotmem_shm loaded?
Code Select
Invalid command 'Require', perhaps misspelled or defined by a module not included in the server configuration
Code Select
Invalid command 'User', perhaps misspelled or defined by a module not included in the server configuration1.
Code Select
Invalid command 'DirectoryIndex', perhaps misspelled or defined by a module not included in the server configuration
Code Select
ERROR: Config file dir.conf not properly enabled: /etc/apache2/mods-enabled/dir.conf is a real file, not touching it


Cause

Configuration files were not completely switched to the new Apache 2.4


Resolution

1.Check if custom templates exist in /usr/local/psa/admin/conf/templates folder. If so review all of them and change Include to IncludeOptional in every line what contain wildcard.

2.If there are no custom templates change Include to IncludeOptional in every line what contain wildcard in the following files:

/etc/apache2/conf.d/zz010_psa_httpd.conf
/etc/apache2/plesk.conf.d/server.conf
/etc/apache2/plesk.conf.d/horde.conf

3.Enable and activate the following Apache modules

# a2enmod authz_core authz_host access_compat socache_shmcb slotmem_shm mpm_worker unixd php5 dir
#8
Webserver / Error message on the Home page...
Last post by Suhitha - Nov 29, 2025, 01:44 AM
Question: Error message on the Home page in Plesk: module unique_id_module is already loaded, skipping


Applicable to:

Plesk for Linux


Symptoms

  • One of the following error messages is shown on the Home page in Plesk:

New configuration files for the Apache web server were not created due to the errors in configuration templates: [so:warn] [pid 55597:tid 140252507555968] AH01574: module unique_id_module is already loaded, skipping
httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 13 of /etc/httpd/conf.d/00_mod_security.conf: No matches for the wildcard '00*exclude.conf' in '/etc/httpd/modsecurity.d', failing (use IncludeOptional if required).

New configuration files for the Apache web server were not created due to the errors in configuration templates: [Wed Mar 21 12:25:31 2018] [warn] module security2_module is already loaded, skipping [Wed Mar 21 12:25:31 2018] [warn] module unique_id_module is already loaded, skipping Syntax error on line 35 of /etc/apache2/modsecurity.d/rules/tortix/modsec/50_plesk_basic_asl_rules.conf: ModSecurity: Found another rule with the same id .

  • Apache configuration checker reports one or both of the warnings below ("httpd -t" for CentOS/RHEL-based distributions, "apache2 -t" for Debian/Ubuntu-based distributions):
# httpd -t
[warn] module security2_module is already loaded, skipping
[warn] module unique_id_module is already loaded, skipping

  • In some cases, Apache cannot be started.


Cause

The ModSecurity configuration file 00_mod_security.conf contains duplicated records.


Resolution


                                  For CentOS/RHEL-based distributions


1.Connect to the Plesk server via SSH.

2.Open the file 00_mod_security.conf in a text editor. In this example, we are using the vi editor:

# vi /etc/httpd/conf.d/00_mod_security.conf

3.Replace "Include" in the lines:

Code Select
Include modsecurity.d/00*exclude.conf
Include modsecurity.d/*asl*.conf
Include modsecurity.d/99*exclude.conf
with "IncludeOptional":

Code Select
IncludeOptional modsecurity.d/00*exclude.conf
IncludeOptional modsecurity.d/*asl*.conf
IncludeOptional modsecurity.d/99*exclude.conf
4.Save the changes and close the file.

5.Locate duplicated ModSecurity modules and disable them:

# grep -ir security2_module /etc/httpd/ && grep -ir unique_id_module /etc/httpd/

In case there is a module which is enabled twice in the output above, for example:

Code Select
/etc/httpd/conf.modules.d/00-base.conf:LoadModule unique_id_module modules/mod_unique_id.so
/etc/httpd/conf.modules.d/10-mod_security.conf: LoadModule unique_id_module modules/mod_unique_id.so
disable it by putting a # (hash) character at the beginning of the line in the file 00_mod_security.conf:

Code Select
#LoadModule security2_module ...
#LoadModule unique_id_module ...
6.Restart Apache:

# service httpd restart

7.Repair web-server configuration:

# plesk repair web -y

8.Log in to Plesk.

9.Go to Tools & Settings > Web Application Firewall (ModSecurity) > Settings tab and click OK to refresh ModSecurity settings.


                                For Debian/Ubuntu-based distributions:


1.Connect to the Plesk server via SSH.

2.Open the file 00_mod_security.conf in a text editor. In this example, we are using the vi editor:

# vi /etc/apache2/conf.d/00_mod_security.conf

3.Replace "Include" in the lines:

Code Select
Include modsecurity.d/00*exclude.conf
Include modsecurity.d/*asl*.conf
Include modsecurity.d/99*exclude.conf
with "IncludeOptional":

Code Select
IncludeOptional modsecurity.d/00*exclude.conf
IncludeOptional modsecurity.d/*asl*.conf
IncludeOptional modsecurity.d/99*exclude.conf
4.Locate duplicated ModSecurity modules and disable them:

# grep -ir security2_module /etc/apache2/ && grep -ir unique_id_module /etc/apache2/

In case there is a module which is enabled twice in the output above, for example:

Code Select
/etc/apache2/conf.d/00_mod_security.conf:LoadModule security2_module /usr/lib/apache2/modules//mod_security2.so
/etc/apache2/mods-available/security2.load:LoadModule security2_module /usr/lib/apache2/modules/mod_security2.so
disable it by putting a # (hash) character at the beginning of the line in the file 00_mod_security.conf:

Code Select
#LoadModule security2_module ...
#LoadModule unique_id_module ...
5.Restart Apache:

# service apache2 restart

6.Repair web-server configuration:

# plesk repair web -y

7.Log in to Plesk.

8.Go to Tools & Settings > Web Application Firewall (ModSecurity) > Settings tab and click OK to refresh ModSecurity settings.
#9
Webserver / Apache config file cannot be g...
Last post by Suhitha - Nov 29, 2025, 01:14 AM
Question: Apache config file cannot be generated on a Plesk server: Wrong variable to subsitute


Applicable to:

  • Plesk for Linux
[/b]

Symptoms

  • Apache configuration generation fails with the following or similar error:

New configuration files for the Apache web server were not created due to the errors in configuration templates:
Template processing failed: file = /opt/psa/admin/conf/templates/default/domainVhost.php, error = Template_Exception: [Template_Variable_Domain_PhysicalHosting] Wrong variable to subsitute: maintenanceMode file: /opt/psa/admin/plib/Template/Processor.php line: 27 code: 0 Previous error: Template_Exception: [Template_Variable_Domain_PhysicalHosting] Wrong variable to subsitute: maintenanceMode file: /opt/psa/admin/plib/Template/Processor.php line: 27 code: 0 Previous error: Template_Exception: [Template_Variable_Domain_PhysicalHosting] Wrong variable to subsitute: maintenanceMode file: /opt/psa/admin/plib/Template/Variable/Abstract.php line: 67 code: 0.

  • Custom Apache virtual host templates are used:
# ls -l /usr/local/psa/admin/conf/templates/custom/domain/
-rw-r--r-- 1 root root 987 Jul 22 16:13 domainVhost.php


Cause

Custom Apache virtual host templates contain a syntax error or reference to a nonexistent variable.


Resolution

1.Connect to the server using SSH.

2.Move the custom templates folder to another location:

# mv -f /usr/local/psa/admin/conf/templates/custom /root/custom_templates/

3.Rebuild web server configuration files:

For RHEL-based Linux distributions (CentOS, RedHat, CloudLinux):

# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all

For Debian-based Linux distributions (Ubuntu, Debian):

# /opt/psa/admin/sbin/httpdmng  --reconfigure-all

Note: Check Plesk Advanced Administration Guide to see the full list of allowed variables for custom virtual host templates.
#10
Webserver / Websites on Plesk server are s...
Last post by Suhitha - Nov 29, 2025, 12:59 AM
Question: Websites on Plesk server are slow or show error 500 or PHP mail cannot be sent: ap_pass_brigade failed


Applicable to:

  • Plesk for Linux



Symptoms

  • Websites on Plesk server are slow or not available, sending emails via PHP script fails with:
Code Select
500 Internal server error
  • Domains > exemple.com > Logs or /var/www/vhosts/example.com/logs/error_log show:

Code Select
mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: http://www.example.com/index.php

Cause

The connection is being reset due to the FcgidMaxRequestsPerProcess limit has been reached. The parameter was previously defined in the web configuration:

  • On RedHat/CentOS/CloudLinux:

# grep FcgidMaxRequestsPerProcess /etc/httpd/conf.d/fcgid.conf /var/www/vhosts/system/example.com/conf/vhost.conf /var/www/vhosts/system/example.com/conf/httpd.conf

  • On Ubuntu/Debian:

# grep FcgidMaxRequestsPerProcess /etc/apache2/mods-enabled/fcgid.conf /var/www/vhosts/system/example.com/conf/vhost.conf /var/www/vhosts/system/example.com/conf/httpd.conf


Resolution

                                    Solution for one particular domain

1.Log in to Plesk.

2.Go to Domains > example.com > Apache & nginx Settings > Additional Apache directives.

3.Increase the FcgidMaxRequestsPerProcess parameter value in Additional directives for HTTP and Additional directives for HTTPS fields:

Code Select
<IfModule mod_fcgid.c>
FcgidMaxRequestsPerProcess 500
</IfModule>


                                Solution for all domains on the server

1.Connect to the server via SSH.

2.Open /etc/httpd/conf.d/fcgid.conf (on RedHat/CentOS/CloudLinux) or /etc/apache2/mods-enabled/fcgid.conf (on Ubuntu/Debian) using "vi";

3.Increase the value of FcgidMaxRequestsPerProcess parameter, e.g. to 500:

Code Select
<IfModule mod_fcgid.c>
FcgidMaxRequestsPerProcess 500
</IfModule>
4.Reload Apache configuration:

  • On RedHat/CentOS/CloudLinux:

# systemctl reload httpd

  • On Ubuntu/Debian:

# systemctl reload apache2

5.If it does not help, set FcgidOutputBufferSize 0 in the same configuration file and reload Apache again.
Pages1 2 3 ... 10