![]() ![]() ![]() I know you stated you're not using any proxy. Run the built-in Apache by enabling System Preferences, Sharing, Web Sharing.Change the Listen port of the built-in Apache from 80 to 8080:.To ensure it's not an issue with your web server (like asked: what server are you using?), on my 10.6 Snow Leopard with IPv6 left at automatic, and even with 127.0.0.1 testing.localhost added to my /etc/hosts, the following works fine: Select your Network Connection > Advanced.I would be inclined to turn off IPv6 and remove the entry from the hosts file (temporarily just for testing) Some forum threads suggest IPv6 resolution is causing this issue. I downloaded and installed MAMP, and I could not reproduce this error. When you say "applications can connect as normal" with Chrome and Firefox, what are you seeing? The web page you're expecting to see? A different error? Secondly, have you tried connecting to testing.localhost with Safari, just incase the two entries are confusing Safari (this is entirely possible). So first, you need to have something running. I'm going to guess you have a web server running to accept requests? I currently don't, and Safari won't connect to 127.0.0.1, because it "Couldn't find 127.0.0.1" - even though I can ping it just fine. Anybody else seeing this? I hate being the only one.I think we need a little more information based on your question. Quit/ atsutil server -shutdown has always fixed, but now it’s happening about every 10 minutes. In the past Chrome would sometimes go font-haywire, turning everything on screen into inscrutable characters.Many thanks to Joel Yeaton for pointing out the solution for PCKeyboardHack.And then I noticed that KeyRemap4MacBook had been updated for 10.8.Bollocks to upgrades (he says knowing he can’t turn one down). My hack that turns my Caps-Lock into an escape key isn’t working anymore, either, which is seriously messing up my typical Vim usage.If you’ve figured out a better way to keep Apache/httpd running, let me know. I’m not sure this is the best way to handle this, yet, but it’s working. ![]() It has to be owned by root to run automatically without authentication. Label ProgramArguments /usr/sbin/apachectl start RunAtLoad ![]() Uncomment line 477 (remove the # at the beginning). You’ll need to authenticate as root (System Admin) to save it. If you had a previous setup, you’ll probably quickly notice that your virtual hosts aren’t working… Enable Virtual Hosts and PHPįirst, make the following edits to /etc/apache2/nf. To turn Apache on to begin with, you need to run sudo apachectl start (I’ll get to automating that in a minute). If you want an easy way to run multiple local environments and aren’t already using the built-in Apache server, you might want to just look into MAMP. This is just how to bring one back to life after a Mountain Lion upgrade. If you’re looking for instructions on how to set up a local hosting environment, check this post. I’ve seen some of this posted in a few places, but this serves as a note-to-self. Now that there’s no button to click to turn it on, you have to do things yourself. Mountain Lion moves “web sharing” out of the System Preferences interface (and into Mountain Lion Server), and disables Apache by default. ![]()
0 Comments
Leave a Reply. |