Ошибка port already in use

It must be frustrating when you run the Django local server, and you get the “Error: That port is already in use.” You cannot serve your new Django project on a local development setup.

The main cause of the error is serving more than one Django project using the same default port, 8000.

Fortunately, solving the error is a very straightforward process.

To solve the  “error: that port is already in use” in Django, you need to stop the currently running server on port 8000 and free the port for the new Django project.

Here are three ways to solve “Error: That port is already in use” in Django:

Let’s see how we can implement the three methods to solve “Error: That port is already in use” in detail.

Method 1: How to quit Django local development server

Locate the port that you have your Django local server running. 

The Terminal window should look like this:

Press CTRL + C to quit the Django local development server.

It is as simple as that – nothing else that you need to do.

Open another Terminal for the new Django project and try running python manage.py runserver.

Django’s local development server should run successfully because you only have one Django project on port 8000.

There should be no more than one runserver instances running concurrently. Thus, the “Error: That port is already in use” should not show again.

Method 2: How to serve a Django project on a different port

Another way to solve “Error: That port is already in use” is to serve your new Django project on another port different from the default port 8000.

To do that, open a new Terminal window and activate the virtual environment you have installed the new Django project.

Run python manage.py runserver 0.0.0.0:9000 and the error should not appear.

The new Django project should be served using port 9000.

You may use any other port to serve your new Django project.

However, do not serve your Django project on ports already used by other services such as databases. For example, if you use port 5432, which is used by PostgreSQL databases, you will still get the “Error: That port is already in use.”

Serving a new Django project on a different port has its advantage because you can serve different Django projects on the same local machine. Provided you do not have two projects sharing the same port – that is impossible.

As you can see in the screenshot below, I am serving two Django projects, the Django project in the left pane on default port 8000 and the right pane running another Django project on port 9000.

When you access each Django project on the browser, you must specify the specific port number used to serve the Django project.

So, if you are serving a Django project on port 9000, you should open 127.0.0.1:9000 in your browser.

Similarly, if you have another project on port 4000, you should type 127.0.0.1:4000 in the address bar.

The screenshot below shows how to access two Django projects running on ports 8000 and 4000 in the same local machine on a browser.

Method 3: How to kill Django runserver process running in the background

To kill the background Django runserver process, you need to use htop to browse the process in the background and send a signal to kill it. That way, no Django server instances are running on default port 8000.

The final method involves killing the runserver process running in the background. The reasons that could have led to the Django runserver running in the background would be:

1. Pressing CTRL + Z, which suspends the server.
2. Closing the Terminal running the Django server.

By suspending or closing the Terminal window with the Django project, you can only quit the Django development server using htop. htop is a utility you can use to manage background processes running on your Linux machine.

Let’s see how you use htop to quit the Django server running in the background.

But first, you must install the utility before using it. 

Here’s how to install htop on your Linux machine:

Open a new Terminal window and type the following:

sudo apt update 

sudo apt install htop

After a successful install, htop should be ready to use.

Using the same Terminal window or a new one, type htop and press Enter.

Press function key F3 to search the Django server running in the background.

Type ‘runserver’ and you should see the active Django background process highlighted in a bright color.

Press function key F9 to kill the Django development server process.

Use the up-down keys and use signal 9 SIGKILL to quit the Django development server.

Press Enter to kill the process.

Managing Django “Error: That port is already in use is as easy as that.

You may choose to serve only one Django project using the default server.

Alternatively, you may choose to server more than one Django project on different port numbers. 

When serving Django projects on different ports, you should not have two Django projects sharing the same port.

Besides, avoid using port numbers used by other services such as databases.

If you have a PostgreSQL database, then port 5432 should not be used to serve Django websites on a local machine.

And that’s it basically for this article.

See you next time, Dev!

• nodemon -v: 1.14.12
• node -v: 9.4.0
• Operating system/terminal environment: macOS High Sierra / zsh
• Command you ran:

$ concurrently -k "webpack -d --config ./webpack/config/webpack.dev.config.js --watch" "nodemon ./bin/app.bundle"

This was my first attempt to update the Webpack build and restart the server simultaneously using concurrently. I thought maybe concurrently was causing some issues, so I opted for the Nodemon Webpack Plugin instead, only to find I was getting the same issue.

Expected behaviour

Nodemon should kill the server clean every time it restarts, or when it exits.

Actual behaviour

I’m informed that my server’s port is already running when Nodemon starts it («Port 8080 is already in use»), even after forcibly killing the server on that port using the process ID listened with lsof -i. When files change and Nodemon restarts, sometimes it actually listens on the port, but most of the time it just complains the port is already in use. A clean reboot of my system usually makes the problem go away temporarily.

Steps to reproduce

Unfortunately, an extremely tricky issue to reproduce, seeing there does not seem to be a clear case of when it happens or when it doesn’t. It happens randomly, very often but not frequently. Here is how my server is being set up, though:

const port = normalizePort(process.env.PORT || '8080');
app.set('port', port);

if (port) {
  const server = http.createServer(app);

  server.listen(port);
  server.on('error', onError);
  server.on('listening', onListening);

  process.on('uncaughtException', () => server.close());
  process.on('SIGTERM', () => server.close());
  process.on('exit', () => server.close());

  function onError(error) {
    if (error.syscall !== 'listen') {
      throw error;
    }

    const bind = typeof port === 'string' ? `Pipe ${port}` : `Port ${port.toString()}`;

    switch (error.code) {
      case 'EACCES':
        console.error(`${bind} requires elevated privileges`);
        process.exit(1);
        break;
      case 'EADDRINUSE':
        console.error(`${bind} is already in use`);
        process.exit(1);
        break;
      default:
        throw error;
    }
  }

  function onListening() {
    const addr = server.address();
    const bind = typeof addr === 'string' ? `pipe ${addr}` : `port ${addr.port}`;
    debug(`Listening on ${bind}`);
    console.log(`Server started on ${bind}`);
  }
}

function normalizePort(val) {
  const port = parseInt(val, 10);

  if (isNaN(port)) {
    // named pipe
    return val;
  }

  if (port >= 0) {
    // port number
    return port;
  }

  return false;
}

If applicable, please append the --dump flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.

1. tcpview.exe from SysInternals
2. PowerShell scripts
3. Netstat

cls
$tcpPort = "1433"
$tcpConn = Get-NetTCPConnection | Where-Object {$_.LocalPort -eq $tcpPort -or $_.RemotePort -eq $tcpPort}
$tcpConn
$process = $tcpConn | Select-Object OwningProcess -Unique
if ($process -ne $null)
{
    Get-Process | Where-Object {$_.id -eq $process.OwningProcess} | Select-Object Id, ProcessName
}
else
{
    write-output "No services found using that port"
}