# Local silicon issues: Mailpit, port conflict, site 404 errors

**URL:** <https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249>\
**Category:** Support\
**Created:** [May 22, 2025, 9:41pm UTC](https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249 "2025-05-22T21:41:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![julianpm1](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/julianpm1/32/24320_2.png) [@julianpm1](https://community.localwp.com/u/julianpm1)\
**Post date:** [May 22, 2025, 9:41pm UTC](https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249/1 "2025-05-22T21:41:12Z")

</div>

### What issue or error are you experiencing?

I recently got a new Mac with an M4 chip. I downloaded the silicon-specific version of Local and dragged it into my `Applications` folder. My Local app started up again without any issues.

Then today I started seeing Mailpit not installed errors. I found the solution in another ticket and that is resolved.

Now I am getting errors such as:

`Warning! This site's WordPress URL settings do not match the host set in Local.`’

and

`There is a port conflict with this site's domain. Learn more`

The site that I am getting the unmatched WordPress URL settings is now giving me a `404` error when I open the site. Previously I accidentally clicked `use localhost` for this but I believe I have reset the domain everywhere (including the database).

The site with the `port conflict` error still opens as normal

* * *

### What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

 ![Screenshot 2025-05-22 at 5.37.56 PM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/6/1/61b656513aceba80fafb3aed608103721595689d.png)

* * *

### System Details

- **Local Version:**

- Version 9.2.4+6788

- **Operating System (OS) and OS version:**

- Sequoia 15.4.1

* * *

### Local Logs

Attach your Local Logs here ([Help Doc - Retrieving Local’s Log](https://localwp.com/help-docs/troubleshooting/retrieving-locals-log-file/))

`2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:1 2025/05/22 17:32:47 [warn] 6759#0: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /Users/trewknowledge011/Library/Application Support/Local/run/router/nginx/conf/server-block-ssl.conf:2 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:80 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to 0.0.0.0:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: bind() to [::]:443 failed (48: Address already in use) 2025/05/22 17:32:47 [emerg] 6759#0: still could not bind()`

* * *

_ **Security Reminder** _  
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

---

<div class="post-metadata">

**Author:** ![nickc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nickc/32/21209_2.png) [@nickc](https://community.localwp.com/u/nickc)\
**Post date:** [May 23, 2025, 1:09pm UTC](https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249/2 "2025-05-23T13:09:39Z")

</div>

> [@julianpm1](#):
>
> [emerg] 6759#0: bind() to 0.0.0.0:80 failed (48: Address already in use)

Do you have any other applications running on port 80? Local needs it to be able to serve your sites, so you’ll have to shut down the other application using port 80 first.

With Local closed, you could try this from the command line:

```auto
sudo lsof -i ':80'

```

---

<div class="post-metadata">

**Author:** ![julianpm1](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/julianpm1/32/24320_2.png) [@julianpm1](https://community.localwp.com/u/julianpm1)\
**Post date:** [May 23, 2025, 3:20pm UTC](https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249/3 "2025-05-23T15:20:29Z")

</div>

Hi Nick, thanks for the reply.

I ran the command in my terminal (with Local closed) and this is what happened:

`COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Google 1596 trewknowledge011 29u IPv6 0xdaa5fc0442ae4d0e 0t0 TCP [2607:fea8:7e15:c800:14bd:d664:99e5:8b04]:49854->[2600:1900:4110:86f::]:http (ESTABLISHED)`

I restarted Local and started a site, but still got the same error of `There is a port conflict with this site's domain.`

Sometimes I see this error and sometimes I don’t.

---

<div class="post-metadata">

**Author:** ![nickc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nickc/32/21209_2.png) [@nickc](https://community.localwp.com/u/nickc)\
**Post date:** [May 23, 2025, 3:51pm UTC](https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249/4 "2025-05-23T15:51:57Z")

</div>

Thanks, @julianpm1. If this is intermittent it sounds like something else is sometimes running on port 80. The ‘Google’ command doesn’t look like it here.

You could try:

1. Opening Activity Monitor (with Local closed), searching for, and killing any nginx processes.
2. Restarting your machine. This will normally stop any orphaned processes.

If you’re running any other development software that could also be a candidate.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [August 21, 2025, 3:52pm UTC](https://community.localwp.com/t/local-silicon-issues-mailpit-port-conflict-site-404-errors/50249/5 "2025-08-21T15:52:41Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
