Hi,
there is an known bug in Apache2 / mod_proxy_fcgi:
[Wed Jan 16 08:37:23.303558 2019] [proxy_fcgi:error] [pid 23080] [client 10.24.10.100:35564] AH01068: Got bogus version 9, referer:
[Wed Jan 16 08:37:30.354051 2019] [proxy_fcgi:error] [pid 23125] [client 10.24.10.100:35566] AH01068: Got bogus version 112, referer:
[Wed Jan 16 08:37:43.851958 2019] [proxy_fcgi:error] [pid 23337] [client 10.24.10.100:35672] AH01068: Got bogus version 60, referer:
[Wed Jan 16 08:37:50.804052 2019] [proxy_fcgi:error] [pid 23345] [client 10.24.10.100:35674] AH01068: Got bogus version 60, referer:
[Wed Jan 16 08:37:57.884262 2019] [proxy_fcgi:error] [pid 23417] [client 10.24.10.100:35678] AH01068: Got bogus version 108, referer:
[Wed Jan 16 08:38:55.011231 2019] [proxy_fcgi:error] [pid 23596] [client 10.24.10.100:35682] AH01068: Got bogus version 97, referer:
https://bugzilla.redhat.com/show_bug.cgi?id=1416860
https://talk.plesk.com/threads/ah01068-got-bogus-version-32.338554/page-2
https://bz.apache.org/bugzilla/show_bug.cgi?id=56110
when will apache2 / mod_proxy_fcgi be updated? can we use our own httpd2, is there some howto?
Best Regards, Kristijan
Howdy,
Virtualmin doesn't actually provide Apache. In the case of Ubuntu/Debian, Apache comes directly from their repo.
In the case of RHEL/CentOS, Virtualmin takes the RHEL/CentOS Apache package, makes a minor tweak to the suexec setting, then adds that to the Virtualmin repo.
In either case, we unfortunately can't do much about that issue you're seeing on our end here, you'd need to work with your distribution vendor to ensure that they're shipping the bugfix you need with their Apache version.
Once RHEL/CentOS is shipping a particular Apache version, that'll get included in our own repo here.
-Eric