# Curator with Search Guard and SSL guide

**URL:** <https://forum.search-guard.com/t/curator-with-search-guard-and-ssl-guide/1054>\
**Category:** Search Guard\
**Created:** [August 2, 2018, 1:45pm UTC](https://forum.search-guard.com/t/curator-with-search-guard-and-ssl-guide/1054 "2018-08-02T13:45:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Woodbridge](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@James\_Woodbridge](https://forum.search-guard.com/u/James_Woodbridge)\
**Post date:** [August 2, 2018, 1:45pm UTC](https://forum.search-guard.com/t/curator-with-search-guard-and-ssl-guide/1054/1 "2018-08-02T13:45:01Z")

</div>

Hello,

I have successfully set up ELK stack with search guard, however when I try to use curator to manage indices I am unable to get it to connect.

I’m using Elasticsearch version 6.2.1 and SG version 6

My curator config is as follows:

> **···**
>
> * * *
> 
> # Remember, leave a key empty if there is no value. None will be a string,
> 
> # not a Python “NoneType”
> 
> client:  
> hosts:  
> - 127.0.0.1  
> port: 9200  
> url\_prefix:  
> use\_ssl: True  
> certificate: ‘C:\elastic\elasticsearch-6.2.1\config\cert\Star Financial Systems UAT ELK Certificate Authority.pem’  
> client\_cert: ‘C:\elastic\elasticsearch-6.2.1\config\cert\admin.sfs-uat.com.pem’  
> client\_key: ‘C:\elastic\elasticsearch-6.2.1\config\cert\key-admin.sfs-uat.com.pem’  
> ssl\_no\_validate: True  
> http\_auth:  
> timeout: 30  
> master\_only: False
> 
> logging:  
> loglevel: INFO  
> logfile: “F:/ElkStackLogs/curator.log”  
> logformat: default  
> blacklist:
> 
> ``
> 
> However when running curator, I encounter the following error:
> 
> urllib3.exceptions.NewConnectionError: \<urllib3.connection.VerifiedHTTPSConnection object at 0x00000080C3863C88\>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it
> 
> ``
> 
> If I change the URL to the internal IP of the Elasticsearch instance, 192.168.2.10, I receive this error instead:
> 
> urllib3.exceptions.SSLError: [SSL: UNKNOWN\_PROTOCOL] unknown protocol (\_ssl.c:833)
> 
> ``
> 
> Would somebody be able to point me in the direction of what I’m doing wrong? I’ve heard that maybe I have to configure roles for curator but I’m unsure what permissions they should have. Alternatively, if someone knows of a guide to setting up curator to work with SearchGuard it would be greatly appreciated.
> 
> Many Thanks,  
> James

---

<div class="post-metadata">

**Author:** ![Fabien\_Wernli](https://avatars.discourse-cdn.com/v4/letter/f/48db29/32.png) [@Fabien\_Wernli](https://forum.search-guard.com/u/Fabien_Wernli)\
**Post date:** [August 3, 2018, 1:40pm UTC](https://forum.search-guard.com/t/curator-with-search-guard-and-ssl-guide/1054/2 "2018-08-03T13:40:51Z")

</div>

Your config should work, but is probably unsecure:

1. you’d rather hit the FQDN of the elasticsearch node that matches the server’s certivicate’s CN and set ssl\_no\_validate to False
2. you should not use the admin certificate for curator: if there’s a bug, or the config is wrong, then curator could delete everything
3. you should therefore generate a specific certificate for curator, and add a role with sufficient permissions to do achieve what your actions.yaml contains

Now as for the reason your curator fails to connect:  
Can you successfully connect to elasticsearch using curl --key/–cert?
