Applicable to:
- Plesk for Linux
Symptoms
- The following errors are visible within the Apache Error Log for a website:
CONFIG_TEXT: [Wed Jul 19 11:25:22.455351 2023] [fcgid:warn] [pid 29789:tid 139629537761024] [client 203.0.113.2:0] mod_fcgid: stderr: Connection refused
[Wed Jul 19 11:25:22.455389 2023] [fcgid:warn] [pid 29789:tid 139629537761024] [client 203.0.113.2:0] mod_fcgid: stderr: Connection refused
[Wed Jul 19 11:25:22.455392 2023] [fcgid:warn] [pid 29789:tid 139629537761024] [client 203.0.113.2:0] mod_fcgid: stderr: Connection refused
[Wed Jul 19 11:25:22.455399 2023] [fcgid:warn] [pid 29789:tid 139629537761024] [client 203.0.113.2:0] mod_fcgid: stderr: Connection refused
[Wed Jul 19 11:25:22.455403 2023] [fcgid:warn] [pid 29789:tid 139629537761024] [client 203.0.113.2:0] mod_fcgid: stderr: Connection refused - The following entries are visible within the Access Log for the website:
CONFIG_TEXT: 203.0.113.2 - - [19/Jul/2023:11:25:24 +0200] "POST /blog/wp-cron.php HTTP/1.0" 200 871 "-" "WordPress/6.2.2; https://example.com/blog"
203.0.113.2 - - [19/Jul/2023:11:25:24 +0200] "GET /blog/ HTTP/1.0" 200 17171 "-" "WordPress/6.2.2; https://example.com/blog"
203.0.113.2 - - [19/Jul/2023:11:25:24 +0200] "GET /blog/ HTTP/1.0" 200 17171 "-" "WordPress/6.2.2; https://example.com/blog"
203.0.113.2 - - [19/Jul/2023:11:25:24 +0200] "GET /blog/ HTTP/1.0" 200 17171 "-" "WordPress/6.2.2; https://example.com/blog"
203.0.113.2 - - [19/Jul/2023:11:25:24 +0200] "GET /blog/ HTTP/1.0" 200 17171 "-" "WordPress/6.2.2; https://example.com/blog"
203.0.113.2 - - [19/Jul/2023:11:25:24 +0200] "GET /blog/ HTTP/1.0" 200 17171 "-" "WordPress/6.2.2; https://example.com/blog"
203.0.113.2 - - [19/Jul/2023:11:25:19 +0200] "POST /blog/wp-cron.php?doing_wp_cron=1689758719.9299299716949462890625 HTTP/1.0" 200 871 "-" "WordPress/6.2.2; https://example.com/blog" - A portion of the website (for example, the Blog section) is using a separately installed WordPress script
- The WordPress script has a heavily customized
.htaccessfile that contains entries from security and performance plugins such as Wordfence, W3 Total Cache or All In One WP Security - The connection from the main website script to the WordPress script is being refused due to the configurations of the security and performance plugins in WordPress.
Cause
The connection from the main website script to the WordPress script is being refused due to the configurations of the security and performance plugins in WordPress, which can be seen within the .htaccess file of the WordPress script.
Resolution
Review and adjust the settings of the plugins on the side of the WordPress script in order to allow the connection from the main website to the WordPress portion of it.
Alternatively, you may disable the necessary plugins on the side of WordPress plugins entirely.
Comments
Seeing repeated “mod_fcgid: stderr: Connection refused” messages in the Apache error log on a Plesk server can be a useful clue that Apache is having trouble communicating with the backend process handling the website’s requests. This type of error may be related to PHP-FCGI processes, service availability, resource limits, or a configuration issue. A good first step is to review the Apache and PHP-FCGI logs around the same timestamps to identify whether a specific service is stopping or refusing connections. It is also worth checking server resources such as CPU, RAM, and process limits, especially if the problem happens during periods of higher traffic. Restarting the affected service may temporarily restore connectivity, but identifying the underlying cause is important to prevent the error from returning. Overall, checking the logs, service status, resource usage, and Plesk configuration systematically can help narrow down the problem and lead to a more reliable solution.
Please sign in to leave a comment.