> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/self-managed-enterprise-edition/troubleshooting-and-resources/troubleshooting/helm-install-failure.md).

# Helm installation failure

This topic provides solutions for installation problems related to Helm.

### Ingress-controller port already allocated <a href="#ingress-controller-port-already-allocated" id="ingress-controller-port-already-allocated"></a>

This error occurs when there is an attempt to deploy multiple `helm-charts` in the same cluster or when the `ingress-controller` service is already mapped to port 32500. For example:

```
# helm install harness-release ./ -n harness -f override.yaml <a href="#helm-install-harness-release-n-harness-f-overrideyaml" id="helm-install-harness-release-n-harness-f-overrideyaml"></a>
Error: INSTALLATION FAILED: Service "harness-ingress-controller" is invalid: spec.ports[0].nodePort: Invalid value: 32500: provided port is already allocated
```

The fix for this issue is included in `helm-charts` and is as follows:

* Set `.Values.global.ingress.nginx.httpNodePort` to 32501, or to any unused port.
* Set `.Values.global.ingress.nginx.httpsNodePort` to 32506, or to any unused port.

#### Example <a href="#example" id="example"></a>

```
global:
  nginx:
      controller:
        annotations: {}
      create: true
      httpNodePort: 32501
      httpsNodePort: 32506
```