# Curator SSL problem/question

**URL:** https://discuss.elastic.co/t/curator-ssl-problem-question/47710
**Category:** Elasticsearch
**Created:** [April 18, 2016, 8:17pm UTC](https://discuss.elastic.co/t/curator-ssl-problem-question/47710 "2016-04-18T20:17:27Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![etienc](https://avatars.discourse-cdn.com/v4/letter/e/13edae/32.png) [@etienc](https://discuss.elastic.co/u/etienc)
#### Post date: [April 18, 2016, 8:17pm UTC](https://discuss.elastic.co/t/curator-ssl-problem-question/47710/1 "2016-04-18T20:17:28Z")

</div>

Hi all,

I'm using elastic-curator in a cron job to run automated tasks. My company's cron server is being migrated from CentOS 6 (python-elasticsearch-curator v 2.0.1) to CentOS 7 (elastic-curator v3.2.3)

I tried to update the commands to reflect new flags in v3.2.3, but having an issue with SSL. The following command works fine on the old CentOS 6 box:

`/usr/bin/curator --host myserver.com --port 8444 --ssl --auth 'user:password' close --prefix logstash- --older-than 10`

I updated the flags and ran the following command on the new CentOS 7 box:

`/usr/bin/curator --host myserver.com --port 8444 --use_ssl --http_auth user:password' show indices --prefix "logstash-" --older-than 3 --time-unit days --timestring '%Y.%m.%d'`

but get the following error:

> 2016-04-18 16:06:58,234 INFO Job starting: show indices  
> 2016-04-18 16:06:58,234 INFO Attempting to verify SSL certificate.  
> 2016-04-18 16:06:58,235 WARNING Unable to verify SSL certificate.  
> ERROR: Connection failure.

After using the --debug flag and doing a bit of research, I think this is happening because our site uses a self-signed cert. I tried to use `--ssl-no-validate`, but it doesn't recognize that flag, so it must only be available in v3.3+

Any suggestions?

---

<div class="post-metadata">

### Author: ![msimos](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@msimos](https://discuss.elastic.co/u/msimos)
#### Post date: [April 18, 2016, 9:44pm UTC](https://discuss.elastic.co/t/curator-ssl-problem-question/47710/2 "2016-04-18T21:44:05Z")

</div>

Curator 3.3 introduced the `--ssl-no-validate` flag. Your only choice is to either upgrade curator or don't use a self signed cert.

---

<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: [July 5, 2017, 10:58pm UTC](https://discuss.elastic.co/t/curator-ssl-problem-question/47710/3 "2017-07-05T22:58:21Z")

</div>