Node JS
Known issues
In the Cloud UI, the Configuration section for the environment displays the Operating System and Proxy tabs, but these features are not supported for the environment.
The Acquia Front End Hosting Advanced platform uses the root path (/) as the default Kubernetes readiness probe endpoint. This endpoint determines when an application is ready to receive traffic.
If your Node.js application enforces authentication, redirects, or strict access controls on the root path /, health check requests fail. For example, if the root endpoint challenges unauthenticated requests with a 401 Unauthorized response, Acquia Cloud platform treats the container as unhealthy and prevents it from serving traffic.
During code deployment, Front End Hosting Advanced platform performs these health checks by using specific user agents, such as:
kube-probe/1.31+
curl
To ensure successful container health verification, you must update your Node.js application logic or middleware configuration to bypass authentication checks specifically for health check requests. Ensure that requests that hit the / endpoint with the kube-probe or curl user agents bypass authentication and return a successful HTTP status code 200.
Because authentication setups vary based on your specific application architecture and framework, such as Express, NestJS, or Next.js, this page does not provide a specific code snippet. You must implement this bypass in the custom router or authentication middleware of the application. Failure to configure this bypass causes routing failures because Kubernetes continuously marks the container as unready.
The Front End Hosting Advanced platform supports only the npm package manager. Alternative package managers, such as Yarn or pnpm, are not supported.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Node JS