---
title: "Known issues"
date: "2025-04-15T05:27:23+00:00"
summary: "Discover known issues with Node hosting, including limitations on importing custom builds and automatic artifact building."
image:
type: "page"
url: "/acquia-cloud-platform/add-ons/node-js/known-issues"
id: "2a19ed9a-c7a9-4753-9b2d-28ef52350846"
---

Unsupported configuration tabs
------------------------------

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.

![nodejs_unsupported-configuration-tab-proxy](https://acquia.widen.net/content/apv49kkrrh/web/1f54d_nodejs_unsupported-configuration-tab-proxy.png?w=480&v=f8cb182f-625f-4c50-a62c-570f19dbfa2a&itok=zXLNeEed)

Kubernetes readiness probe behavior
-----------------------------------

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.

### Path restrictions and health check failures

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`
    

### Required application change

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.

Unsupported package managers
----------------------------

The Front End Hosting Advanced platform supports only the `npm` package manager. Alternative package managers, such as `Yarn` or `pnpm`, are not supported.