Plesk for Linux
kb: technical
ABT: Group A
Applicable to:
- Plesk for Linux
Symptoms
The following error messages appear in Plesk at Domains > example.com > Logs or in domain's error log file /var/www/vhosts/system/example.com/logs/error_log:
CONFIG_TEXT: AH01068: Got bogus version 111, referer: (22)Invalid argument: AH01075: Error dispatching request to :, referer:
Cause
This is Apache bug 49671, which has been fixed in Apache version 2.4.16.
Resolution
Note: Apache 2.4.16 is not available in default repositories of CentOS/RHEL 7.x.
These error messages can be safely ignored - there are no consequences for the website.
To get rid of these messages, you may switch the website to nginx only.
Comments
15 comments
When is this planned to be fixed? The messages are flooding my logs which is quite annoying. Thank you.
@Martin, yes, this bug will be fixed in future product updates
@Vitaly: I have asked for a timeline: When will it be fixed? Just future product updates is too vague. Hopefully someone from Plesk support will answer this question.
A hint: I have noticed that the error flooding stops when disabling watchdog monitoring for the Apache service.
Is this the same error as I get it in my PHP logs:
"AH01068: Got bogus version 27, referer: ...." ?
My logfile fills with about 500k per day with these messages. If it's because of a bug on Plesk's side, it would be great if it could be resolved, otherwise I would really like to know what is causing it so I can fix it on my side.
thanks!
Hello rookey,
Could you please let us know if the issue is still actual for you? In addition, Plesk supports only official repositories in regards to Apache, so, you can use Ubuntu 16.04 with Apache 2.4.18.
I am still getting this in few Joomla websites:
[Mon Aug 28 22:05:14.912477 2017] [proxy_fcgi:error] [pid 28520:tid 139673577895680] [client xx.xx.xx.xx:37974] AH01068: Got bogus version 92
Server version: Apache/2.4.6 (CentOS)
Regards
@Asad Qureshi,
The bug has been fixed in Apache 2.4.16 only. You may migrate to Ubuntu 16, where Apache is 2.4.18.
There are 503 errors in server logs with this issue.
And this error is showing only for Google bot. Is it ok for SEO?
[Wed Mar 10 12:44:10.271459 2021] [proxy_fcgi:error] [pid 9334:tid 140517211817728] [client 66.249.64.127:39972] AH01070: Error parsing script headers
[Wed Mar 10 12:44:10.271544 2021] [proxy_fcgi:error] [pid 9334:tid 140517211817728] [client 66.249.64.127:39972] AH01068: Got bogus version 40
[Wed Mar 10 12:44:10.271550 2021] [proxy_fcgi:error] [pid 9334:tid 140517211817728] (22)Invalid argument: [client 66.249.64.127:39972] AH01075: Error dispatching request to :
The issue is still there. Is there any solution for this?? The server load is really high due to this error.
After updating to "Plesk 18.0.34 Update2", I saw those error logs in the web logs for the first time.
Because it is not likely to be a problem only with apache2.4.6.
For exapmle:
[proxy_fcgi:error] [pid 8295:tid 140088344311552] [client ***.***.***.***:45130] AH01068: Got bogus version 51, referer:
[proxy_fcgi:error] [pid 8295:tid 140088344311552] (22)Invalid argument: [client ***.***.***.***:45130] AH01075: Error dispatching request to :, referer:
The same problem here, only when I run PHP with FPM
Tons of these in the error_log: AH01068: Got bogus version 45
PHP 7.3.28
FPM served by Nginx
CentOS Linux 7.9.2009 (Core)
Plesk 18.0.36
Switching PHP to FPM application served by nginx doesn't fix it.
I have the exact same issue, except the website is already on PHP-FPM served by nginx.
Also, a few websites, from time to time, randomly drop their commercial grade SSL certs, and if there is no LetsEncrypt SSL cert issued it will fail as if it never had a certificate to begin with...
Can we please have a fix?
Hi Andrea Pietropaolo
Try to switch your website to nginx only.
Please sign in to leave a comment.