• 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.

Is it possible to update Apache within Plesk?

S

ScottyMojo

Guest
Is it possible to update Apache within Plesk or do I need to run a command in SSH? If I need to run a command, what would the command be for Red Hat Enterprise Linux 5?
 
You can always grab the latest version of apache from Red hat using "yum update". Plesk itself does not use apache any more, it was replaced with lighttpd in version 9.
 
So to update Apache, I just enter "yum update" in SSH? Also, is lighttpd better than Apache? I like the sounds of better speed. How would I switch over from Apache to lighttpd and is there a potential of incompatibilities with various php scripts/programs?
 
Yes, yum update is all you need to do. I'd recommend you check this regularly, updates come out for the system all the time.

In regard to lighttpd, it is not supported in Plesk although I suspect you wouldn't have much trouble getting it to work in a plesk environment. lighttpd doesn't support things like mod_security, so I'm not particularly interested in it myself.
 
I'm trying to update too...

The latest version of Apache is 2.2.14

If I enter an SSH session to my server and type the following:

httpd /v

I get:

Server version: Apache/2.2.3
Server built: Nov 12 2009

This was as a result of me previously running:

yum update httpd


Basically, it applied an update (I had to answer Y and there were 4 parts to it) yet the final version number is still 2.2.3

What have I done wrong? Why won't it update to 2.2.14? More importantly, why does yum update think that the latest version is 2.2.3?
 
The latest version of Apache is 2.2.14

If I enter an SSH session to my server and type the following:

httpd /v

I get:

Server version: Apache/2.2.3
Server built: Nov 12 2009

This was as a result of me previously running:

yum update httpd


Basically, it applied an update (I had to answer Y and there were 4 parts to it) yet the final version number is still 2.2.3

What have I done wrong? Why won't it update to 2.2.14? More importantly, why does yum update think that the latest version is 2.2.3?

I think that you should ask it from OS vendor - RedHat - why they do not updated apache in repository to latest version?
 
Ok, any idea how I would go about that? I am using CentOS 5. Can I presume they share Redhat's repositories then?
 
Back
Top