• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

I need to upgrade apache 2.0.54 to a newer version

M

micmac@

Guest
Hello,

How can I upgrade the version of apache2
that comes with plesk to a newer version ?

Plesk comes with apache 2.0.54, but there
is an important security fix in apache
2.0.59

How can I upgrade the current version
of apache in plesk 8.1 linux to this
newer 2.0.59 version ? (I'm not even
asking to upgrade to the new 2.2 apache...)
 
just look to an update of your linux distribution, plesk use the version of your installed linux ...
 
ok, thanks for the answer.

I had a manual installation of apache 2.2
(I mean building it from the source) on
Debian Sarge before installing Plesk.


I guess that's why plesk didn't find
it, since I din't install it with apt.

Too bad that the 2.2 version of apache2
is not released in debian paquets for
Sarge then.

I have to wait for the upcoming Plesk
8.2 to move to Etch and solve those
problems, as everybody else I guess.
 
If you're using a distribution that is still supported by the vendor (and if you're running Debian Sarge, you are) there is no need to install the latest version to get the security patches. A lot of distributions do backports instead of version upgrades. You might want to read this (Red Hat) document that explains the backporting process: http://www.redhat.com/advice/speaks_backport.html

In short: if you're running the latest apache that apt-get has for you, there is nothing to worry about. If you really need new features that are not available in the latest version that your distro is supplying, *then* it's time for more complex operations.
 
Ok! The security issues are fixed,
even if the version number is slightly
the same.

I'll keep my current apt updated version
then, thanks for explaining the
backporting principle to me :)
 
Back
Top