---
title: "How do you resolve EADDRINUSE port collision errors during PM2 Next.js deployment?"
type: FAQ
category: "deployment"
slug: "port-collisions-pm2-watchdog-resolution"
id: 8
facility_tags: ["deployment-safety","port-alignment"]
service_tags: ["pm2-watchdog","locks-management"]
---

# How do you resolve EADDRINUSE port collision errors during PM2 Next.js deployment?

Multi-tenant VPS nodes frequently experience port collisions when launching concurrent dev servers. To prevent conflicts, we dedicate specific port allocations inside ecosystem.config.cjs: the recipesmd site runs on port 4095, while the fifapanini site is allocated port 4093.

## Detailed Deep Dive
Multi-tenant VPS nodes frequently experience port collisions when launching concurrent dev servers. To prevent conflicts, we dedicate specific port allocations inside ecosystem.config.cjs: the recipesmd site runs on port 4095, while the fifapanini site is allocated port 4093. Standalone builds copy static files to .next/standalone/ before PM2 starts server.js inside the directory. Watchdog lock files ensure that active compilation steps do not collide.

### Metadata Tags
- **Category**: deployment
- **Required Tags**: deployment-safety, port-alignment
- **Context Tags**: pm2-watchdog, locks-management