Error map

could not connect PostgreSQL: could not connect to server / connection refused — Is the server running on host and accepting TCP/IP connections?

PostgreSQL · layer 5, Data

Open the full error page →

Centre: this error. First ring: errors it is linked with (11). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

could not connect — PostgreSQL: could not connect to server / connection refused — Is the server running on host and accepting TCP/IP connections? (PostgreSQL)could not c…28P01 — PostgreSQL: FATAL: password authentication failed for user (PostgreSQL)28P01connection closed — server closed the connection unexpectedly — This probably means the server terminated abnormally before or while processing the request. (PostgreSQL)connection closed2002 — MySQL ERROR 2002 (HY000): Can't connect to local MySQL server through socket (MySQL)2002Prisma P1001 — Error: P1001: Can't reach database server at `host`:`5432` (Node.js)Prisma P1001connection limit for role — FATAL: too many connections for role "x" (PostgreSQL)connection limit fo…3D000 — FATAL: database "x" does not exist (PostgreSQL)3D00053300 — FATAL: sorry, too many clients already / remaining connection slots are reserved for non-replication superuser connections (PostgreSQL)53300SQLAlchemy OperationalError — sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server … failed (Python)SQLAlchemy Operatio…ECONNREFUSED — Error: connect ECONNREFUSED 127.0.0.1:5432 (Node.js)ECONNREFUSEDSSL required — server does not support SSL, but SSL was required / no pg_hba.conf entry … no encryption (PostgreSQL)SSL requiredSequelizeConnectionRefusedError — SequelizeConnectionRefusedError: connect ECONNREFUSED 127.0.0.1:5432 (Node.js)SequelizeConnection…1045 — MySQL ERROR 1045 (28000): Access denied for user (MySQL)104542P01 — PostgreSQL: ERROR: relation "x" does not exist (PostgreSQL)42P0142501 — PostgreSQL: ERROR: permission denied for table / schema public (PostgreSQL)425012006 — MySQL ERROR 2006 (HY000): MySQL server has gone away (MySQL)2006HikariCP timeout — HikariPool-1 - Connection is not available, request timed out after 30000ms (Java)HikariCP timeoutDB connection — WordPress: Error Establishing a Database Connection (WordPress)DB connection1040 — MySQL ERROR 1040 (08004): Too many connections (MySQL)1040Communications link failure — com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure (Java)Communications link…buffering timed out — MongooseError: Operation `users.find()` buffering timed out after 10000ms (Node.js)buffering timed outMongoServerSelectionError — MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017 (Node.js)MongoServerSelectio…Prisma P2002 — PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`) (Node.js)Prisma P200253100 — ERROR: could not extend file "base/…": No space left on device (PostgreSQL)53100508 — HTTP 508 Loop Detected (Resource Limit Is Reached) (HTTP)508509 — HTTP 509 Bandwidth Limit Exceeded (HTTP)5091049 — MySQL ERROR 1049 (42000): Unknown database 'x' (MySQL)1049out of shared memory — ERROR: out of shared memory — HINT: You might need to increase max_locks_per_transaction. (PostgreSQL)out of shared memoryapi_version_invalid — API Error: Invalid or unsupported API version (API)api_version_invalidSkuNotAvailable — Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource (Azure)SkuNotAvailableInsufficientInstanceCapacity — InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested (AWS)InsufficientInstanc…AllocationFailed — Azure VM: AllocationFailed / ZonalAllocationFailed — Allocation failed. We do not have sufficient capacity for the requested VM size (Azure)AllocationFailedLazyInitializationException — org.hibernate.LazyInitializationException: could not initialize proxy - no Session (Java)LazyInitializationE…TransientObjectException — org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing (Java)TransientObjectExce…Hibernate ConstraintViolationException — org.hibernate.exception.ConstraintViolationException: could not execute statement (Java)Hibernate Constrain…EADDRINUSE — Error: listen EADDRINUSE: address already in use :::3000 (Node.js)EADDRINUSEFailed to fetch — TypeError: Failed to fetch / NetworkError when attempting to fetch resource (JavaScript)Failed to fetchETIMEDOUT — API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded) (API)ETIMEDOUTCERTIFICATE_VERIFY_FAILED — SSL: CERTIFICATE_VERIFY_FAILED / unable to get local issuer certificate (API)CERTIFICATE_VERIFY_…tlsv1 alert protocol version — SSL error: tlsv1 alert protocol version / unsupported protocol / no protocols available (API)tlsv1 alert protoco…Pending validation — ACM certificate stuck in Pending validation (AWS)Pending validation

Directly related (11)

28P01PostgreSQL

PostgreSQL: FATAL: password authentication failed for user

PostgreSQL rejected the password for that role, or pg_hba.conf requires a different auth method.

connection closedPostgreSQL

server closed the connection unexpectedly — This probably means the server terminated abnormally before or while processing the request.

The connection to PostgreSQL dropped — the server restarted/crashed, a proxy/firewall killed an idle connection, or the backend w…

2002MySQL

MySQL ERROR 2002 (HY000): Can't connect to local MySQL server through socket

The client couldn’t reach the MySQL server — it isn’t running, or the client is looking for the socket/port in the wrong place.

Prisma P1001Node.js

Error: P1001: Can't reach database server at `host`:`5432`

Prisma couldn’t connect to the database in DATABASE_URL.

connection limit for rolePostgreSQL

FATAL: too many connections for role "x"

The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).

3D000PostgreSQL

FATAL: database "x" does not exist

The connection names a database that isn’t on that server.

53300PostgreSQL

FATAL: sorry, too many clients already / remaining connection slots are reserved for non-replication superuser connections

PostgreSQL reached max_connections.

SQLAlchemy OperationalErrorPython

sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server … failed

SQLAlchemy’s DB driver raised an operational error — connection failures, lost connections or locked SQLite databases.

ECONNREFUSEDNode.js

Error: connect ECONNREFUSED 127.0.0.1:5432

Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.

SSL requiredPostgreSQL

server does not support SSL, but SSL was required / no pg_hba.conf entry … no encryption

The client and server disagree about SSL — the client requires it but the server doesn’t offer it, or the server requires it and…

SequelizeConnectionRefusedErrorNode.js

SequelizeConnectionRefusedError: connect ECONNREFUSED 127.0.0.1:5432

Sequelize couldn’t connect to the database server.

Two steps away (29)

1045MySQL

MySQL ERROR 1045 (28000): Access denied for user

MySQL rejected the login — wrong password, wrong user/host combination, or the user doesn’t exist.

42P01PostgreSQL

PostgreSQL: ERROR: relation "x" does not exist

The table/view isn’t found — missing migration, wrong schema, or a case-sensitive quoted name.

42501PostgreSQL

PostgreSQL: ERROR: permission denied for table / schema public

The role is connected but lacks privileges on that table or schema — very common after PostgreSQL 15 removed CREATE on the public…

2006MySQL

MySQL ERROR 2006 (HY000): MySQL server has gone away

The connection to MySQL was closed — usually by a timeout or a packet larger than `max_allowed_packet`.

HikariCP timeoutJava

HikariPool-1 - Connection is not available, request timed out after 30000ms

The connection pool was exhausted — all connections were busy for 30 seconds.

DB connectionWordPress

WordPress: Error Establishing a Database Connection

WordPress can’t connect to its MySQL/MariaDB database with the credentials in wp-config.php, or the database server is down.

1040MySQL

MySQL ERROR 1040 (08004): Too many connections

MySQL reached `max_connections` and refuses new clients.

Communications link failureJava

com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

The MySQL JDBC driver couldn’t reach the database (or the connection dropped).

buffering timed outNode.js

MongooseError: Operation `users.find()` buffering timed out after 10000ms

Mongoose queued a query waiting for a connection that never opened.

MongoServerSelectionErrorNode.js

MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017

The MongoDB driver couldn’t find a reachable server for the connection string.

Prisma P2002Node.js

PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`)

A Prisma create/update violated a unique constraint.

53100PostgreSQL

ERROR: could not extend file "base/…": No space left on device

The disk holding the PostgreSQL data directory (or WAL) is full.

508HTTP

HTTP 508 Loop Detected (Resource Limit Is Reached)

Either the server detected an infinite loop (WebDAV) or — much more often — a cPanel/CloudLinux host is saying your account hit i…

509HTTP

HTTP 509 Bandwidth Limit Exceeded

A hosting-control-panel status (cPanel/Apache) meaning the account used up its monthly bandwidth allowance.

1049MySQL

MySQL ERROR 1049 (42000): Unknown database 'x'

The database named in the connection doesn’t exist on that server.

out of shared memoryPostgreSQL

ERROR: out of shared memory — HINT: You might need to increase max_locks_per_transaction.

A transaction took more locks than the lock table can hold — usually touching many tables/partitions at once.

api_version_invalidAPI

API Error: Invalid or unsupported API version

The API version you requested — in the URL, a header or the SDK config — doesn’t exist or has been retired.

SkuNotAvailableAzure

Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource

The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.

InsufficientInstanceCapacityAWS

InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested

AWS has no free capacity for that instance type in that Availability Zone right now.

AllocationFailedAzure

Azure VM: AllocationFailed / ZonalAllocationFailed — Allocation failed. We do not have sufficient capacity for the requested VM size

Azure has no capacity for that VM size in the region/zone (or in the cluster the VM is pinned to) right now.

LazyInitializationExceptionJava

org.hibernate.LazyInitializationException: could not initialize proxy - no Session

A lazy-loaded association was accessed after the Hibernate session/transaction closed.

TransientObjectExceptionJava

org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing

An entity references another entity that hasn’t been saved yet, and no cascade is configured.

Hibernate ConstraintViolationExceptionJava

org.hibernate.exception.ConstraintViolationException: could not execute statement

The database rejected an insert/update because of a constraint (unique, foreign key, not null).

EADDRINUSENode.js

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

Another process is already listening on that port.

Failed to fetchJavaScript

TypeError: Failed to fetch / NetworkError when attempting to fetch resource

The browser couldn’t complete the request at the network level — CORS, DNS, offline, blocked mixed content, or the server refused…

ETIMEDOUTAPI

API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded)

The client gave up waiting — either for the connection to open or for the response to arrive.

CERTIFICATE_VERIFY_FAILEDAPI

SSL: CERTIFICATE_VERIFY_FAILED / unable to get local issuer certificate

The client couldn’t verify the server’s TLS certificate chain, so it refused the HTTPS connection.

tlsv1 alert protocol versionAPI

SSL error: tlsv1 alert protocol version / unsupported protocol / no protocols available

The client and server couldn’t agree on a TLS version or cipher, so the HTTPS handshake failed before any HTTP was exchanged.

Pending validationAWS

ACM certificate stuck in Pending validation

ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.