service apache can not start
in

Service Apache can not start. Reason: Fixed

Fixed Service Apache can not start. Reason: Failed: Apache httpd. After the Laragan installation, when we start services, a problem will occur something like “Apache can not start”.

Service Apache can not start. Reason:

1- failed: Apache httpd-2.4.35-win64-VC15

Service apache can not start

1- Select settings icons.

failed apache laragon

3- Under laragon preferences, select Services & Ports, and then the SSL checkbox enabled.
Close preferences window.

laragon preferences services & ports

4- Open again preferences and then uncheck SSL 443 enables box.

laragon preferences services & ports

5- Select start all and your Apache service started.

laragon dashboard

6- If you get same error message again then follow the below steps.

Service apache can not start

Laragon Apache problem

1- Fixed: It is very easy to fix apache can start in Laragon. Go to laragon installed directory D:\laragon/bin/apache/httpd-2.4.35-win64-VC15\conf. (maybe you can find it in C Drive, I have installed it in D drive).

windows explorer laragon bin

2- Right-click on httpd.conf file and then select open it.

windows explorer laragon httpd.conf

3- Select notepad and then click ok.

Open with

4- Press Ctrl + F, type Listen 80 in finding what, and then hit enter.
Find Listen 80

httpd.conf notepad

5- Change Listen 80 port to 85 and save the notepad.

httpd.conf notepad

6- Select Stop.

Laragon lite 4.0

7- Now select Start All the serve.

Laragon lite start all services

8- Enjoy Laragon

Laragon lite apache started

For more details visit Laragon website

Written by Jamil Parvez

Jamil Pervez works as a Network Administrator, based in Kuwait with a Primary focus on Microsoft technologies. Microsoft Certified MCSE, MCTP, MCITP, CCNP, CCIP, CCVP with 20 years of experience in administering Windows Servers, Exchange, VMWare, Veeam B&R, Veritas BackupExec.

Leave a Reply

How to Increase Snapchat Score? Hacks and Methods

configure network acl in aws

How to Configure Network ACL in AWS