<p>Unless instructed otherwise, MAMP uses port 8888. You can tell it to use the "default" ports, which will mean the site gets served over port 80, and your URLs no longer contain <code>:8888</code>.</p>

<p>As for the other issue, it sounds like you haven't set up your site's document root correctly. Either way, it's a MAMP configuration issue, not a Craft issue.</p>

CC BY-SA 3.0
2017-05-01T17:15:49.893Z
Thanks Stephen and Brad for your answers! Indeed I can change the port 8888 to the default port. I am going to try to set up my site's document root again, do you know what could cause that in the configuration? Could it be an issue with the database also/
Lisonc
CC BY-SA 3.0
2017-05-01T22:33:07.537Z
Problem solved! I don't know exactly what I did wrong the last time but I started the set up again and this time everything works perfectly. Thanks again!
Lisonc
CC BY-SA 3.0
2017-04-29T18:43:00.193Z
2017-04-29T18:43:00.193Z
Stephen Lewis
<p>I downloaded and installed Craft Personal on my computer and choose /<strong>websitetest</strong>/ as my website name. I used MAMP and phpMyAdmin to create a database.</p>

<hr>

<p>Still to access my website the url is <a href="http://localhost:8888/" rel="nofollow noreferrer">http://localhost:8888/</a> and when I try to access <a href="http://localhost/websitetest/" rel="nofollow noreferrer">http://localhost/websitetest/</a> I get the following error message: <strong>Forbidden
You don't have permission to access /websitetest/ on this server.</strong></p>

<hr>

<p>Moreover in my index.html file, when I call for an URL entry:</p>

<p>href="{{ entry.url }}"</p>

<p>by default it redirects towards <strong>/websitetest/_entry</strong> , which displays me the same error message, while <strong>localhost:8888/_entry</strong> works when I test it manually!</p>

<hr>

<p>Some ideas where can this come from?</p>

<p>Thanks!</p>

CC BY-SA 3.0
2017-04-29T14:31:53.373Z
If you want to get rid of the `:8888` port number, you're going to have to tell MAMP about it. I'm assuming there is some MAMP port settings for your site.  If a domain doesn't have a port, it's assumed to be port 80, so try changing it to that.
Brad Bell
<entry><database><url><siteurl>
How do I set my siteURL instead of having http://localhost:8888/?
# How do I set my siteURL instead of having http://localhost:8888/?

(Asked by: username_0 on 2017-04-29)

I downloaded and installed Craft Personal on my computer and choose /**websitetest**/ as my website name. I used MAMP and phpMyAdmin to create a database.

---

Still to access my website the url is <http://localhost:8888/> and when I try to access <http://localhost/websitetest/> I get the following error message: **Forbidden
You don't have permission to access /websitetest/ on this server.**

---

Moreover in my index.html file, when I call for an URL entry:

href="{{ entry.url }}"

by default it redirects towards **/websitetest/\_entry** , which displays me the same error message, while **localhost:8888/\_entry** works when I test it manually!

---

Some ideas where can this come from?

Thanks!

**Tags:** entry, database, url, siteurl

> **Comments:**
> **username_1**: If you want to get rid of the `:8888` port number, you're going to have to tell MAMP about it. I'm assuming there is some MAMP port settings for your site.  If a domain doesn't have a port, it's assumed to be port 80, so try changing it to that.  

---

## 1 answers

### Answer by username_2 on 2017-04-29. Score: 2 | Accepted answer

Unless instructed otherwise, MAMP uses port 8888. You can tell it to use the "default" ports, which will mean the site gets served over port 80, and your URLs no longer contain `:8888`.

As for the other issue, it sounds like you haven't set up your site's document root correctly. Either way, it's a MAMP configuration issue, not a Craft issue.

> **Comments:**
> **username_0**: Thanks Stephen and Brad for your answers! Indeed I can change the port 8888 to the default port. I am going to try to set up my site's document root again, do you know what could cause that in the configuration? Could it be an issue with the database also/  
> **username_0**: Problem solved! I don't know exactly what I did wrong the last time but I started the set up again and this time everything works perfectly. Thanks again!  

---

