# Lumberjack input needs to support specifying a certificate chain for ssl
**URL:** https://discuss.elastic.co/t/lumberjack-input-needs-to-support-specifying-a-certificate-chain-for-ssl/30048
**Category:** Logstash
**Created:** [September 26, 2015, 1:57am UTC](https://discuss.elastic.co/t/lumberjack-input-needs-to-support-specifying-a-certificate-chain-for-ssl/30048 "2015-09-26T01:57:02Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@nneul](https://discuss.elastic.co/u/nneul)
#### Post date: [September 26, 2015, 1:57am UTC](https://discuss.elastic.co/t/lumberjack-input-needs-to-support-specifying-a-certificate-chain-for-ssl/30048/1 "2015-09-26T01:57:02Z")
You should allow specifying path to a certificate chain. Pointing ssl\_certificate at crt and intermediates does not work - it just grabs the first entry only.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [September 26, 2015, 9:25am UTC](https://discuss.elastic.co/t/lumberjack-input-needs-to-support-specifying-a-certificate-chain-for-ssl/30048/2 "2015-09-26T09:25:53Z")
This sounds like a genuine bug report in which case you're likely to get better traction if you file a bug here: [https://github.com/logstash-plugins/logstash-input-lumberjack/issues/new](https://github.com/logstash-plugins/logstash-input-lumberjack/issues/new)
I wonder if what you're talking about touches upon what's going to be addressed in the context of [github.com/logstash-plugins/logstash-input-lumberjack issue #31](https://github.com/logstash-plugins/logstash-input-lumberjack/issues/31).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:27am UTC](https://discuss.elastic.co/t/lumberjack-input-needs-to-support-specifying-a-certificate-chain-for-ssl/30048/3 "2017-07-06T05:27:58Z")