[Tutorial] How to add another Apache version


  • administrators
    | 113323 points

    With Laragon, adding another Apache version is very easy.

    1. Download Apache (64-bit):
      https://www.apachelounge.com/download/VC14/binaries/httpd-2.4.28-win64-VC14.zip

    1. Extract the downloaded to: {LARAGON_ROOT}\bin\apache\httpd-2.4.28-win64-VC14
    C:\laragon
    -- bin
       -- apache
           -- httpd-2.4.28-win64-VC14
           -- .............
    

    1. Select the new version at: Laragon Menu > Apache > Version > httpd-2.4.28-win64-VC14

    Very easy huh. That's all forks!


  • administrators
    | 113323 points

    Some pics:

    1. Folder structure:
      0_1468589199464_apache-folder-structure.png

    2. Menu:
      0_1468589212510_laragon-menu-apache-select.png


  • | 125 points

    @leokhoa After I change from default to 2.4.27 he is not even running, instead tell create http conf


  • administrators
    | 113323 points

    @pemakanwortel : Please make sure that your Apache version must match your PHP (TS) version in term of "Architecture (64-bit)" and "VC Build (VC14)".

    You didn't tell me your full Apache version so I can't tell you what's wrong.

    FYI: When I bundled Apache (httpd-2.4.27-win64-VC14) to Laragon 3.1.3, I saw no issue.


  • | 125 points

    @leokhoa is not working for me.


  • administrators
    | 113323 points

    @Katarina-Trajkovic : Can you show me some images?


  • | 125 points

    @leokhoa ok, I have a question. in this picture gives the files that I do not have in www. this are the old files. When I go to the apache VirtualHost, he gives me the lists of the names of these files. Is there a way to remove the names of these files?0_1504285541559_Capture.PNG


  • administrators
    | 113323 points

    @Katarina-Trajkovic :
    There are 2 ways to do this:

    1. Change your Document Root in Menu > Preferences...
    2. Delete all auto virtual hosts in **Menu > Apache > sites-enabled > Delete all [auto]

  • | 125 points

    @leokhoa thank you, working perfectly.


  • administrators
    | 113323 points

    My pleasure. I'm glad to hear that :)


  • | 439 points

    I had the same error message after downloading, extracting and choosing another Apache version.

    Error: Must create file: C:\laragon\bin\apache\httpd-2.4.34-win64...\httpd.conf

    That was because I strictly followed your instructions about extracting the downloaded apache package. Because I needed to use php-5.6.37-Win32-VC11-x64 laragon instructed me that bundled Apache httpd-2.4.27-win64-VC14 doesnt match chosen PHP ( probably because different VC ) so I wanted to try httpd-2.4.34-win64-VC11 so I have downloaded it and extracted into bin\apache\httpd-2.4.34-win64-VC11 and then that error appeared. After while I noticed that there is Apache24 folder in that zip file, from which those files should be copied into httpd-2.4.34-win64-VC11 folder.

    So without noticing, I had this folder structure:
    bin\apache\httpd-2.4.34-win64-VC11\Apache24\bin... which is wrong
    vs.
    bin\apache\httpd-2.4.34-win64-VC11\bin... correct

    Maybe for a lot of people, this is clear, but a small note about this could help others whose doesn't look what they are extracting and havent looked at your screenshot in the second post how the folder structure for another Apache version should look like :)

    But overall I had to admit that this is the best WAMP software which I tried until now ( I have used XAMPP for years, then paid MAMP PRO for 6 months ), so thanks a lot for this great software. I love how laragon automatically identifies laravel projects and set virtual host accordingly to public folder and how is everything fast, automatic and simple ( after while ) .


  • | 442 points

    Every time I try to change Apache version with SSL activated I get the following message in Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE
    Edge displays page without problems. Firefox also works fine when you dismiss self-signed certificate warning for certain domain.

    I rolled back to previous version of Apache and it works fine in Chrome.

    Is there a simple way to avoid this error when updating Apache version while using SSL?


  • | 163 points

    @matija said in [Tutorial] How to add another Apache version:

    Every time I try to change Apache version with SSL activated I get the following message in Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE
    Edge displays page without problems. Firefox also works fine when you dismiss self-signed certificate warning for certain domain.

    I rolled back to previous version of Apache and it works fine in Chrome.

    Is there a simple way to avoid this error when updating Apache version while using SSL?

    same error with apache httpd-2.4.37-win64-VC15
    when i switch back to php 5.6 and apache httpd-2.4.37-win64-VC11, chrome is working fine.


  • | 792 points

    I switched from PHP 7.3.5 to 7.3.6 and Apache 2.4.37 to 2.4.39 and now none of my sites will load correctly in Chrome. I can get to the home page but when I try to load any other page I get an error: ERR_SSL_KEY_USAGE_INCOMPATIBLE

    Edge works with no problem. Firefox works after I accept the risk on using an invalid security certificate (not trusted because it is self-signed MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT)

    I tried switching back to my original configuration of PHP 7.3.5 and Apache 2.4.37 but still none of my sites will load correctly in Chrome.

    Any ideas for how to fix this?


  • | 792 points

    Uninstall and reinstall laragon fixed it for me


  • | 26 points

    Thank you @leokhoa this is really helpful, I was trying for quite some time to add another Apache Version


Log in to reply
 

Looks like your connection to Laragon was lost, please wait while we try to reconnect.