# SNMP Connecter Error **URL:** \ **Category:** Logstash\ **Tags:** docker\ **Created:** [May 22, 2024, 8:35am UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967 "2024-05-22T08:35:05Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![anguri\_sudhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anguri_sudhakar/32/50050_2.png) [@anguri\_sudhakar](https://discuss.elastic.co/u/anguri_sudhakar)\ **Post date:** [May 22, 2024, 8:35am UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/1 "2024-05-22T08:35:05Z")
Hello, I encountered after upgrading Docker\_elk-8.9.1 to Docker\_ELk\_8.13.1. I clone the latest version of ELK: Docker and Compose.]([GitHub - deviantony/docker-elk: The Elastic stack (ELK) powered by Docker and Compose.](https://github.com/deviantony/docker-elk)) Previously, I was using Docker version `docker_elk_8.9.1`, and the SNMP connector was functioning properly. However, after upgrading to `Docker_elk_8.13.1`, I started experiencing problems with the SNMP connector. The error message I received is as follows: `[plugins.actions.email] action execution failure: .email:10374bc1-f265-44ae-857e-a4a3edca345f: SNMP: error sending email: Client network socket disconnected before secure TLS connection was established` Note: I am not using SSL certification in My Pervious version . Now new versions well . Please suggest me anything i need to do in configuration ..? ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/9/b92cf053620630f3b44b6751e2410b2e9299f207.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/9/b92cf053620630f3b44b6751e2410b2e9299f207.png) Best regards, Sudhakar Anguri ---
**Author:** ![Sander\_Philipse](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sander_philipse/32/101890_2.png) [@Sander\_Philipse](https://discuss.elastic.co/u/Sander_Philipse)\ **Post date:** [May 22, 2024, 10:08am UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/2 "2024-05-22T10:08:36Z")
Hi @anguri_sudhakar, You probably need to set up TLS support for connectors, we have a guide to do that here: > **[Alerting and action settings in Kibana | Kibana Guide \[8.13\] | Elastic](https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html)** ---
**Author:** ![anguri\_sudhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anguri_sudhakar/32/50050_2.png) [@anguri\_sudhakar](https://discuss.elastic.co/u/anguri_sudhakar)\ **Post date:** [May 22, 2024, 2:39pm UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/3 "2024-05-22T14:39:54Z")
Thanks for update ,will try and let you know @Sander_Philipse🙂 ---
**Author:** ![Artem\_Shelkovnikov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_shelkovnikov/32/134322_2.png) [@Artem\_Shelkovnikov](https://discuss.elastic.co/u/Artem_Shelkovnikov)\ **Post date:** [May 22, 2024, 3:18pm UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/4 "2024-05-22T15:18:09Z")
It might make sense to ask it in the repository of the dockerfiles that you're using ([GitHub - deviantony/docker-elk: The Elastic stack (ELK) powered by Docker and Compose.](https://github.com/deviantony/docker-elk)) There might have been a breaking change in the network settings for the docker images, and some ports are not available any more / some traffic is not properly routed. Theoretically, you can also ssh into the image that's sending this error message and manually try `curl`'ing the URL used for emails and see what's actually going on. ---
**Author:** ![anguri\_sudhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anguri_sudhakar/32/50050_2.png) [@anguri\_sudhakar](https://discuss.elastic.co/u/anguri_sudhakar)\ **Post date:** [May 22, 2024, 3:35pm UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/5 "2024-05-22T15:35:52Z")
Let me give a try @Artem_Shelkovnikov will update ---
**Author:** ![anguri\_sudhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anguri_sudhakar/32/50050_2.png) [@anguri\_sudhakar](https://discuss.elastic.co/u/anguri_sudhakar)\ **Post date:** [May 22, 2024, 4:01pm UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/6 "2024-05-22T16:01:45Z")
> [@Artem\_Shelkovnikov](#): > > sending Hi @Artem_Shelkovnikov Its working inside docker container using CURL command and getting mail also: ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/a/5accf4e2fd5eb34d65016f802aeee8afde2ef1ff.png) ---
**Author:** ![anguri\_sudhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anguri_sudhakar/32/50050_2.png) [@anguri\_sudhakar](https://discuss.elastic.co/u/anguri_sudhakar)\ **Post date:** [May 24, 2024, 10:02am UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/7 "2024-05-24T10:02:16Z")
Hi @Sander_Philipse, We are using plain smtp server on 25 port . we added the below syntax in kibana.yml xpack.actions.customHostSettings: - url: smtp://xxxx.xxxxxx.xx.com:25 ssl: verificationMode: 'none' smtp: requireTLS: false but still not working Between Elastic and Kibana we have setup the TLS handshake as per ELK documentation. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 21, 2024, 10:03am UTC](https://discuss.elastic.co/t/snmp-connecter-error/359967/8 "2024-06-21T10:03:12Z")
Closed on June 21, 2024, 10:03am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.