---
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/f8cb182f-625f-4c50-a62c-570f19dbfa2a/web/1f54d_nodejs_unsupported-configuration-tab-proxy.png?w=480&itok=zXLNeEed)

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

The Acquia Front End Hosting Advanced platform typically uses the root path (`/`) as the Kubernetes readiness probe endpoint. This endpoint determines when the application is ready to receive traffic.

If the application enforces authentication, redirects, or access controls on the root path, you must configure a bypass. The bypass ensures that health check requests can access the path without authentication and receive a successful HTTP response (200–399). If a bypass is not configured, the platform may treat the container as unhealthy and prevent it from serving traffic.