Troubleshooting Apache 2.4.9 on OS X Yosemite

Since upgrading to OS X Yosemite DP, I have had problems using Apache on my Mac and have previously dropped back to using MAMP. Since OS X 10.10 DP5, now MAMP doesn't work either. So I figured I had to tackle this problem in a complex way (I'm not very good at setting up raw servers). I have tried, however, without success, and now I know where to look next.

This is what I did:

enter image description here

After looking at this result, I of course checked if the Aoache service was actually running:

enter image description here

OK. Then I thought it was indeed my Apache configuration that was wrong. And rightfully, by calling apachectl

in Terminal, I found that there were parsing errors in the Apache configuration (possibly because Apache was upgraded when upgrading to OS X 10.10, but the config file doesn't match? Anyway, I followed the instructions to get a valid config file with minimal modules installed ( .so

files taken from previous install location).

enter image description here

A copy of mine httpd.conf

can be seen at http://pastebin.com/VU5aZ6vL , but the key variables are listed here:

ServerRoot "/usr"
Listen 127.0.0.1:80
LoadModule authz_core_module libexec/apache2/mod_authz_core.so
User daemon
Group daemon
ServerName localhost:80
<Directory />
    AllowOverride none
    Require all granted
</Directory>
DocumentRoot "/Users/casparjespersen/Sites/"

      

However, the result is the same. Any ideas where to look next?

+3


source to share


3 answers


I had the same problem. Quick fix: http://www.ampps.com/ still works for me for a basic Apache / MySQL installation.



But AMPPS is missing many great features that I love using MAMP.

+1


source


This will help you just follow the instructions:



http://coolestguidesontheplanet.com/get-apache-mysql-php-phpmyadmin-working-osx-10-10-yosemite/

+1


source


After looking into configuring Apache on Yosemite, the problem was explained - the solution is to implicitly add localhost at the top before your Virtualhost block points to 127.0.0.1 ... Sorry, I can find a YouTube link that explained this.

+1


source







All Articles