EasyApache 3 Deprecation Schedules


Notice 9/13/16: This deprecation schedule is no longer valid. Please see the updated schedule in the new post: Updated EasyApache 3 Deprecation Schedule. The below post is retained solely for historical accuracy. 

EasyApache 3 has served us well for the past 10 years, but it’s almost time for us to say goodbye. While EasyApache3 did its job, and did it for a long time, there were many improvements that we wanted to make. The biggest external complaint was that EasyApache 3 took between 20 – 30 minutes just to add a PHP or Apache module. That’s CRAZY! Internally, we struggled with maintenance as there is a lot of code in EasyApache3 (around half a million lines).

For the past two years, we’ve been working on our new web stack, EasyApache 4. EasyApache 4 offers the benefit of using RPMs to speed up both customization and the time spent building, as well as other asked-for features like the ability to use multiple versions of PHP. We believe that EasyApache 4 provides a wealth of great features and improved functionality, and we strongly encourage you to check it out if you haven’t already. We’re enormously excited about the work that’s gone into it, and think you will be too. 

Here’s the tentative schedule:

  • v58 – EasyApache 3 and EasyApache 4.
    • With the release of cPanel & WHM version 58, EasyApache 4 will be the default web stack on fresh installations. EasyApache 4 offers full parity with EasyApache 3, with improved install and configuration times. You’ll still be able to use EasyApache 3 if you prefer, with a bit of extra configuration first.
  • v60 – EasyApache 3 deprecated.
    • The last version of cPanel & WHM to support EasyApache 3 will be version 60, currently planned for September 2016. Once version 60 goes End of Life in September 2017, EasyApache 3 will receive no further updates, and will be fully deprecated.
  • v62 – EasyApache 3 fully removed.
    • If you are running EasyApache 3, you will be blocked from upgrading to v62 of cPanel & WHM.

EasyApache 3 has had a good run, but EasyApache 4 is the future. Last week’s post from our Community Manger gives you a good place to start, if you’re brand new to EasyApache 4. If you have any questions, find me on Twitter, or on IRC (Perk on freenode)

Photo Credit: https://www.pexels.com/photo/holiday-animal-cute-travel-34297/ – CC0 1.0 License


The web hosting industry's most reliable management solution since 1997. With our first-class support and rich feature set, it's easy to see why our customers and partners make cPanel & WHM their hosting platform of choice. For more information, visit cPanel.net.

11 responses to “EasyApache 3 Deprecation Schedules”

  1. Daniel Bustamante says:

    Sorry @disqus_Q500EwxEqK:disqus but i totally disagree with you. Are you sysadmin? because seems like you love the design before “enabling quick modules” that they are improving. Only your clients can say that.
    I can’t imagine you on a CustomBuild interface of DA, so in my honest opinion you MUST or LEARN MORE to become a better root administrator and a user expert of CPANEL/WHM.

  2. cPanelbenny says:

    Totally understand that move, and I’m glad the LTS tier allows you that extra time. As soon as there’s any change in our plan, it’ll definitely be mentioned here on the blog!

  3. chrismfz says:

    Already switched a few servers to “Stable” Tier. Will switch them to “LTS” when they gonna be updated to 62 to stick with 60. It will save me time until September 2017. Got many customers with Tomcat and I don’t know what to do. But got 13 months to think something.

  4. cPanelbenny says:

    Send it all! I love hearing it, and I’ll definitely make sure your feedback gets to the right ears. One note: the easier to digest, the more likely your feedback will get implemented. Splitting bigger things into small, actionable items is good. Also bullet points. Devs love bullet points. 😀

  5. Lewis says:

    How detailed would you like my feedback? I’m happy to go all out if it has the chances of actually making things better. If so, I’ll whack it in an email to you, as it’ll be quite a lot!

  6. cPanelbenny says:

    Hey there! I’m so sorry I didn’t get back to you yesterday! Your feedback is absolutely heard, and we’re working to make it easier. The EasyApache 3 UI and functionality had its own drawbacks as well.

    Theoretically, if you had a chance to design it from the ground-up, how would you build the EasyApache 4 interface?

  7. Lewis says:

    I’m not sure if you even read what I wrote, but “one line of code” sounds like you are referring to upgrading from EA3 to EA4. That was fine, however that whole post was about the ***functionality*** of EasyApache 4. The whole point isn’t “one line of code” but rather a graphical user interface for upgrading and downgrading Apache and PHP as well as configuring modules/extensions for both of them. My complaint is that this process is much more difficult in EA4 than in EA3 even though the name suggests simplicity; please re-read.

  8. poto says:

    come on man, its just one line of code on ssh to upgrade, whats so difficult about that?

  9. Lewis says:

    In my honest opinion it looks like cPanel magically assumed all of their root administrator users are expert users and the simplicity has been taken away. Although it was annoying to have to rebuild everything in EasyApache 3 when I only wanted to add a single PHP Module, I overall found the process of it to be easier and I honestly prefer the wait. Nothing is explained very well and even the How to use EasyApache 4 link just goes to an install/uninstall instructions page which doesn’t explain any use. I have absolutely no idea what these different MPM modules do, the list of Apache modules is extensive and spans over 8 pages without explanation (which one do I pick?!), and why on earth can I have multiple PHP version installations and what benefit does that bring; also how does a website know which one to use or is it automatic? The names are not that friendly either – and although it does say “Package that installs X”, “ea-php56” still isn’t a friendly term. Oh god… then PHP extensions… 15 pages?!?! 15! Again, unfriendly names which was NEVER a problem in EasyApache. If I wanted Intl extension, I could easily find it – all on one page… the only benefit at all that I can see of this screen is how I no longer need to Google what each extension does as it gives a brief description. With EasyApache 3, it really was easy. I go down a list, select what I want, all titles were clean, no mess, no 15 pages – it was VERY easy, however now I feel like EasyApache 4 is more DifficultApache 1 and that cPanel has completely forgotten about the people who are not native/experienced root administrators and frankly it is very likely I will not update to v62 at all – ever – even if it means missing security fixes and new features, I would much rather keep EasyApache 4. It would have been fine if cPanel kept both however removing it entirely is much a shame and I am sure I’m not the only one that feels this way. Sorry if that seemed a hit harsh but at least it’s honest; I would love to get your own thoughts on this.

  10. cPanelbenny says:

    Hi Lewis! I’m sorry to hear you dislike EA4, but we want to make sure EA4 is ready for everyone. Is there anything specific you dislike about EA4? I’m genuinely interested in your feedback!

  11. Lewis says:

    No! It’ll be sad to see it go, I can’t stand EasyApache 4.

Leave a Reply