• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue proxy_fcgi:error AH01068: Got bogus version

Azurel

Silver Pleskian
I get nearly every minute this errors in log

[proxy_fcgi:error] [pid 29033] [client xxxx:46748] AH01068: Got bogus version 97
[proxy_fcgi:error] [pid 29033] (22)Invalid argument: [client xxxx:46748] AH01075: Error dispatching request to : xxxx

CentOS Linux 7.3.1611 (Core)‬
Product Plesk Onyx Version 17.0.17 Update #18
Server version: Apache/2.4.6 (CentOS) built: Nov 14 2016 18:04:44

What can I do to fix this?

I found this article
https://support.plesk.com/hc/en-us/...ot-bogus-version-or-Error-dispatching-request
 
That not help in Additional nginx directives :(

proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
 
Had tons of these exact errors appear in my log and finally got rid of them. It's an Apache error and drove us nuts.

Upgraded Plesk to 17.8 (error still exists with 17.5) and upgrade CentOS to 7.5 -- no more errors.
 
Back
Top