Fix: 'Address Already in Use' (Kill Stuck Process on Any Port)

OneLineDev — Sun, 04 Oct 2026 16:04:53 +0000

The Error

You start your local server (Node, Python, Go, Docker) and get stopped in your tracks:

Error: listen EADDRINUSE: address already in use :::3000

(or bind: address already in use :8080)

Why It Happens

An orphaned background process or crashed terminal session didn't release the TCP socket. Your operating system prevents two applications from listening on the exact same port simultaneously.

⚡ Linux & macOS: Instant One-Liner Fix

Replace 3000 with your blocked port number:

npx kill-port 3000

Native Terminal Alternatives (No Node required):

Option A (Using fuser):

fuser -k 3000/tcp

Option B (Using lsof + kill):

kill -9 $(lsof -t -i:3000)

⚡ Windows: Instant Fix

In PowerShell (One-Liner):

Stop-Process -Id (Get-NetTCPConnection -LocalPort 3000).OwningProcess -Force

In CMD (Command Prompt):

Find the Process ID (PID):

   netstat -ano | findstr :3000

Kill the process using the PID from the rightmost column:

   taskkill /PID <PID> /F

Quick Tip

If you frequently run into this issue during development, install kill-port globally so you can blast any port from any terminal in 1 second:

npm install -g kill-port
kill-port 3000 8080 5000

Fix: 'fatal: refusing to merge unrelated histories' in Git

OneLineDev — Sun, 04 Oct 2026 15:58:53 +0000

The Error

You run git pull or git merge and see:

fatal: refusing to merge unrelated histories

Why It Happens

Git refuses to merge branches that do not share a common ancestor commit. This typically happens when you created a local repo with git init, created a remote repository on GitHub with a default README.md or .gitignore, and then tried to connect them.

The Quick Fix (One-Liner)

Force Git to merge the two independent project histories:

git pull origin main --allow-unrelated-histories

(Note: Replace main with master if your default branch is named master)

If you are merging directly:

git merge origin/main --allow-unrelated-histories

Resolving the Merge & Pushing

If an editor opens for a commit message:
- Vim: Type :wq and hit Enter.
- Nano: Press Ctrl + O, Enter, then Ctrl + X.
If merge conflicts occur:
Open the conflicting files (e.g., README.md), choose which lines to keep, save, and run:

   git add .
   git commit -m "chore: merge unrelated histories"

Push to Remote:

   git push -u origin main

Alternative: Overwrite Local with Remote

If your local commits don't matter and you just want the remote repository's exact state:

git fetch origin
git reset --hard origin/main

Warning: reset --hard permanently discards uncommitted local changes.

DEV Community: OneLineDev

Fix: 'Address Already in Use' (Kill Stuck Process on Any Port)

The Error

Why It Happens

⚡ Linux & macOS: Instant One-Liner Fix

Native Terminal Alternatives (No Node required):

⚡ Windows: Instant Fix

In PowerShell (One-Liner):

In CMD (Command Prompt):

Quick Tip

Fix: 'fatal: refusing to merge unrelated histories' in Git

The Error

Why It Happens

The Quick Fix (One-Liner)

Resolving the Merge & Pushing

Alternative: Overwrite Local with Remote