Vesta Control Panel - Forum

Hi all.

Please, could someone involved in VestaCP development say something about this: VestaCP ouch no HTTP/2 and outdated Apache

The ALPN support, it's ok, no problem with that (CentOS problem), but why is VestaCP using an outdated version of Apache?

Thanks!!

Which version of CentOS are you using? And is it a modified version provided by your server provide because I think VestaCP uses the default Apache of the OS (CentOS)

vikhyat wrote:Which version of CentOS are you using? And is it a modified version provided by your server provide because I think VestaCP uses the default Apache of the OS (CentOS)

That is correct, the installer script works with the packages your OS has, you might probably want to update your repositories before running the install script.

You can always update Apache afterwards from a different Repo... even after install.

It depends on your OS of choice. I am using Debian 8.6 and can upgrade to Apache 2.4.25 and openssl 1.0.1t without problems by testing repo, you can upgrade to openssl 1.0.2j or 1.1.0+ if you like. Have you checked the following topic?
viewtopic.php?f=20&t=12522

Trentor wrote:but why is VestaCP using an outdated version of Apache?

Why OS repo by default have so old and stable soft? Why!! ;-)

The uninformed and novice users just pop over to forums and start bashing "Why Vesta is using OLD versions of Apache, Nginx, PHP or MySQL... while completely failing to understand it is not VestaCP which "installs software", it merely issues commands "apt-get" or "yum install" and the version of software is "pulled" from the repo whatever is registered and marked in the operating system's maintenance Repository.

If the software in that OS Repo is outdated, its not VestaCP's fault. This can be overcome easily by including/forcing newer repos and pulling/upgrading newer software pkgs from them.

I hope it makes it a bit clear.

One more thing...

Updated to the top version != Better

P.D. I got a tons of headaches after upgrade Exim ... bad idea :(

Re-read https://community.centminmod.com/thread ... che.10114/ and then it's quite easy to check if your Apache version date using command
check the server built date

check whether VestaCP uses CentOS or own VestaCP yum repo for Apache
check Apache rpm's change log history
compare it to

• http://www.apache.org/dist/httpd/CHANGES_2.4.25
• https://rhn.redhat.com/errata/RHEA-2016 ... 20(v.%207)