#MAMP APACHE NEEDS OPEN PORT 80 INSTALL#
#MAMP APACHE NEEDS OPEN PORT 80 UPDATE#

Just something to keep in mind.The official MAMP twitter handle recommends renaming the file “envvars” located in into “_envvars”. Luckily, I had Time Machine on my Mac, so I was able to recover my settings and apply them to the new files.

#MAMP APACHE NEEDS OPEN PORT 80 UPDATE#

I found out that doing a major MAMP update will blow away your nf file and your nf. This setup worked great for me until I updated MAMP from version 5 to 6. Note, if you’re running local WordPress sites, you’ll need to do a search and replace on the database to update the URLs. You should be able to access your local dev sites through the new URLs! If it doesn’t work, add “ to the beginning of the URL. Save all of the changes to your nf files, then re-start MAMP.

Once you find it, set it to “All” like this: The solution is to go back into your nf file and search for “AllowOverride”. Basically, the home page would show up, but I couldn’t access any posts or pages. Set AllowOverride in Your nf FileĪfter I did these steps (and doing a search and replace on my site’s database to update the URLs), I got the site to resolve, but s were not working. If you were editing your nf file directly, you’re done with this step.Ĥ. I also added this entry so I could access the project root through a browser: Remember to change the DocumentRoot URL to the appropriate path to your sites on your computer. Now, for each domain name, add an entry to connect it to the appropriate directory path on your computer like this: ĭocumentRoot '/Users/username/projects/mysite'ĭocumentRoot '/Users/username/projects/anothersite'ĭocumentRoot '/Users/username/projects/yetanother' In nf, find this line and make sure it’s uncommented: Include /Applications/MAMP/conf/apache/extra/nf If you do this, make sure that your main nf file includes the nf file. Now, you can edit it directly, or do what I did, which is edit the nf file in the “extra” directory here: /Applications/MAMP/conf/apache/extra/nf You can find it here on MAMP for Mac: /Applications/MAMP/conf/apache/nf If you’re familiar with Apache, you know this happens in the nf file. Now you have to tell Apache which directory to use for each URL. You can choose whatever you want, but don’t use “.dev”, as that has been reserved for other purposes and won’t work in most browsers (I learned this the hard way back when I was using Desktop Server).ģ. Note, I decided to switch to the “.local” top-level domain for my local dev sites. Go ahead and edit it using your favorite text editor and add all your local development sites like this: 127.0.0.1 mysite.local The next step is to direct your local URLs to your localhost by adding them to your hosts file, which is located here on a Mac: /etc/hosts The settings on this page are misleading because port 80 is the actual default value that lets you eliminate the port number in the URL.Īfter restarting, MAMP, you should be able to access your local sites without the port number in the URL like this: 127.0.0.1/īut remember, none of your WordPress sites will work with this URL until you do a search and replace on the database, but we’re not there yet. Unfortunately, when I started using MAMP, I chose their “default” Apache port value of 8888. Here are my step-by-step instructions to get pretty URLs when using MAMP! I did a bunch of research to finally fix this problem to get a clean local development URL of this format: mysite.local So, I figured that a simple entry in my hosts file would fix it, but I discovered that hosts files can’t handle port numbers or subdirectories.

#MAMP APACHE NEEDS OPEN PORT 80 INSTALL#

Also, it was kind of ugly, but this was just for development, so who cares, right?īut, I recently wanted to copy a WordPress Multisite install to my local computer and wasn’t able to get it to work with this URL format. Occasionally, I’d have a problem when a site used root-relative links, but I just lived with that. That was fine for most of my local sites. When I started using MAMP for local website development, my local URLs were of this form: 127.0.0.1:8888/ If you want to keep struggling with MAMP (like I did for a long time), keep reading: The Original Article

I’ve kept the article below for those still using MAMP, but rather than messing with these settings, I’d recommend that you check out LocalWP. Note, since writing this article, I have switched to LocalWP, which is superior to MAMP in practically every way and has clean URLs from the get-go.

Mamp apache needs open port 80