# Calls to .well-known every 5 seconds for more than 24 hours **URL:** \ **Category:** Help\ **Created:** [April 4, 2019, 6:43pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378 "2019-04-04T18:43:43Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bbzg](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@bbzg](https://community.letsencrypt.org/u/bbzg)\ **Post date:** [April 4, 2019, 6:43pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/1 "2019-04-04T18:43:44Z")
I am receiving calls to .well-known every 5 seconds and have been for the last 24 hours. The requests look like this: “GET [https://x.y.z/.well-known/acme-challenge/redacted](https://x.y.z/.well-known/acme-challenge/redacted)” 403 554 “Go-http-client/2.0” And as you can see the request is routed to my default pod which is a Java Spring server that responds with 403 Forbidden. How can I stop these requests from being made? Thank you! My domain is: Will disclose later if absolutely necessary I ran this command: Kubernetes cluster with cert-manager (currently uninstalled) My hosting provider, if applicable, is: Google/GKE I can login to a root shell on my machine (yes or no, or I don’t know): Yes I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No The version of my client is: Was cert-manger 0.2.5 but currently uninstalled When this is resolved I intend to use 0.7.0 ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 4, 2019, 6:48pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/2 "2019-04-04T18:48:13Z")
Hi @bbzg > [@bbzg](#): > > How can I stop these requests from being made? what ip address creates these requests? ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [April 4, 2019, 6:57pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/3 "2019-04-04T18:57:28Z")
👋 Hi @bbzg, welcome to the community forum. > [@bbzg](#): > > Was cert-manger 0.2.5 but currently uninstalled > When this is resolved I intend to use 0.7.0 We have seen lots of bugs that end up generating excessive traffic to our ACME server from this version of cert-manager. Are you 100% sure it is fully uninstalled? The ACME server wouldn't be making HTTP-01 validation requests without an ACME client POSTing challenges. Can you share your domain name? It would make it possible for me to check the server-side logs to see what user agent is initiating the challenges to confirm whether it is cert-manager. ---
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [April 4, 2019, 7:09pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/4 "2019-04-04T19:09:15Z")
> [@bbzg](#): > > Go-http-client/2.0 If it's just using a generic Go user-agent, it's not the Let's Encrypt validation servers. Plus it's using HTTPS -- if it was from Let's Encrypt, there would be an equal number of HTTP requests as well. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [April 4, 2019, 7:10pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/5 "2019-04-04T19:10:59Z")
> [@mnordhoff](#): > > If it’s just using a generic Go user-agent, it’s not the Let’s Encrypt validation servers. Good point! Maybe its a self-check from certmanager? ---
**Author:** ![bbzg](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@bbzg](https://community.letsencrypt.org/u/bbzg)\ **Post date:** [April 5, 2019, 6:14pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/6 "2019-04-05T18:14:16Z")
Thanks for the help guys \<3, I tracked it down to a misconfiguration in another cluster that had been configured with faulty subdomain. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [May 5, 2019, 6:14pm UTC](https://community.letsencrypt.org/t/calls-to-well-known-every-5-seconds-for-more-than-24-hours/90378/7 "2019-05-05T18:14:17Z")
Closed on May 5, 2019, 6:14pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.