# Issue with registration of a test NTP Pool Agent version v4.1.4

**URL:** <https://community.ntppool.org/t/issue-with-registration-of-a-test-ntp-pool-agent-version-v4-1-4/4365>\
**Category:** Monitoring Operators\
**Tags:** monitoring, beta\
**Created:** [April 24, 2026, 8:51am UTC](https://community.ntppool.org/t/issue-with-registration-of-a-test-ntp-pool-agent-version-v4-1-4/4365 "2026-04-24T08:51:38Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\
**Post date:** [April 24, 2026, 3:56pm UTC](https://community.ntppool.org/t/issue-with-registration-of-a-test-ntp-pool-agent-version-v4-1-4/4365/7 "2026-04-24T15:56:05Z")

</div>

Maybe a new topic for the airport codes would be nice. I don’t think that mechanism has changed during this ongoing service move. Reading [this message](https://community.ntppool.org/t/beta-system-monitoring-testing/3875/43) first may be informative.

As for this test monitor, I now get:

level=ERROR msg=“could not get config, http error” env=test ip\_version=v4 err=“unavailable: tls: failed to verify certificate: x509: certificate is valid for localhost, ingress.local, not api.test.mon.ntppool.dev”

so something is still not quite working.

Edit: Additionally, api.test.mon.ntppool.dev has an IPv6 address as well but that seems to refuse connections.

---

_[View the full topic](https://community.ntppool.org/t/issue-with-registration-of-a-test-ntp-pool-agent-version-v4-1-4/4365)._