# Can I disable TLS 1.3 on HTTPS Load Balancer?

**URL:** <https://discuss.google.dev/t/can-i-disable-tls-1-3-on-https-load-balancer/98662>\
**Category:** Compute Infrastructure\
**Tags:** server-configuration\
**Created:** [December 13, 2022, 12:33am UTC](https://discuss.google.dev/t/can-i-disable-tls-1-3-on-https-load-balancer/98662 "2022-12-13T00:33:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![younghunyun](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/younghunyun/32/212_2.png) [@younghunyun](https://discuss.google.dev/u/younghunyun)\
**Post date:** [December 13, 2022, 12:33am UTC](https://discuss.google.dev/t/can-i-disable-tls-1-3-on-https-load-balancer/98662/1 "2022-12-13T00:33:05Z")

</div>

Hello

I checked the SSL policy in the frontend configuration of the HTTPS load balancer. When creating a new SSL policy instead of default, the minimum TLS version is selectable. There is no options to deny or disable TLS version.

 ![younghunyun_0-1670891275904.png](https://d2yds90mtvelsl.cloudfront.net/original/3X/9/0/9029570f7aacbab94af62df02cfa2d84df9a8df8.png)

The person currently developing the service is requesting that TLS 1.3 be disabled. Can I deny or disable TLS 1.3 on the GCP configuration? Or should I guide the persion that it is the client area that calls LB and it is not handling in GCP resource?

---

<div class="post-metadata">

**Author:** ![Marvin\_Lucero](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/marvin_lucero/32/212_2.png) [@Marvin\_Lucero](https://discuss.google.dev/u/Marvin_Lucero)\
**Post date:** [December 14, 2022, 4:41pm UTC](https://discuss.google.dev/t/can-i-disable-tls-1-3-on-https-load-balancer/98662/2 "2022-12-14T16:41:16Z")

</div>

Hi @younghunyun ,

TLS 1.3 is [enabled by default](https://cloud.google.com/blog/products/networking/tls-1-3-is-now-on-by-default-for-google-cloud-services#:~:text=TLS%201.3%20as%20the%20default%20for%20all%20new%20and%20existing%20Cloud%20CDN%20and%20Global%20Load%20Balancing%20customers) as part of Google Cloud’s improvement of Internet protocols. This is a feature and not an option that can be disabled or skipped when setting up SSL policies.

---

<div class="post-metadata">

**Author:** ![kumards](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/kumards/32/159905_2.png) [@kumards](https://discuss.google.dev/u/kumards)\
**Post date:** [December 14, 2022, 6:24pm UTC](https://discuss.google.dev/t/can-i-disable-tls-1-3-on-https-load-balancer/98662/3 "2022-12-14T18:24:58Z")

</div>

Hi @younghunyun ,

If the requirement to disable TLS 1.3 is because the clients of the app/service support only older SSL features, then choosing the COMPATIBLE profile for the SSL policy might be something that you can consider.

Relevant documentation: [https://cloud.google.com/load-balancing/docs/ssl-policies-concepts#defining\_an\_ssl\_policy](https://cloud.google.com/load-balancing/docs/ssl-policies-concepts#defining_an_ssl_policy)

 ![kumards_1-1671042253386.png](https://d2yds90mtvelsl.cloudfront.net/original/3X/8/f/8f77607344c7b1cdd4968c9b862f49571dc87c69.png)
