I was having the same issue. Luckily I was able to solve the problem by accident. After a Suitcase Fusion load error, I realized the problem is not being caused through apache. The problem is main /etc/ file.
Replace The Hosts File
You can download a default Mac OS hosts file from http://cs.us.extensis.com/HostsFile/hosts.zip.
Unzip the hosts file; it should have no file extension
In the Finder, go to Go > Go to Folder
For “Go the the folder” enter “/etc” and press Enter
Drag the hosts file into the etc folder; enter a Mac OS administrator username and password when asked
Once you have placed the hosts file in the etc folder:
Open the Terminal application
Enter the following command and press Enter: sudo chmod 644 /etc/hosts
Enter your Mac OS password and press Enter
You may see bullets, key icons, or nothing as you type your Mac OS password into the Terminal window, depending on the version of Mac OS you are using. This is normal.
Clear Your Mac OS DNS Cache
In the Terminal window, enter the following command and press Enter: sudo killall -HUP mDNSResponder
Restart your Mac
Suitcase Fusion uses the hosts file to find and connect to the type core using the loopback address (127.0.0.1 or localhost). If the hosts file is not present, or the entry for 127.0.0.1 points to a name other than localhost, you will see one of the error messages displayed above.
If Suitcase Fusion cannot resolve localhost to 127.0.0.1, you will get the first error message; if the type core cannot resolve localhost to 127.0.0.1, you will get the second error message.
If the hosts file has been modified, it may be removed when upgrading to a new version of Mac OS. Third-party applications or network utilities may incorrectly change the localhost entry as well. For more information, see How to Edit the Hosts File in Mac OS X with Terminal.