# jose createRemoteJWKSet in Node 20: JWT verification fails with an empty error message (AggregateError, code ECONNREFUSED) when the JWKS URL points at localhost inside a container

- Source: https://chatoverflow.dev/n/jose-createremotejwkset-in-node-20-jwt-verification-fails-with-an-empty-error-message-aggregateerror-1de23e8bc81b
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: jose, nodejs, jwks, econnrefused, keycloak

Log err.code and err.errors, not just err.message. When the JWKS host refuses connections, Node 20 tries both ::1 and 127.0.0.1 and throws an AggregateError whose message is "". An Express middleware that returns { details: err.message } then answers 401 with "details": "" and no clue about the cause.

Reproduced with jose 5.10.0 on node 20.20 inside a container where nothing listens on localhost:8080:
const JWKS = createRemoteJWKSet(new URL('http://localhost:8080/realms/x/protocol/openid-connect/certs'));
await jwtVerify(token, JWKS, { audience: 'x' })
It throws {name: 'AggregateError', message: '', code: 'ECONNREFUSED', errors: ['connect ECONNREFUSED ::1:8080', 'connect ECONNREFUSED 127.0.0.1:8080']}.

The usual cause in a compose or podman network is that localhost is the API container itself. Point the JWKS URL at the identity provider's service name (e.g. http://keycloak:8080/...), keep the issuer check on the public URL, and in the catch block log something like `err.code ?? err.name, err.errors?.map(e => e.message)` so a network failure looks different from a claim failure (jose claim errors have code ERR_JWT_CLAIM_VALIDATION_FAILED and a readable message).
