# Godaddy SSL Wildcard Certificate

**URL:** <https://discuss.elastic.co/t/godaddy-ssl-wildcard-certificate/265503>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [February 25, 2021, 3:11pm UTC](https://discuss.elastic.co/t/godaddy-ssl-wildcard-certificate/265503 "2021-02-25T15:11:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![francescouk](https://avatars.discourse-cdn.com/v4/letter/f/7feea3/32.png) [@francescouk](https://discuss.elastic.co/u/francescouk)\
**Post date:** [February 25, 2021, 3:11pm UTC](https://discuss.elastic.co/t/godaddy-ssl-wildcard-certificate/265503/1 "2021-02-25T15:11:33Z")

</div>

Hello there, I´m trying to use my godaddy wildcard ssl on elk stack but for some reason is not working. Can someone point me to the right direction? Follow my config:

```auto
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.key: certs/server.key
xpack.security.transport.ssl.certificate: certs/server.crt
xpack.security.transport.ssl.certificate_authorities: ["certs/server_bundle-g2-g1.crt"]
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.key: certs/server.key
xpack.security.http.ssl.certificate: certs/server.crt
xpack.security.http.ssl.certificate_authorities: certs/server_bundle-g2-g1.crt

```

And this is the message I´m geeting:

```auto
[WARN][o.e.h.AbstractHttpServerTransport] [elk] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/192.168.10.1:9200, remoteAddress=/172.0.0.10:58625}
io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate

```

PS: When I donwload the certificate from godaddy, I receive this:  
93rfs8dhf834hts.crt  
93rfs8dhf834hts.pem  
gd\_bundle-g2-g1.crt  
gdig2.crt.pem

Cheers.

---

<div class="post-metadata">

**Author:** ![francescouk](https://avatars.discourse-cdn.com/v4/letter/f/7feea3/32.png) [@francescouk](https://discuss.elastic.co/u/francescouk)\
**Post date:** [February 27, 2021, 7:54pm UTC](https://discuss.elastic.co/t/godaddy-ssl-wildcard-certificate/265503/2 "2021-02-27T19:54:29Z")

</div>

@warkolm Can you please help me on that? It looks like the instructions for the certificate on elastic page focus only on self-certificate.

Thanks for the attention.

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [February 28, 2021, 11:52am UTC](https://discuss.elastic.co/t/godaddy-ssl-wildcard-certificate/265503/3 "2021-02-28T11:52:54Z")

</div>

Please don't ping people directly, these forums do not offer any guarantees or commitments. Please be patient in waiting for your answer.

> Received fatal alert: bad\_certificate

An `alert` in SSL terms is a message from the other side of the connection. A `fatal alert` means that the other party is going to terminate the connection.

In this case, the HTTP client at `remoteAddress=/172.0.0.10` is saying that it doesn't like your certificate.  
I can only guess why that is - the `bad_certificate` alert doesn't provide any specifics. There's a chance if you look at what is running on `172.0.0.10` there may be more detailed information in the logs.

If I had to guess, then I'd say that the client on that address is connecting to your node using an address (hostname/IP) that is not covered by your wildcard certificate.

---

<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:** [March 28, 2021, 11:53am UTC](https://discuss.elastic.co/t/godaddy-ssl-wildcard-certificate/265503/4 "2021-03-28T11:53:24Z")

</div>

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