Problem: Sometimes when you start a local node.js server, it may be stuck running at the background. When you try to start the server again, you will hit error saying that the port (for example 8080) is already is in used and locked:
<pre><code>throw er; // Unhandled ‘error’ event
Error: listen EADDRIUSE 127.0.0.1:8080
</code></pre>Solution: You can try to find the process using <code>lsof</code> command:
<pre><code>lsof -n -i4TCP:8080
</code></pre>Or replace <code>8080</code> with the port number that you want to find. Then you will see a list of processes. Find the process that you want to kill, for example <code>node</code> is running with PID <code>6709</code>, then kill that process with command:
<pre><code>kill -9 &lt;PID&gt;
</code></pre>Finally, start the server again and it will be running as normal after you free the port in use.
Originally published at <a target="_blank" href="https://victorleungtw.com/find-and-kill-process-locking-specific-port-on-mac/">https://victorleungtw.com</a> on February 18, 2020.

Problem: Sometimes when you start a local node.js server, it may be stuck running at the background. When you try to start the server again, you will hit error saying that the port (for example 8080) is already is in used and locked:

```
throw er; // Unhandled ‘error’ event
Error: listen EADDRIUSE 127.0.0.1:8080
```


**Solution**: You can try to find the process using `lsof` command:

```
lsof -n -i4TCP:8080
```


Or replace `8080` with the port number that you want to find. Then you will see a list of processes. Find the process that you want to kill, for example `node` is running with PID `6709`, then kill that process with command:

```
kill -9 <PID>
```


Finally, start the server again and it will be running as normal after you free the port in use.

*Originally published at [https://victorleungtw.com](https://victorleungtw.com/find-and-kill-process-locking-specific-port-on-mac/) on February 18, 2020.*

Find and kill process locking specific port on Mac