# How to disable TLS1.1 on Elastic Agent

**URL:** <https://discuss.elastic.co/t/how-to-disable-tls1-1-on-elastic-agent/363171>\
**Category:** Elastic Agent\
**Created:** [July 15, 2024, 4:02pm UTC](https://discuss.elastic.co/t/how-to-disable-tls1-1-on-elastic-agent/363171 "2024-07-15T16:02:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CCee](https://avatars.discourse-cdn.com/v4/letter/c/ac91a4/32.png) [@CCee](https://discuss.elastic.co/u/CCee)\
**Post date:** [July 15, 2024, 4:02pm UTC](https://discuss.elastic.co/t/how-to-disable-tls1-1-on-elastic-agent/363171/1 "2024-07-15T16:02:17Z")

</div>

We are trying to disable TLS 1.1 service on port 8220 for the Elastic Agent Fleet Server.  
The configuration file is as follows，I have three three different configuration methods but it is still not working.  
The `elastic-agent.yaml` is located at the default installation path `/opt/Elastic/Agent/elastic-agent.yaml` and version is 8.11.1.

```auto
fleet:
  ssl:
    supported_protocols: ["TLS1.2", "TLS1.3"]
---
fleet: 
  xxxx 
ssl:
  supported_protocols: ["TLS1.2", "TLS1.3"]
---
fleet:
  kibana:
    ssl.supported_protocols: ["TLS1.2", "TLS1.3"]

```

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [July 15, 2024, 4:30pm UTC](https://discuss.elastic.co/t/how-to-disable-tls1-1-on-elastic-agent/363171/2 "2024-07-15T16:30:23Z")

</div>

Check this answer for a similar post: [TLS1.1 disable in Fleet Server - #2 by leandrojmp](https://discuss.elastic.co/t/tls1-1-disable-in-fleet-server/361245/2)

You need to use `server.ssl` instead of just `ssl`.

---

<div class="post-metadata">

**Author:** ![CCee](https://avatars.discourse-cdn.com/v4/letter/c/ac91a4/32.png) [@CCee](https://discuss.elastic.co/u/CCee)\
**Post date:** [July 15, 2024, 5:27pm UTC](https://discuss.elastic.co/t/how-to-disable-tls1-1-on-elastic-agent/363171/3 "2024-07-15T17:27:15Z")

</div>

Thank you very much for your assistance. The issue has been resolved.