# 404 error on retrieving metrics this morning

**URL:** <https://community.ntppool.org/t/404-error-on-retrieving-metrics-this-morning/4291>\
**Category:** Server operators\
**Created:** [March 16, 2026, 10:23am UTC](https://community.ntppool.org/t/404-error-on-retrieving-metrics-this-morning/4291 "2026-03-16T10:23:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [March 19, 2026, 8:32am UTC](https://community.ntppool.org/t/404-error-on-retrieving-metrics-this-morning/4291/6 "2026-03-19T08:32:22Z")

</div>

Sorry this took a minute. I upgraded the ingress in the old cluster (to an alpha version which in retrospect wasn’t a good idea) to get better logging which was helpful in finding pieces to migrate out of the old cluster. The new version of the ingress had a [subtle bug](https://github.com/jcmoraisjr/haproxy-ingress/issues/1432) when combining certain features.

I implemented a [work-around in the data api](https://gitea.develooper.com/ntppool/data-api/commit/bf27d87891f2dd6839632badb2092aa3f68e1606) to accept the /api/data paths instead of having the ingress rewrite them.

---

_[View the full topic](https://community.ntppool.org/t/404-error-on-retrieving-metrics-this-morning/4291)._