# Cannot SIGHUP Kibana with SSL enabled

**URL:** <https://discuss.elastic.co/t/cannot-sighup-kibana-with-ssl-enabled/86156>\
**Category:** Kibana\
**Created:** [May 17, 2017, 5:56pm UTC](https://discuss.elastic.co/t/cannot-sighup-kibana-with-ssl-enabled/86156 "2017-05-17T17:56:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 17, 2017, 5:56pm UTC](https://discuss.elastic.co/t/cannot-sighup-kibana-with-ssl-enabled/86156/1 "2017-05-17T17:56:38Z")

</div>

I have SSL enabled in kibana using "server.ssl.cert: /etc/opt/zookeeper/kafkapoc.pem" (and the associated key is also set). This works just fine and uses SSL. However, I just configured logrotate and when I send SIGHUP to the kibana process it logs that it is going to reconfigure logging and then exits

/usr/share/kibana/src/server/config/config.js:116  
throw results.error;  
^

ValidationError: child "server" fails because [child "ssl" fails because ["cert" is not allowed]]  
at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:140:17)  
at internals.Any.\_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:649:25)  
at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:102:23)  
at Config.\_commit (/usr/share/kibana/src/server/config/config.js:113:35)  
at Config.set (/usr/share/kibana/src/server/config/config.js:84:10)  
at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:57:10)

I can change logrotate to do stop/start to workaround this. I recently installed xpack and told it not to enable security (since I already had SSL enabled in my whole ELK / kafka / zookeeper environment. I am not sure if this happens without xpack. Anyways it seems wrong that restart does validation not done on startup.

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [May 17, 2017, 6:10pm UTC](https://discuss.elastic.co/t/cannot-sighup-kibana-with-ssl-enabled/86156/2 "2017-05-17T18:10:22Z")

</div>

@Badger this is caused because of a bug being tracked [here](https://github.com/elastic/kibana/issues/11740). For the time being I'd recommend using `elasticsearch.ssl.certificate` if you'd like to use SIGHUP to restart the kibana process.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 17, 2017, 7:16pm UTC](https://discuss.elastic.co/t/cannot-sighup-kibana-with-ssl-enabled/86156/3 "2017-05-17T19:16:03Z")

</div>

That would be server.ssl.certificate, but yes, that fixes the problem. Thanks!

---

<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:** [June 14, 2017, 7:16pm UTC](https://discuss.elastic.co/t/cannot-sighup-kibana-with-ssl-enabled/86156/4 "2017-06-14T19:16:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.