# Linkerd\_app\_core::serve: Connection closed error=TLS

**URL:** <https://linkerd.buoyant.io/t/linkerd-app-core-connection-closed-error-tls/511>\
**Category:** Linkerd General Discussion\
**Tags:** ingress\
**Created:** [July 3, 2024, 6:58pm UTC](https://linkerd.buoyant.io/t/linkerd-app-core-connection-closed-error-tls/511 "2024-07-03T18:58:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lance](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/lance/32/186_2.png) [@lance](https://linkerd.buoyant.io/u/lance)\
**Post date:** [July 3, 2024, 6:58pm UTC](https://linkerd.buoyant.io/t/linkerd-app-core-connection-closed-error-tls/511/1 "2024-07-03T18:58:30Z")

</div>

We recently installed linkerd on our EKS production and staging clusters. All EKS logs are sent to Scalyr (now DataSet). There are a flood of logs coming from ingress containing

" INFO ThreadId(01) inbound: linkerd\_app\_core::serve: Connection closed error=TLS detection timed out client.addr=…"

We have tried various suggestions including attestations to namespaces, etc with no resolution. It would be great if linkerd had configuration settings to NOT check or report on issues like this. We get enough useful information from viz where this check or report isn’t necessary or helpful.

---

<div class="post-metadata">

**Author:** ![william](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/william/32/5_2.png) [@william](https://linkerd.buoyant.io/u/william)\
**Post date:** [July 10, 2024, 11:33pm UTC](https://linkerd.buoyant.io/t/linkerd-app-core-connection-closed-error-tls/511/2 "2024-07-10T23:33:29Z")

</div>

Thanks @lance. Please file a GitHub issue with these details so that the maintainers can evaluate lowering the log level of that specific message.