React.JS / Next.JS application keeps getting 502 error which does NOT happen in our local developement environment

[khteh]

Describe the bug
Latest version of ALB. Don't spot any of the HTTPCode_ELB_502_Count, HTTPCode_Target_5XX_Count, elb_status_code and target_status_code in the logs. I am using SPDY and HTTP/2 backend protocol with default 60-second idle timeout. I have configured the following:

  server.on("connection", function(socket) {
    // Set the socket's idle timeout in milliseconds. 2 minutes is the default
    // for Node's HTTPS server. We are currently using SPDY:
    // https://nodejs.org/api/https.html#https_server_settimeout_msecs_callback
    socket.setTimeout(70000)
    socket.setKeepAlive(70000)

    // Wait for the timeout event. The socket will emit it when the idle timeout
    // elapses.
    socket.on("timeout", function() {
      // Call destroy again.
      socket.destroy();
    });
  });

Steps to reproduce

Expected outcome
A concise description of what you expected to happen.

Environment

• AWS Load Balancer controller version 2.4.6
• Kubernetes version v1.24.8-eks-ffeb93d
• Using EKS (yes/no), if so version? Yes v1.24.8-eks-ffeb93d

Additional Context:

[kishorj]

@khteh, could you verify if the target group targets are healthy?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[oliviassss]

@khteh, I'm closing this issue as for now, please feel free to reach out or reopen if you have any questions. Thanks