# Metricbeat, MSSQL module, TLS Handshake failed unsupported protocol version 301

**URL:** <https://discuss.elastic.co/t/metricbeat-mssql-module-tls-handshake-failed-unsupported-protocol-version-301/332651>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [May 5, 2023, 1:11pm UTC](https://discuss.elastic.co/t/metricbeat-mssql-module-tls-handshake-failed-unsupported-protocol-version-301/332651 "2023-05-05T13:11:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)\
**Post date:** [May 5, 2023, 1:11pm UTC](https://discuss.elastic.co/t/metricbeat-mssql-module-tls-handshake-failed-unsupported-protocol-version-301/332651/1 "2023-05-05T13:11:21Z")

</div>

Hi, Im getting this error when remotly monitoring a MSSQL database:

`ERROR instance/beat.go:1014 Exiting: 2 errors: could not create connection to db: error doing ping to db: TLS Handshake failed: tls: server selected unsupported protocol version 301; could not create connection to db: error doing ping to db: TLS Handshake failed: tls: server selected unsupported protocol version 301`

how I can solve this?

if I install metricbeat directly to the host server of the db, will I get this error?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 2, 2023, 3:11pm UTC](https://discuss.elastic.co/t/metricbeat-mssql-module-tls-handshake-failed-unsupported-protocol-version-301/332651/2 "2023-06-02T15:11:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.