# Getting wrong method GET for \_ssl/certificates ES 7.17
**URL:** https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811
**Category:** Elasticsearch
**Created:** [September 25, 2023, 9:24pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811 "2023-09-25T21:24:32Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Doc\_Kaos](https://discuss.elastic.co/u/Doc_Kaos)
#### Post date: [September 25, 2023, 9:24pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/1 "2023-09-25T21:24:33Z")
Has anyone seen this? It works fine on my 8.x clusters ...
```auto
# curl -X GET "localhost:9200/_ssl/certificates?pretty"
{
"error" : "Incorrect HTTP method for uri [/_ssl/certificates?pretty] and method [GET], allowed: [POST]",
"status" : 405
}
```
Documentation doesn't mention a "POST" at all [SSL certificate API | Elasticsearch Guide [7.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-api-ssl.html)
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [September 26, 2023, 2:13am UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/2 "2023-09-26T02:13:47Z")
Hi @Doc_Kaos Interesting...
Did you mean `https://localhost:9200...`
Do you have certs?
I run the following on my 7.17.13 and works
```auto
# GET /
{
"name" : "instance-0000000000",
"cluster_name" : "dsfgsdfg54a3fbc1e14cf595222d2",
"cluster_uuid" : "sfdsfdsfsdgdsfgd",
"version" : {
"number" : "7.17.13",
"build_flavor" : "default",
"build_type" : "docker",
"build_hash" : "2b211dbb8bfdecaf7f5b44d356bdfe54b1050c13",
"build_date" : "2023-08-31T17:33:19.958690787Z",
"build_snapshot" : false,
"lucene_version" : "8.11.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
# GET _ssl/certificates?pretty
[
{
"path" : "internal_tls_ca.crt",
"format" : "PEM",
"alias" : null,
"subject_dn" : "CN=elastic ce internal tls root",
"serial_number" : "1dfgdfg3c764f12",
"has_private_key" : false,
"expiry" : "2031-09-29T15:25:58.000Z"
}
```
---
### Author:  [@Doc\_Kaos](https://discuss.elastic.co/u/Doc_Kaos)
#### Post date: [September 26, 2023, 1:28pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/3 "2023-09-26T13:28:06Z")
That's what I was trying to check 😃 "Do I have any certs?" 😃
I can use Kibana dev tools to get the same thing as well. So if you have none, it responds with wrong method instead of an empty response?
---
### Author:  [@coezdemir](https://discuss.elastic.co/u/coezdemir)
#### Post date: [September 26, 2023, 1:36pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/4 "2023-09-26T13:36:54Z")
Hello,
I have checked this question on a http cluster with 7.x it responds with an empty list.
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [September 26, 2023, 1:45pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/5 "2023-09-26T13:45:07Z")
Same Here
```auto
hyperion:config sbrown$ curl http://localhost:9200/_ssl/certificates
[]
```
---
### Author:  [@Doc\_Kaos](https://discuss.elastic.co/u/Doc_Kaos)
#### Post date: [September 26, 2023, 3:26pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/6 "2023-09-26T15:26:04Z")
Weird. I'll try updating maybe:
```auto
"version" : {
"number" : "7.17.10",
"build_flavor" : "default",
"build_type" : "deb",
```
---
### Author:  [@Doc\_Kaos](https://discuss.elastic.co/u/Doc_Kaos)
#### Post date: [September 27, 2023, 9:55pm UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/7 "2023-09-27T21:55:15Z")
Discovered this happens if you have `transport.ssl` settings, but didn't enable `xpack.security` 😃
---
### Author:  [@TimV](https://discuss.elastic.co/u/TimV)
#### Post date: [September 29, 2023, 6:54am UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/8 "2023-09-29T06:54:17Z")
> [@Doc\_Kaos](#):
>
> Discovered this happens if you have `transport.ssl` settings, but didn't enable `xpack.security`
That's correct.
If security is not enabled then the `_ssl/certificates` API does not exist. and the error message you are getting is due to the fact that Elasticsearch thinks you're trying to create a document in the `_ssl` index.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 27, 2023, 6:54am UTC](https://discuss.elastic.co/t/getting-wrong-method-get-for-ssl-certificates-es-7-17/343811/9 "2023-10-27T06:54:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.