# Alert manager pod CrashLoopBackOff - No private IP address found, and explicit IP not provided

**URL:** https://discuss.kubernetes.io/t/alert-manager-pod-crashloopbackoff-no-private-ip-address-found-and-explicit-ip-not-provided/26181
**Category:** General Discussions
**Tags:** development, prometheus
**Created:** [November 23, 2023, 10:39am UTC](https://discuss.kubernetes.io/t/alert-manager-pod-crashloopbackoff-no-private-ip-address-found-and-explicit-ip-not-provided/26181 "2023-11-23T10:39:02Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Krishnendu](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/krishnendu/32/13715_2.png) [@Krishnendu](https://discuss.kubernetes.io/u/Krishnendu)
#### Post date: [November 23, 2023, 10:39am UTC](https://discuss.kubernetes.io/t/alert-manager-pod-crashloopbackoff-no-private-ip-address-found-and-explicit-ip-not-provided/26181/1 "2023-11-23T10:39:02Z")

</div>

When I deploy Prometheus on my AWS EKS cluster by using the helm chart, Prometheus is getting up. But the alert manager pod not getting up. It’s showing CrashLoopBackOff. Here are my pod logs below.

ts=2023-11-23T10:11:13.768Z caller=main.go:245 level=info msg=“Starting Alertmanager” version=“(version=0.26.0, branch=HEAD, revision=d7b4f0c7322e7151d6e3b1e31cbc15361e295d8d)”  
ts=2023-11-23T10:11:13.768Z caller=main.go:246 level=info build\_context=“(go=go1.20.7, platform=linux/amd64, user=root@df8d7debeef4, date=20230824-11:11:58, tags=netgo)”  
ts=2023-11-23T10:11:13.769Z caller=cluster.go:179 level=warn component=cluster err=“couldn’t deduce an advertise address: no private IP found, explicit advertise addr not provided”  
ts=2023-11-23T10:11:13.770Z caller=main.go:278 level=error msg=“unable to initialize gossip mesh” err=“create memberlist: Failed to get final advertise address: No private IP address found, and explicit IP not provided”

Also, I try to update the below custom value in values.yaml, although it’s not working.

```auto
alertmanager:
args:
- --cluster.advertise-address=0.0.0.0:9093

```

### Cluster information:

Kubernetes version: 1.28  
Cloud being used: AWS  
Installation method: EKS  
Host OS: AMAZON Linux 2  
CNI and version:  
CRI and version:

---

<div class="post-metadata">

### Author: ![Abdulsalam\_Abdulraza](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/abdulsalam_abdulraza/32/15579_2.png) [@Abdulsalam\_Abdulraza](https://discuss.kubernetes.io/u/Abdulsalam_Abdulraza)
#### Post date: [August 12, 2024, 5:42pm UTC](https://discuss.kubernetes.io/t/alert-manager-pod-crashloopbackoff-no-private-ip-address-found-and-explicit-ip-not-provided/26181/2 "2024-08-12T17:42:24Z")

</div>

Hello, please were you able to solve this?  
I’m currently facing this issue too, please how do I go about it?

---

<div class="post-metadata">

### Author: ![Kalyan\_P](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/kalyan_p/32/17047_2.png) [@Kalyan\_P](https://discuss.kubernetes.io/u/Kalyan_P)
#### Post date: [April 20, 2025, 1:03pm UTC](https://discuss.kubernetes.io/t/alert-manager-pod-crashloopbackoff-no-private-ip-address-found-and-explicit-ip-not-provided/26181/3 "2025-04-20T13:03:17Z")

</div>

which values.yaml ? i dont see any file with name values.yaml