# Issue with SSL when importing data but fine in browser

**URL:** <https://discuss.elastic.co/t/issue-with-ssl-when-importing-data-but-fine-in-browser/341008>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [August 17, 2023, 11:57am UTC](https://discuss.elastic.co/t/issue-with-ssl-when-importing-data-but-fine-in-browser/341008 "2023-08-17T11:57:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nick\_harper1](https://avatars.discourse-cdn.com/v4/letter/n/c37758/32.png) [@nick\_harper1](https://discuss.elastic.co/u/nick_harper1)\
**Post date:** [August 17, 2023, 11:57am UTC](https://discuss.elastic.co/t/issue-with-ssl-when-importing-data-but-fine-in-browser/341008/1 "2023-08-17T11:57:05Z")

</div>

I have setup an SSL from a local CA which is working fine when I try to view in the browser from the server I am pushing data from but when trying to push data I get the following error on the server:

[2023-08-17T12:40:52,332][WARN][o.e.h.AbstractHttpServerTransport] [servername] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/"localip":9200, remoteAddress=/"remoteip":28343}  
io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad\_certificate

Is this trying to use the "transport" SSL rather than HTTP?

xpack.security.transport.ssl is using the self assigned certs/transport.p12 but xpack.security.http.ssl.key is using my actual SSL which works in the browser.

When I try to use my SSL for transport it stops the cluster from working.

---

<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:** [September 14, 2023, 11:57am UTC](https://discuss.elastic.co/t/issue-with-ssl-when-importing-data-but-fine-in-browser/341008/2 "2023-09-14T11:57:33Z")

</div>

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