[Tutorial] How to add another Apache version

leokhoa

With Laragon, adding another Apache version is very easy.

Download Apache (64-bit):
https://www.apachelounge.com/download/VS16/binaries/httpd-2.4.48-win64-VS16.zip

Extract the downloaded to: {LARAGON_ROOT}\bin\apache\httpd-2.4.48-win64-VS16

C:\laragon
-- bin
   -- apache
       -- httpd-2.4.48-win64-VS16
       -- .............

Select the new version at: Laragon Menu > Apache > Version > httpd-2.4.48-win64-VS16

Very easy huh. That's all forks!

Ref: https://www.apachelounge.com/download/

leokhoa

Some pics:

Folder structure:
Menu:

pemakanwortel

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

leokhoa

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

Katarina Trajkovic

@leokhoa is not working for me.

leokhoa

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

Katarina Trajkovic

@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?

leokhoa

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

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

Katarina Trajkovic

@leokhoa thank you, working perfectly.

leokhoa

My pleasure. I'm glad to hear that

Jelenik

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

matija

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?

trananhmanh89

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

Dustin

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?

Dustin

Uninstall and reinstall laragon fixed it for me

JackRyan404

Thank you @leokhoa this is really helpful, I was trying for quite some time to add another Apache Version. Now it's done. Now i can make use of my free amazon prime account by watching movies on it.

matija

Anyone managed to get the latest Apache (httpd-2.4.41-win64-VS16 or httpd-2.4.41-win64-VC15) working on Chrome with SSL enabled?

I'm still getting ERR_SSL_KEY_USAGE_INCOMPATIBLE and can't find any workaround. Tried reinstalling with no success.

Upgrade procedure described here is obviously broken.

antonymarc

Thanks all for your responses. i was having similar questions and your answers were helpful to me. You may refer must see website to get more information about this.

forhadkhan

@matija
Check this one:
https://forum.laragon.org/topic/2298/apache-update-problem-and-solution

forhadkhan

@Jelenik
Same here.
Check this one:
https://forum.laragon.org/topic/2298/apache-update-problem-and-solution