How to fix Error: ERR_TLS_SESSION_TICKET_APP_DISABLED in Node.js

What this error means

The ERR_TLS_SESSION_TICKET_APP_DISABLED error indicates that the Node.js TLS/HTTPS server has been configured to disable session tickets through the secureOptions parameter. Session tickets are a TLS extension that allows clients to resume previous sessions by storing encrypted session state on the client side, avoiding the need for server-side session caching. When a server disables session tickets using the SSL_OP_NO_TICKET flag, clients that attempt to use a previously issued session ticket will encounter this error because the server refuses to accept ticket-based resumption. This configuration is often intentional, used in scenarios where session ticket management becomes problematic (such as in clustered environments without shared ticket keys) or where security policies prohibit session tickets due to key rotation concerns.

Typical symptoms

• TLS/HTTPS connections fail with ERR_TLS_SESSION_TICKET_APP_DISABLED
• Session resumption attempts are rejected by the server
• Clients receive error when trying to use cached session tickets
• Performance degradation due to full handshakes on every connection
• Issue appears in clustered Node.js applications without shared ticket keys

Common causes

1. Server explicitly sets SSL_OP_NO_TICKET in secureOptions when creating TLS server
2. Application running in cluster mode without synchronized ticket keys across workers
3. Security policy requires disabling session tickets for key rotation control
4. Configuration intentionally disables tickets to avoid session state management complexity
5. Migration from single-server to multi-server setup without ticket key synchronization

How to fix "Error: ERR_TLS_SESSION_TICKET_APP_DISABLED"

const tls = require('tls');
const constants = require('node:constants');

// Check if SSL_OP_NO_TICKET is set
const server = tls.createServer({
  key: fs.readFileSync('server-key.pem'),
  cert: fs.readFileSync('server-cert.pem'),
  secureOptions: constants.SSL_OP_NO_TICKET  // <-- This disables tickets
}, (socket) => {
  console.log('server connected');
});

const tls = require('tls');
const fs = require('fs');

const server = tls.createServer({
  key: fs.readFileSync('server-key.pem'),
  cert: fs.readFileSync('server-cert.pem'),
  // Remove or don't set secureOptions with SSL_OP_NO_TICKET
}, (socket) => {
  console.log('server connected');
});

server.listen(8000, () => {
  console.log('TLS server listening on port 8000');
});

const cluster = require('cluster');
const tls = require('tls');
const crypto = require('crypto');
const fs = require('fs');

if (cluster.isMaster) {
  // Generate shared ticket keys (48 bytes)
  const ticketKeys = crypto.randomBytes(48);

  // Save to shared location or pass via IPC
  fs.writeFileSync('/tmp/ticket-keys.bin', ticketKeys);

  // Fork workers
  for (let i = 0; i < 4; i++) {
    cluster.fork();
  }
} else {
  // Workers read the shared keys
  const ticketKeys = fs.readFileSync('/tmp/ticket-keys.bin');

  const server = tls.createServer({
    key: fs.readFileSync('server-key.pem'),
    cert: fs.readFileSync('server-cert.pem'),
    ticketKeys: ticketKeys  // Share same keys across workers
  }, (socket) => {
    console.log('Worker', process.pid, 'accepted connection');
  });

  server.listen(8000);
}

const tls = require('tls');
const crypto = require('crypto');

const server = tls.createServer({
  key: fs.readFileSync('server-key.pem'),
  cert: fs.readFileSync('server-cert.pem'),
});

// Rotate keys every 24 hours
setInterval(() => {
  const newKeys = crypto.randomBytes(48);
  server.setTicketKeys(newKeys);
  console.log('Ticket keys rotated');
}, 24 * 60 * 60 * 1000);

server.listen(8000);

const tls = require('tls');

const server = tls.createServer({
  key: fs.readFileSync('server-key.pem'),
  cert: fs.readFileSync('server-cert.pem'),
  sessionTimeout: 300  // 5 minutes (in seconds)
}, (socket) => {
  console.log('Connection established');
});

server.listen(8000);

Advanced notes

Frequently asked questions

What does "ERR_TLS_SESSION_TICKET_APP_DISABLED" mean?

js TLS/HTTPS server has been configured to disable session tickets through the secureOptions parameter. Session tickets are a TLS extension that allows clients to resume previous sessions by storing encrypted session state on the client side, avoiding the need for server-side session caching. When a server disables session tickets using the SSL_OP_NO_TICKET flag, clients that attempt to use a previously issued session ticket will encounter this error because the server refuses to accept ticket-based resumption.

How do I fix "ERR_TLS_SESSION_TICKET_APP_DISABLED"?

This error occurs when a TLS client attempts to use session resumption via session tickets, but the server has explicitly disabled this feature through the SSL_OP_NO_TICKET flag. Session tickets are a performance optimization that allows clients to resume previous TLS sessions without a full handshake.

What causes "ERR_TLS_SESSION_TICKET_APP_DISABLED"?

Server explicitly sets SSL_OP_NO_TICKET in secureOptions when creating TLS server Application running in cluster mode without synchronized ticket keys across workers Security policy requires disabling session tickets for key rotation control

Is the "ERR_TLS_SESSION_TICKET_APP_DISABLED" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• TypeError: The URL argument must be a string or URL object

  The URL argument must be a string or URL object

  MEDIUM

• Error: UNSUPPORTED_PROTOCOL: TLS version mismatch (incompatible protocol versions)

  TLS Protocol Version Mismatch

  HIGH

• RangeError: util.inspect depth must be a non-negative integer

  RangeError: util.inspect depth must be a non-negative integer

  LOW

• Error: DH parameter is too small

  DH parameter is too small (Diffie-Hellman key too weak)

  HIGH

• Error: zlib error Z_DATA_ERROR (corrupted compressed data)

  Z_DATA_ERROR: Corrupted compressed data

  MEDIUM

• Error: Could not find package.json in current directory (npm module resolution)

  How to fix "Could not find package.json in current directory" in Node.js

  MEDIUM

Official resources & further reading

• 📚Node.js Official Documentation
• 📖
  Node.js TLS documentation - Session resumption(Official Docs)
• 🐙
  TLS session ticket extension not working in cluster(GitHub)
• 🐙
  tlsServer.setTicketKeys results in abort(GitHub)