ERR_INSUFFICIENT_RESOURCES
gcerdas16
HOBBYOP

17 days ago

Description of the Issue

Experiencing ERR_INSUFFICIENT_RESOURCES errors on backend service despite healthy metrics. Started Jan 27, 2026 at 11:16 AM CST during deployment.

Status:

  • Frontend: Working white_check_mark emoji

  • Database: Healthy (11/100 connections) white_check_mark emoji

  • Backend: Rejecting all API requests with ERR_INSUFFICIENT_RESOURCES x emoji

Metrics:

  • RAM: 250 MB / 512 MB (50%)

  • CPU: 0.1 vCPU

  • PostgreSQL: 11/100 connections

  • Connection pool: max 10, min 2, idle timeout 30s

Backend shows "Active" status but rejects all incoming requests.

Error Message

GET https://backend-production-32b0.up.railway.app/api/cart/count
net::ERR_INSUFFICIENT_RESOURCES

GET https://backend-production-32b0.up.railway.app/api/products
net::ERR_INSUFFICIENT_RESOURCES

Service:backend-production-32b0.up.railway.app
Deployment ID:6a0804f4
Time: Jan 27, 2026 at 11:16 AM CST

Timeline:

  • 11:20:59 - Old deployment received SIGTERM

  • 11:21:19 - New deployment started

  • 11:21:19+ - All API calls return ERR_INSUFFICIENT_RESOURCES

Logs

Backend Deploy Logs:

Jan 27 2026 at 11:21:19  Servidor corriendo en puerto 8080
Jan 27 2026 at 11:21:19  Conectado a PostgreSQL

Jan 27 2026 at 11:20:59 npm error signal SIGTERM
Jan 27 2026 at 11:20:59 npm error command failed

Database Status (verified locally):

Max connections: 100
Current: 11 (11%)
Status: HEALTHY

Code

Database Pool (backend/src/config/database.js):

javascript

const pool = new Pool({
  max: 10,
  min: 2,
  idleTimeoutMillis: 30000,
  connectionTimeoutMillis: 10000,
});

Server (backend/src/server.js):

javascript

const app = express();
app.use(cors({ origin: process.env.FRONTEND_URL }));
app.use(express.json());
app.listen(PORT, '0.0.0.0');

Stack:

  • Node.js + Express

  • PostgreSQL (pg@8.11.3)

  • Railway Hobby Plan

  • 3 services: Backend, Frontend, Database

Questions:

  1. Could deployment overlap (old shutting down + new starting) cause resource exhaustion?

  2. Is there a Railway infrastructure limit we're hitting despite available resources?

  3. Any Node.js configuration recommendations for Hobby plan?

Solved$10 Bounty

Pinned Solution

darseen
HOBBYTop 1% Contributor

17 days ago

net::ERR_INSUFFICIENT_RESOURCES is a client-side (browser) error, not a server-side one. It simply means your browser runs out of memory due to making too many requests, in most scenarios. I would suggest you inspect yourNetwork tab in chrome dev tools, and see how many requests you're making to the server. Also, check your forntend code as well, as the issue most certainly stems from it.

4 Replies

darseen
HOBBYTop 1% Contributor

17 days ago

net::ERR_INSUFFICIENT_RESOURCES is a client-side (browser) error, not a server-side one. It simply means your browser runs out of memory due to making too many requests, in most scenarios. I would suggest you inspect yourNetwork tab in chrome dev tools, and see how many requests you're making to the server. Also, check your forntend code as well, as the issue most certainly stems from it.


Anonymous
HOBBY

17 days ago

logs?


darseen

net::ERR_INSUFFICIENT_RESOURCES is a client-side (browser) error, not a server-side one. It simply means your browser runs out of memory due to making too many requests, in most scenarios. I would suggest you inspect yourNetwork tab in chrome dev tools, and see how many requests you're making to the server. Also, check your forntend code as well, as the issue most certainly stems from it.

gcerdas16
HOBBYOP

16 days ago

It worked, it changed the perspective of how I was looking for the error message and now I got my service back. Appreciate it.


gcerdas16

It worked, it changed the perspective of how I was looking for the error message and now I got my service back. Appreciate it.

darseen
HOBBYTop 1% Contributor

16 days ago

You're welcome


Status changed to Solved brody 16 days ago


Loading...