# Unable to attache pdf report

**URL:** <https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [September 15, 2016, 12:38pm UTC](https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605 "2016-09-15T12:38:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![theo.bot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theo.bot/32/5739_2.png) [@theo.bot](https://discuss.elastic.co/u/theo.bot)\
**Post date:** [September 15, 2016, 12:38pm UTC](https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605/1 "2016-09-15T12:38:49Z")

</div>

Hi

I am try-ing to send a pdf using the watch I get the following message:

Unable to get attachment of type [http] with id [dash\_report.pdf] in watch [dash\_report] aborting watch execution

I used the following watcher:

{  
"trigger" : {  
"schedule": {  
"interval": "10m"  
}  
},  
"actions" : {  
"email\_admin" : {  
"email": {  
"to": "'Recipient Name [foo@bar.com](mailto:foo@bar.com)'",  
"subject": "Dashboard Monitoring Report",  
"attachments" : {  
"dash\_report.pdf" : {  
"http" : {  
"content\_type" : "application/pdf",  
"request" : {  
"method": "POST",  
"headers": {  
"kbn-xsrf": "reporting"  
},  
"auth": {  
"basic": {  
"username": "elkuser",  
"password": "secret"  
}  
},  
"read\_timeout": "300s",  
"url":  
"[https://0.0.0.0:5601/api/reporting/generate/dashboard/dashboard?\_g=(time:(from:now-1d%2Fd,mode:quick,to:now)](https://0.0.0.0:5601/api/reporting/generate/dashboard/dashboard?_g=(time:(from:now-1d%2Fd,mode:quick,to:now)))&sync"  
}  
}  
}  
}  
}  
}  
}  
}

Any suggestions?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 15, 2016, 12:59pm UTC](https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605/2 "2016-09-15T12:59:12Z")

</div>

Heya,

can you check the log files, if there is more information, like the HTTP response status code?

--Alex

---

<div class="post-metadata">

**Author:** ![theo.bot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theo.bot/32/5739_2.png) [@theo.bot](https://discuss.elastic.co/u/theo.bot)\
**Post date:** [September 15, 2016, 1:39pm UTC](https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605/3 "2016-09-15T13:39:15Z")

</div>

Hey Alex,

I checked the logs. Indeed it struggles over the URL. Kibana is using ssl. However it uses a self-signed certificate. Is there a way to tell watcher it should not verify the verify the certificate?

Theo

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 16, 2016, 8:49am UTC](https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605/4 "2016-09-16T08:49:24Z")

</div>

Hey,

you can import that certificate into a truststore that is used by watcher. Run

```auto
keytool -importcert -keystore watcher-truststore.jks -file server.crt

```

And then specify the truststore in your `elasticsearch.yml` file

```auto
watcher.http.ssl.truststore.path: /path/to/elasticsearch/config/watcher-truststore.jks

```

--Alex

---

<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 6, 2017, 1:42pm UTC](https://discuss.elastic.co/t/unable-to-attache-pdf-report/60605/5 "2017-07-06T13:42:50Z")

</div>