# Loki Ingester /ring Endpoint in Distributed Mode

**URL:** <https://community.grafana.com/t/loki-ingester-ring-endpoint-in-distributed-mode/140344>\
**Category:** Grafana Loki\
**Tags:** helm\
**Created:** [January 15, 2025, 6:10am UTC](https://community.grafana.com/t/loki-ingester-ring-endpoint-in-distributed-mode/140344 "2025-01-15T06:10:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vyongxin](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vyongxin](https://community.grafana.com/u/vyongxin)\
**Post date:** [January 15, 2025, 6:10am UTC](https://community.grafana.com/t/loki-ingester-ring-endpoint-in-distributed-mode/140344/1 "2025-01-15T06:10:00Z")

</div>

I’m currently trying to check the ingester ring status in my Loki setup via the `/ring` endpoint as documented. However, I’m encountering a **502 Bad Gateway** error when making a request to:  
`https://loki.domain.com/ring?tokens=false`  
While `https://loki.domain.com/distributor/ring?tokens=false` and `https://loki.domain.com/indexgateway/ring?tokens=false` work completely fine.

### Context:

- Loki is running in **scalable mode** with **zone-aware replication** enabled.
- The `/ring` endpoint configuration is dynamically set in the Loki Helm chart’s `_helpers.tpl` file. [loki/production/helm/loki/templates/\_helpers.tpl at main · grafana/loki · GitHub](https://github.com/grafana/loki/blob/main/production/helm/loki/templates/_helpers.tpl#L890-L893)

```auto
# Ring
location = /ring {
    proxy_pass {{ $ingesterUrl }}$request_uri;
}

```

The value of `$ingesterUrl` is defined in the Helm chart as:

```auto
{{- $ingesterUrl := printf "%s://%s.%s.svc.%s:%s" $httpSchema $ingesterHost .Release.Namespace .Values.global.clusterDomain (.Values.loki.server.http_listen_port | toString) }}

```

Accessing the `/ring` endpoint results in a **502 Bad Gateway** error:

- **Request URL:** `https://loki.domain.com/ring?tokens=false`
- **Status Code:** 502 Bad Gateway

I suspect the issue might be related to **zone-awareness** since replication is enabled. It’s possible that the `/ring` endpoint is not routing correctly to the ingester service or that additional configuration is required for zone-aware setups.

### Questions:

1. Are there additional configurations needed in the Helm chart or NGINX to make the `/ring` endpoint work?
2. Could the issue be due to a mismatch between `$ingesterUrl` and the actual ingester service URLs?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/grafana/original/2X/e/ef5308cc58c9e5a13187b5012eb99f406928462f.png) [@system](https://community.grafana.com/u/system)\
**Post date:** [January 15, 2026, 6:10am UTC](https://community.grafana.com/t/loki-ingester-ring-endpoint-in-distributed-mode/140344/2 "2026-01-15T06:10:29Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.