Assistance with heroku setup

[brad-decker]

Hey there, since you helped me with #24, I was able to get past the first rejection, but now when I attempt to use the cache handler, I get a new error.

I am unsure of what this means, or how to handle it. It also appears like this is causing my other usage of redis within the site (for caching expensive rest queries etc) to fail as well. I even upgraded my redis plan on staging to check and see if this was a limitation of my account type:

concierge-web:build:    Collecting page data ...
       concierge-web:build: Redis client error [Error: Client network socket disconnected before secure TLS connection was established] {
       concierge-web:build:   code: 'ECONNRESET',
       concierge-web:build:   path: undefined,
       concierge-web:build:   host: 'ec2-52-44-168-108.compute-1.amazonaws.com',
       concierge-web:build:   port: 11000,
       concierge-web:build:   localAddress: undefined
       concierge-web:build: } 0
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Redis client error [Error: Client network socket disconnected before secure TLS connection was established] {
       concierge-web:build:   code: 'ECONNRESET',
       concierge-web:build:   path: undefined,
       concierge-web:build:   host: 'ec2-52-44-168-108.compute-1.amazonaws.com',
       concierge-web:build:   port: 11000,
       concierge-web:build:   localAddress: undefined
       concierge-web:build: } 0
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: [ioredis] Unhandled error event: Error: Client network socket disconnected before secure TLS connection was established
       concierge-web:build:     at TLSSocket.onConnectEnd (node:_tls_wrap:1732:19)
       concierge-web:build:     at TLSSocket.emit (node:events:530:35)
       concierge-web:build:     at endReadableNT (node:internal/streams/readable:1698:12)
       concierge-web:build:     at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
       concierge-web:build: Redis client error [Error: Client network socket disconnected before secure TLS connection was established] {
       concierge-web:build:   code: 'ECONNRESET',
       concierge-web:build:   path: undefined,
       concierge-web:build:   host: 'ec2-52-44-168-108.compute-1.amazonaws.com',
       concierge-web:build:   port: 11000,
       concierge-web:build:   localAddress: undefined
       concierge-web:build: } 0
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to connect subscriber client. Retrying...
       concierge-web:build: Failed to connect subscriber client. [Error: Socket already opened]
       concierge-web:build: Error setting up pub/sub client: [Error: Socket already opened]
       concierge-web:build: Failed to setup SyncedMap: [Error: Socket already opened]
       concierge-web:build: [Error: Socket already opened]
       concierge-web:build: Failed to reconnect Redis client after connection loss: [Error: Socket already opened]
       concierge-web:build: Failed to reconnect Redis client after connection loss: [Error: Socket already opened]
       concierge-web:build: [ioredis] Unhandled error event: Error: Client network socket disconnected before secure TLS connection was established
       concierge-web:build:     at TLSSocket.onConnectEnd (node:_tls_wrap:1732:19)
       concierge-web:build:     at TLSSocket.emit (node:events:530:35)
       concierge-web:build:     at endReadableNT (node:internal/streams/readable:1698:12)
       concierge-web:build:     at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
       concierge-web:build: Redis client error [Error: Client network socket disconnected before secure TLS connection was established] {
       concierge-web:build:   code: 'ECONNRESET',
       concierge-web:build:   path: undefined,
       concierge-web:build:   host: 'ec2-52-44-168-108.compute-1.amazonaws.com',
       concierge-web:build:   port: 11000,
       concierge-web:build:   localAddress: undefined
       concierge-web:build: } 1
       concierge-web:build: [ioredis] Unhandled error event: Error: Client network socket disconnected before secure TLS connection was established
       concierge-web:build:     at TLSSocket.onConnectEnd (node:_tls_wrap:1732:19)
       concierge-web:build:     at TLSSocket.emit (node:events:530:35)
       concierge-web:build:     at endReadableNT (node:internal/streams/readable:1698:12)
       concierge-web:build:     at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
       concierge-web:build: Redis client error [Error: Client network socket disconnected before secure TLS connection was established] {
       concierge-web:build:   code: 'ECONNRESET',
       concierge-web:build:   path: undefined,
       concierge-web:build:   host: 'ec2-52-44-168-108.compute-1.amazonaws.com',
       concierge-web:build:   port: 11000,
       concierge-web:build:   localAddress: undefined
       concierge-web:build: } 2
       concierge-web:build: Redis client error [Error: Client network socket disconnected before secure TLS connection was established] {
       concierge-web:build:   code: 'ECONNRESET',
       concierge-web:build:   path: undefined,
       concierge-web:build:   host: 'ec2-52-44-168-108.compute-1.amazonaws.com',
       concierge-web:build:   port: 11000,
       concierge-web:build:   localAddress: undefined
       concierge-web:build: } 1

i'm not sure how to even begin troubleshooting this.

[brad-decker]

here is my cacheHandler.mjs file:

import { RedisStringsHandler } from '@trieb.work/nextjs-turbo-redis-cache';

let cachedHandler;

const REDIS_URL = process.env.REDIS_TLS_URL ?? process.env.REDIS_URL;

export default class CustomizedCacheHandler {
  constructor() {
    const socketOptions = REDIS_URL?.startsWith('rediss:')
      ? {
          tls: true,
          rejectUnauthorized: false,
        }
      : undefined;
    if (!cachedHandler) {
      cachedHandler = new RedisStringsHandler({
        redis_url: REDIS_URL,
        socketOptions,
        keyPrefix: 'concierge-web',
        sharedTaskKey: '__sharedTags__',
        revalidateTagQuerySize: 500,
        timeoutMs: 2_000,
        avgResyncIntervalMs: 60_000,
        redisGetDeduplication: false,
        inMemoryCachingTime: 0,
        defaultStaleAge: 1209600,
        estimateExpireAge: (staleAge) => staleAge * 2,
      });
    }
  }
  get(...args) {
    return cachedHandler.get(...args);
  }
  set(...args) {
    return cachedHandler.set(...args);
  }
  revalidateTag(...args) {
    return cachedHandler.revalidateTag(...args);
  }
  resetRequestCache(...args) {
    return cachedHandler.resetRequestCache(...args);
  }
}

[brad-decker]

The thing it didn't like was the .mjs extension.

I am getting these type of errors now:

       concierge-web:build: RedisStringsHandler.set() Error occurred while setting cache entry. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 5
       concierge-web:build: Failed to update prerender cache for dddbdcf7380c5051f122e4a67cdea1a7271fa4d95f17613884b2acd366e55bac [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready]
       concierge-web:build: RedisStringsHandler.get() Error occurred while getting cache entry. Returning null so site can continue to serve content while cache is disabled. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 6

that prevent the build from completing.

[brad-decker]

Got it to build by removing some components from the tree that apparently were taking a while to load.

Now the site won't render because of this:

2025-08-06T21:03:27.000000+00:00 app[heroku-redis]: source=REDIS addon=redis-fluffy-21237 sample#active-connections=22 sample#max-connections=398 sample#connection-percentage-used=0.05528 sample#load-avg-1m=0.01 sample#load-avg-5m=0.06 sample#load-avg-15m=0.1 sample#read-iops=7.3973 sample#write-iops=19.014 sample#max-iops=3000 sample#iops-percentage-used=0.00880 sample#memory-total=16070580kB sample#memory-free=12613908kB sample#memory-percentage-used=0.21509 sample#memory-cached=1180756kB sample#memory-redis=23932816bytes sample#hit-rate=0.17365 sample#evicted-keys=0
2025-08-06T21:04:02.139310+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=staging.conciergeauctions.com request_id=513800be-a605-941b-d255-7cbc7359fe85 fwd="50.24.26.51" dyno=web.1 connect=0ms service=30000ms status=503 bytes=567 protocol=http2.0 tls=true tls_version=tls1.3
2025-08-06T21:04:02.198289+00:00 app[web.1]: RedisStringsHandler.get() Error occurred while getting cache entry. Returning null so site can continue to serve content while cache is disabled. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 1
2025-08-06T21:04:03.179929+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=staging.conciergeauctions.com request_id=63701e00-b663-fc06-073c-a303c2141a4e fwd="50.24.26.51" dyno=web.1 connect=0ms service=7ms status=200 bytes=554 protocol=http2.0 tls=true tls_version=tls1.3
2025-08-06T21:04:07.646828+00:00 app[web.1]: RedisStringsHandler.set() Error occurred while setting cache entry. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 2
2025-08-06T21:04:07.647027+00:00 app[web.1]: Failed to update prerender cache for e4d06799c76abe654efcb3ec6d3b253d0e0737fa615442440d01184db9fc91e9 [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready]
2025-08-06T21:04:32.245707+00:00 app[web.1]: RedisStringsHandler.set() Error occurred while setting cache entry. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 3
2025-08-06T21:04:32.245955+00:00 app[web.1]: Failed to update prerender cache for e4d06799c76abe654efcb3ec6d3b253d0e0737fa615442440d01184db9fc91e9 [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready]

Current state of my cacheHandler:

// eslint-disable-next-line @typescript-eslint/no-var-requires
const { RedisStringsHandler } = require('@trieb.work/nextjs-turbo-redis-cache');

let cachedHandler;

const REDIS_URL = process.env.REDIS_TLS_URL ?? process.env.REDIS_URL;

module.exports = class CustomizedCacheHandler {
  constructor() {
    const socketOptions = REDIS_URL?.startsWith('rediss:')
      ? {
          tls: true,
          rejectUnauthorized: false,
        }
      : undefined;
    if (!cachedHandler) {
      cachedHandler = new RedisStringsHandler({
        redis_url: REDIS_URL,
        socketOptions,
        keyPrefix: 'concierge-web',
        sharedTaskKey: '__sharedTags__',
      });
    }
  }
  get(...args) {
    return cachedHandler.get(...args);
  }
  set(...args) {
    return cachedHandler.set(...args);
  }
  revalidateTag(...args) {
    return cachedHandler.revalidateTag(...args);
  }
  resetRequestCache(...args) {
    return cachedHandler.resetRequestCache(...args);
  }
};

This is as far as i can go with this at the moment. If you have suggestions please let me know.

[brad-decker]

Enabled debug and this is what I see:

2025-08-06T21:32:16.678212+00:00 app[web.1]: �[32m DEBUG CACHE HANDLER:  RedisStringsHandler.get() called with e4d06799c76abe654efcb3ec6d3b253d0e0737fa615442440d01184db9fc91e9 {
2025-08-06T21:32:16.678227+00:00 app[web.1]:   kind: 'FETCH',
2025-08-06T21:32:16.678227+00:00 app[web.1]:   revalidate: 600,
2025-08-06T21:32:16.678228+00:00 app[web.1]:   fetchUrl: 'https://graphql.contentful.com/content/v1/spaces/1307m41etaws/environments/staging',
2025-08-06T21:32:16.678230+00:00 app[web.1]:   fetchIdx: 1,
2025-08-06T21:32:16.678230+00:00 app[web.1]:   tags: [ 'homepage', 'pages' ],
2025-08-06T21:32:16.678231+00:00 app[web.1]:   softTags: [
2025-08-06T21:32:16.678231+00:00 app[web.1]:     '_N_T_/layout',
2025-08-06T21:32:16.678232+00:00 app[web.1]:     '_N_T_/(main)/layout',
2025-08-06T21:32:16.678232+00:00 app[web.1]:     '_N_T_/(main)/page',
2025-08-06T21:32:16.678233+00:00 app[web.1]:     '_N_T_/'
2025-08-06T21:32:16.678233+00:00 app[web.1]:   ]

Along with these:

2025-08-06T21:38:34.965664+00:00 app[web.1]: RedisStringsHandler.set() Error occurred while setting cache entry. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 24

[itekhi]

Hello!
Same thing here 😕

RedisStringsHandler.set() Error occurred while setting cache entry. The original error was: [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready] 32
Failed to update prerender cache for 4cf8d186685a6fd63f86e39c9ae4cd665a6225294fa0cfd3ff76ab739cd261cb [Error: assertClientIsReady: Timeout waiting for Redis maps to be ready]

Maybe it's an issue with redis server configuration? I'm running Redis v8.2.3 in Docker with:
redis-server --notify-keyspace-events Exe

Update:
Hmm, just to try, I removed a volume bind for redis' /data, it seems that doing that makes the error disappear....

(But now I have issues with Payload's live preview - on first load it's working, but after a single change, it exits the preview mode on it's own and doesn't work even after reloading the frame ;( Guys, if you know what this could be, or if you could at least point me in the right direction, that would be great 🙏🏻)

I also noticed that after recompiling (experimental-build-mode compile) and restarting the app (on start runs the generate command), I also need to restart Redis (clear it), or app just loses it - 404 on CSS and JS... :[

[JannikZed]

@itekhi can you tell us a bit more about your setup? So which next.js version you using etc?

Concerning the assertClientIsReady: Timeout waiting for Redis maps to be ready -> we faced the same issue from time to time in Google Cloud run as well. Really strange issue, where we suspect some underlying bugs in next.js or node.js networking stack. This just happened when new containers get started, so mostly on new deployments. Never happened for running containers. So we solved that with the setting of the cache handler: KILL_CONTAINER_ON_ERROR_THRESHOLD=30. That helped, as the container gets restarted automatically and cloud run started a new one that worked then.

[itekhi]

Hi @JannikZed

Node: v22.20.0

"react": "19.1.0",
"next": "15.4.4",
"payload": "3.52.0",
"@trieb.work/nextjs-turbo-redis-cache": "^1.8.1",
"redis": "^4.7.0",

I also noticed that this issue happens only when new containers get started...
Thanks for the setting, I will add it too.