I've searched far and wide on the internet for answers but with no success. I downloaded xampp a couple of months ago and everything has worked fine until recently. I noticed the problem when I was unable to access localhost so I went onto the xammp control panel and saw that apache was turned off. When I click start now every time I get this message -
13:41:55 [Apache] Error: Apache shutdown unexpectedly.
13:41:55 [Apache] This may be due to a blocked port, missing dependencies,
13:41:55 [Apache] improper privileges, a crash, or a shutdown by another method.
13:41:55 [Apache] Press the Logs button to view error logs and check
13:41:55 [Apache] the Windows Event Viewer for more clues
13:41:55 [Apache] If you need more help, copy and post this
13:41:55 [Apache] entire log window on the forums
A common answer to this seems to be to change the port from 80 to 8080 in the httpd.conf file and then changing it from 443 to 4433 in the httpd-ssl.conf file. I have already done this and still not working. When I check the apache error logs it says -
AH00020: Configuration Failed, exiting
It might be worth mentioning that I installed Wordpress on my local server a few days ago and maybe that might have something to do with it? I have tried everything from re-starting my computer to running a full virus scan and nothing seems to work.
I am using Windows 10, Apache version 2.4 and PHP 7.
I've now also tried typing in the command "httpd -t" in Shell and it returns "syntax OK". Also here is a sample from the apache error log -
PHP Warning: 'vcruntime140.dll' 14.0 is not compatible with this PHP build linked with 14.16 in Unknown on line 0
[Tue Jun 09 04:15:03.462661 2020] [:emerg] [pid 4160:tid 548] AH00020: Configuration Failed, exiting
[Tue Jun 09 12:54:30.209908 2020] [core:warn] [pid 4000:tid 684] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
PHP Warning: 'vcruntime140.dll' 14.0 is not compatible with this PHP build linked with 14.16 in Unknown on line 0
[Tue Jun 09 12:54:30.239019 2020] [:emerg] [pid 4000:tid 684] AH00020: Configuration Failed, exiting
Thanks for taking the time to read this and if anyone has any ideas it would be much appreciated.
Ok I've managed to solve the proplem.
For anyone who is having the same problem (apache won't start even if port 80 is available) this info could be useful.
When I looked through the apache error logs there were a number of errors but the particular error causing the problem was -
PHP Warning: 'vcruntime140.dll' 14.0 is not compatible with this PHP build linked with 14.16 in Unknown on line 0
If anyone else gets this error it can be solved by installing the "Visual Studio 2015, 2017 and 2019" runtime (x64: vc_redist.x64.exe). Here's the link to where you can download it.
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
After the download is finished, go into xampp folder and right click on xampp-control.exe, click "run as administrator" then you should be able to start apache with no problems.
Hope this will help anyone who winds up in the same situation as I did.
Do you have checked the log files?
Sometimes it helps to reboot your computer. And then start xampp again
I have installed apache in centos 7. PHP version 7.1 and php-fpm. I had restarted system. Afterward, apache is working but once i access any file it show me below error.
503 service Unavailable
Service Unavailable
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
Apache log:
[Tue Nov 13 18:25:25.171750 2018] [proxy:error] [pid 13059]
(111)Connection refused: AH00957: FCGI: attempt to connect to
127.0.0.1:6000 (127.0.0.1) failed
Please help me to fix this issue.
Finally i got solution of the error. I just uninstall PHP-fpm and used standard PHP 7.1 version and restarted HTTPD services. Its working fine.
All sites work fine when SSL is not enabled. Once I enable it, it fails...
I installed MAMP Pro 5.0.3 today hoping that might change things. Tried SSL again, got a failure and this message from the log:
[Tue Aug 07 16:14:53 2018] [notice] Graceful restart requested, doing restart
(48)Address already in use: make_sock: could not bind to address 10.20.1.10:80
no listening sockets available, shutting down
Can anyone help me figure out what is going on here? (Oh, and how to fix it....) Thanks in advance...
I just set up our first machine with Ubuntu 16 LTS and Tomcat 8.5.11 + Apache/2.4.18, mod_jk/1.2.41.
I was quiet familiar with Ubuntu 14 LTS, Tomcat 7.0.70 and Apache/2.4.7 mod_jk/1.2.37.
Deploying my servlet seemed fine, no errors in tomcat or app log, but still not avail.
Using fqdn/app showed an error 503.
Using ip:port/app worked fine..
I saw these entries in mod_jk.log:
[Fri Feb 24 11:17:49.149 2017] [9219:139689407260416] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1068): (worker1) Failed opening socket to (::1:8009) (errno=111)
[Fri Feb 24 11:17:49.149 2017] [9219:139689407260416] [error] ajp_send_request::jk_ajp_common.c (1728): (worker1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
-> ::1:8009
Why is my worker.host=localhost resolved to ::1 (IPv6) instead of 127.0.0.1 (IPv4)?
I also saw the "newer" parameter "prefer_ipv6" and set it to "worker.prefer_ipv6=0" but without luck..
Workaround:
When I set the worker.host=127.0.0.1 everything works fine/as I am used to.
Downside:
I know some collegue of mine has changed the 127.0.0.1 entry to "localhost" in the past for some reason (different ip stack in processing?), so I am not 100% confident leaving it with IPv4-IP.
Some advices on how I could fix that?
It's a bug in the JK connector, where it always prefers IPv6 when resolving the hostname in the "worker.*.host=" setting. The only way to force the latest JK connector to connect via IPv4 is to use an IPv4 address (rather than a DNS name).
The other alternative is to configure tomcat AJP/1.3 listener to listen on IPv6.
Until the folks at Apache fix the bug in the JK connector, these are the only options right now.
Apache server won't start when in MAMP. Here are the error logs:
[Wed Aug 01 21:07:34 2012] [notice] Digest: generating secret for digest authentication ...
[Wed Aug 01 21:07:34 2012] [notice] Digest: done
[Wed Aug 01 21:07:34 2012] [notice] Apache/2.0.63 (Unix) PHP/5.3.2 DAV/2 configured -- resuming normal operations
[Wed Aug 01 21:08:00 2012] [notice] caught SIGTERM, shutting down
[Wed Aug 01 21:08:01 2012] [notice] Digest: generating secret for digest authentication ...
[Wed Aug 01 21:08:01 2012] [notice] Digest: done
[Wed Aug 01 21:08:01 2012] [notice] Apache/2.0.63 (Unix) PHP/5.3.2 DAV/2 configured -- resuming normal operations
[Wed Aug 01 21:08:51 2012] [notice] caught SIGTERM, shutting down
I don't think I did anything our of the ordinary except create a new folder in htdocs. Any suggestions?
My solution:
in /Applications/Mamp/Library/bin, find the file envvars and rename it to _envvars.
now it works.
I encountered this same issue with the same log output above, but did not need to reinstall MAMP to solve the issue in my case. When I encountered this error it was related to one of the hosts I had set up. Click the Hosts tab and see if any of your hosts appear in red:
The host in red required SSL certificates. In the configuration I did not have valid references to the required certificates after I had altered the file structure of my application. After fixing this issue and applying changes the host was no longer highlighted in red, and I was able to start Apache through MAMP.
Additionally, you can ensure that the problem doesn't have to do with your Apache client itself by running this command in terminal:
sudo /Applications/MAMP/Library/bin/apachectl restart
OR
sudo /Applications/MAMP\ PRO/Library/bin/apachectl restart
If you are able to start Apache in terminal, you have ruled out that you have an error with MAMP's Apache client itself.
Change the name of the file envvars to _envvars in /Applications/MAMP/Library/bin , thats it .
Instead of reinstalling mamp I did the following:
1. Moved back to default mamp ports
2. Started mamp
3. Stopped mamp
4. Went back to ports 80 443 3306
and it started working.
Just reinstalled MAMP and changed the ports. Not sure what the problem was, but it's fixed now.
If your existing MAMP PRO suddenly won't start Apache anymore, then it might be an error in vhosts settings which is not visible.
There is often no indication in apache_error.log - it just comes up with the message.
Apache wasn't able to start. Please check log for more information.
In my case it was a wrong path in Customized virtual host settings such as
Include /path/to/project/rewrite.conf
Vhost config is saved in ~/Library/Application Support/appsolute/MAMP PRO/httpd.conf so you can check the settings there.
Solution: MAMP 4 - Dec 2017, macOS High Sierra
Had this issue with MAMP Pro 3.4.1 so i paid for a new license so i could upgrade to Version 4.2.1 and the problem still occurred. I tried the above solution and unfortunately had no luck.
I did however get Apache running again by selection all options for the directory directive as shown in the image below:
This issue occurred completely randomly, one day everything working fine then the next... Apache says no. I believe the issue is that like web browsers use a Cache and separately also hold open processes, i think sometimes when MAMP or MAMP Pro is not closed properly then it can screw up Apache because it is not stopped correctly.
I hope this answer helps any persons experiencing this issue!
In case above answers didn't fix it, you can check that Document Root isn't set on some non-existing directory.
Go to MAMP Settings > Web-Server > Document Root
I found a Solution:
JUST:
in /Applications/Mamp/Library/bin, find the file envvars and rename it to _envvars.
this issue comes to me today …
after trying several solutions, i found this dialog message may appear if MAMP no longer finds a certificate used by a securized localhost.
So be careful to keep them in a place you won't move or delete.
hope it helps