Stuck with the Error reading data from fastcgi server: Plesk? We can help you.

Generally, we come across this error due to corrupted WordPress plugins.

As part of our Server Management Services, we assist our customers with several Plesk queries.

Today, let us discuss how to resolve this error.

Error reading data from fastcgi server: Plesk

Recently, one of our customers came across this error on at least 3 of the domains on his server. The error message is like this:

Connection reset by peer: mod_fcgid: error reading data from FastCGI server

The major symptom of this error includes:

• WordPress is installed on the Plesk server. However, login to the WordPress admin page is slow.
• Errors in /var/www/vhosts/system/example.com/logs/error_log:

[warn] [client 203.0.113.2] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://example.com/wp-admin/
[error] [client 203.0.113.2] Premature end of script headers: edit-comments.php, referer: https://example.com/wp-admin

• Stracing Apache processes shows the following:

# for fn in `ps fax | grep -i /usr/sbin/httpd | grep -v grep | awk '{ print $1 } '` ; do strace -fF -tT -s102400 -o /tmp/strace.log -p $fn & done

# grep plugins /tmp/strace.log | grep such
32335 02:12:05 lstat("/var/www/vhosts/example.com/httpdocs/test_rp/wp-content/languages/plugins/woocommerce-en_US.mo", 0x7ffe87108a60) = -1 ENOENT (No such file or directory) <0.000015>

Corrupted WordPress plugins can be the cause of this error. In the example above, the WooCommerce plugin is the cause.

How to solve this?

Moving ahead, let us see how we can fix this error in different scenarios:

• Initially, we log in to Plesk
• Then we deactivate one by one all plugins for the website at Domains > example.com > WordPress > Plugins until we fix it.
• Eventually, we can Re-install or delete the plugin we have identified.

On the other hand, if we find that the permissions on the file /var/www/cgi-bin/cgi_wrapper are incorrect, we can fix it via command-line.

To do so, we connect to the server via SSH

Then we correct the permissions:

# chown root:root /var/www
# chmod 0755 /var/www
# chown -R root:root /var/www/cgi-bin
# chmod 0755 /var/www/cgi-bin
# chmod -R 0755 /var/www/cgi-bin/cgi_wrapper

[Need help with the fix? We are available 24*7]

Conclusion

To conclude, in most cases, this error occurs when there are Corrupted WordPress plugins. Today, we saw how our Support Techs fix this for our customers.