# Kibana, Searchguard & X-Pack Mointoring **URL:** \ **Category:** Search Guard\ **Created:** [April 20, 2018, 5:47pm UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884 "2018-04-20T17:47:43Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Richard\_Laing](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Richard\_Laing](https://forum.search-guard.com/u/Richard_Laing)\ **Post date:** [April 20, 2018, 5:47pm UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/1 "2018-04-20T17:47:43Z")
When asking questions, please provide the following information: Hi there I would like to ask if anyone has seen the following error. - Search Guard and Elasticsearch version 6.2.2 - Installed and used enterprise modules, if any None - JVM version and operating system version The one that ships with the offical docker containers - Search Guard configuration files Default for now testing TLS setup and deployment - Elasticsearch log messages on debug level {“type”:“error”,“@timestamp”:“2018-04-20T17:41:45Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} {“type”:“error”,“@timestamp”:“2018-04-20T17:41:50Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} `` - Other installed Elasticsearch or Kibana plugins, if any X-Pack for monitoring only ---
**Author:** ![Bishwajit\_Samanta](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@Bishwajit\_Samanta](https://forum.search-guard.com/u/Bishwajit_Samanta)\ **Post date:** [April 21, 2018, 3:38pm UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/2 "2018-04-21T15:38:55Z")
Based on the error logs , I can understand that ssl is not allowed. So I guess we need to make some changes in elasticsearch.yml post that ssl may be resolved. > **···** > > On Fri 20 Apr, 2018, 23:17 , [richardlaing00@gmail.com](mailto:richardlaing00@gmail.com) wrote: > > > When asking questions, please provide the following information: > > > Hi there I would like to ask if anyone has seen the following error. > > > - Search Guard and Elasticsearch version > > > 6.2.2 > > > > > > - Installed and used enterprise modules, if any > > > None > > > - JVM version and operating system version > > > The one that ships with the offical docker containers > > > > > > - Search Guard configuration files > > > Default for now testing TLS setup and deployment > > > > > > - Elasticsearch log messages on debug level > > > {“type”:“error”,“@timestamp”:“2018-04-20T17:41:45Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > {“type”:“error”,“@timestamp”:“2018-04-20T17:41:50Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > > `` > > > > > > - Other installed Elasticsearch or Kibana plugins, if any > > > X-Pack for monitoring only > > > – > > > > You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group. > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard+unsubscribe@googlegroups.com](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto:search-guard@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/b7bba6bd-36b5-4570-8244-0f7d7682ec2e%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/b7bba6bd-36b5-4570-8244-0f7d7682ec2e%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\ **Post date:** [April 22, 2018, 11:45am UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/3 "2018-04-22T11:45:16Z")
Make sure you have disabled X-Pack security in kibana.yml ... xpack.security.enabled: false xpack.monitoring.enabled: true ... > **···** > > > Am 21.04.2018 um 17:38 schrieb Bishwajit Samanta \: > > > > Based on the error logs , I can understand that ssl is not allowed. So I guess we need to make some changes in elasticsearch.yml post that ssl may be resolved. > > > > On Fri 20 Apr, 2018, 23:17 , \ wrote: > > When asking questions, please provide the following information: > > > > Hi there I would like to ask if anyone has seen the following error. > > > > \* Search Guard and Elasticsearch version > > 6.2.2 > > > > \* Installed and used enterprise modules, if any > > None > > \* JVM version and operating system version > > The one that ships with the offical docker containers > > > > \* Search Guard configuration files > > Default for now testing TLS setup and deployment > > > > \* Elasticsearch log messages on debug level > > {"type":"error","@timestamp":"2018-04-20T17:41:45Z","tags":["fatal"],"pid":1,"level":"fatal","error":{"message":"child \"searchguard\" fails because [\"ssl\" is not allowed]","name":"ValidationError","stack":"ValidationError: child \"searchguard\" fails because [\"ssl\" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361"},"message":"child \"searchguard\" fails because [\"ssl\" is not allowed]"} > > {"type":"error","@timestamp":"2018-04-20T17:41:50Z","tags":["fatal"],"pid":1,"level":"fatal","error":{"message":"child \"searchguard\" fails because [\"ssl\" is not allowed]","name":"ValidationError","stack":"ValidationError: child \"searchguard\" fails because [\"ssl\" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361"},"message":"child \"searchguard\" fails because [\"ssl\" is not allowed]"} > > > > \* Other installed Elasticsearch or Kibana plugins, if any > > X-Pack for monitoring only > > > > -- > > You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com. > > To post to this group, send email to search-guard@googlegroups.com. > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/b7bba6bd-36b5-4570-8244-0f7d7682ec2e%40googlegroups.com\](https://groups.google.com/d/msgid/search-guard/b7bba6bd-36b5-4570-8244-0f7d7682ec2e%40googlegroups.com%5C). > > For more options, visit [https://groups.google.com/d/optout\](https://groups.google.com/d/optout%5C). > > > > -- > > You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com. > > To post to this group, send email to search-guard@googlegroups.com. > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/CAPkwwd0OHDGX7J2EYULZWM0hpAqs8tGAigWejwVR8jPHrc5B%2BA%40mail.gmail.com\](https://groups.google.com/d/msgid/search-guard/CAPkwwd0OHDGX7J2EYULZWM0hpAqs8tGAigWejwVR8jPHrc5B%2BA%40mail.gmail.com%5C). > > For more options, visit [https://groups.google.com/d/optout\](https://groups.google.com/d/optout%5C). ---
**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\ **Post date:** [April 22, 2018, 8:26pm UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/4 "2018-04-22T20:26:19Z")
Can you please post the contents of your kibana.yml. According to the error message: “message”:“child "searchguard" fails because ["ssl" is not allowed]”} It seems you have a configuration entry like: searchguard.ssl… in kibana.yml which is not valid. Make sure you do not confuse the settings in elasticsearch.yml with settings in kibana.yml. The error is thrown when Kibana is validating the kibana.yml configuration settings. > **···** > > On Friday, April 20, 2018 at 10:47:43 AM UTC-7, [richardlaing00@gmail.com](mailto:richardlaing00@gmail.com) wrote: > > > When asking questions, please provide the following information: > > > Hi there I would like to ask if anyone has seen the following error. > > > - Search Guard and Elasticsearch version > > > 6.2.2 > > > > > > - Installed and used enterprise modules, if any > > > None > > > - JVM version and operating system version > > > The one that ships with the offical docker containers > > > > > > - Search Guard configuration files > > > Default for now testing TLS setup and deployment > > > > > > - Elasticsearch log messages on debug level > > > {“type”:“error”,“@timestamp”:“2018-04-20T17:41:45Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > {“type”:“error”,“@timestamp”:“2018-04-20T17:41:50Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > > `` > > > > > > - Other installed Elasticsearch or Kibana plugins, if any > > > X-Pack for monitoring only ---
**Author:** ![Richard\_Laing](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Richard\_Laing](https://forum.search-guard.com/u/Richard_Laing)\ **Post date:** [April 23, 2018, 8:50am UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/5 "2018-04-23T08:50:11Z")
The following is my Kibana configuration > **···** > > On 22 April 2018 at 21:26, Jochen Kressin [jkressin@floragunn.com](mailto:jkressin@floragunn.com) wrote: > > > Can you please post the contents of your kibana.yml. According to the error message: > > > “message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > > > It seems you have a configuration entry like: > > > > > > searchguard.ssl… > > > > > > in kibana.yml which is not valid. Make sure you do not confuse the settings in elasticsearch.yml with settings in kibana.yml. The error is thrown when Kibana is validating the kibana.yml configuration settings. > > > > > > On Friday, April 20, 2018 at 10:47:43 AM UTC-7, [richardlaing00@gmail.com](mailto:richardlaing00@gmail.com) wrote: > > > > > When asking questions, please provide the following information: > > > > Hi there I would like to ask if anyone has seen the following error. > > > > - Search Guard and Elasticsearch version > > > > 6.2.2 > > > > > > > > - Installed and used enterprise modules, if any > > > > None > > > > - JVM version and operating system version > > > > The one that ships with the offical docker containers > > > > > > > > - Search Guard configuration files > > > > Default for now testing TLS setup and deployment > > > > > > > > - Elasticsearch log messages on debug level > > > > {“type”:“error”,“@timestamp”:“2018-04-20T17:41:45Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > > {“type”:“error”,“@timestamp”:“2018-04-20T17:41:50Z”,“tags”:[“fatal”],“pid”:1,“level”:“fatal”,“error”:{“message”:“child "searchguard" fails because ["ssl" is not allowed]”,“name”:“ValidationError”,“stack”:“ValidationError: child "searchguard" fails because ["ssl" is not allowed]\n at Object.exports.process (/usr/share/kibana/node\_modules/joi/lib/errors.js:181:19)\n at \_validateWithOptions (/usr/share/kibana/node\_modules/joi/lib/any.js:651:31)\n at root.validate (/usr/share/kibana/node\_modules/joi/lib/index.js:121:23)\n at Config.\_commit (/usr/share/kibana/src/server/config/config.js:119:35)\n at Config.set (/usr/share/kibana/src/server/config/config.js:89:10)\n at Config.extendSchema (/usr/share/kibana/src/server/config/config.js:62:10)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:22:12\n at next (native)\n at step (/usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:191)\n at /usr/share/kibana/src/plugin\_discovery/plugin\_config/extend\_config\_service.js:45:361”},“message”:“child "searchguard" fails because ["ssl" is not allowed]”} > > > > `` > > > > > > > > - Other installed Elasticsearch or Kibana plugins, if any > > > > X-Pack for monitoring only > > > – > > > > You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group. > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard+unsubscribe@googlegroups.com](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto:search-guard@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/d5b7c414-2b55-4f27-be16-dc22f80521d2%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/d5b7c414-2b55-4f27-be16-dc22f80521d2%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > – > > Yours R.Laing BSC Hons ---
**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\ **Post date:** [April 23, 2018, 2:05pm UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/6 "2018-04-23T14:05:23Z")
seems you mixed up elasticsearch.yml and kibana.yml There is no “searchguard.ssl.http.enabled” configuration in kibana.yml You need to define this in elasticsearch.yml Pls refer to the SG docs: [Security for Elasticsearch | Search Guard Documentation](https://docs.search-guard.com/latest/index) and the kibana docs: [Kibana User Guide [6.2] | Elastic](https://www.elastic.co/guide/en/kibana/6.2/index.html) > **···** > > On Monday, 23 April 2018 10:50:14 UTC+2, …ard Lai… wrote: > > > The following is my Kibana configuration > > > > xpack.security.enabled: false > > > xpack.monitoring.enabled: true > > > [server.name](http://server.name): kibana > > > server.host: “0” > > > elasticsearch.url: [https://XXX:9200](https://XXX:9200) > > > elasticsearch.username: “XXXXXX” > > > elasticsearch.password: “XXXXXX” > > > searchguard.ssl.http.enabled: true > > > elasticsearch.ssl.verificationMode: certificate ---
**Author:** ![Richard\_Laing](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Richard\_Laing](https://forum.search-guard.com/u/Richard_Laing)\ **Post date:** [April 23, 2018, 2:10pm UTC](https://forum.search-guard.com/t/kibana-searchguard-x-pack-mointoring/884/7 "2018-04-23T14:10:44Z")
Yeah i noticed that I have been reading up on your website and I have fixed my configuration as exampled by the configuration below, also I read a couple of posts around the user group so thanks for the help. #xpack settings xpack.security.enabled: false xpack.monitoring.enabled: true #elasticsearch settings elasticsearch.ssl.verificationMode: certificate elasticsearch.ssl.certificateAuthorities: /usr/share/kibana/config/certs/XXXXX elasticsearch.ssl.certificate: /usr/share/kibana/config/certs/XXXXX elasticsearch.ssl.key: /usr/share/kibana/config/certs/XXXXX elasticsearch.url: “[https://XXX:9200](https://XXX:9200)” elasticsearch.username: “XXXXX” elasticsearch.password: “XXXXX” elasticsearch.requestHeadersWhitelist: [“Authorization”, “x-forwarded-for”, “x-forwarded-by”, “x-proxy-user”, “x-proxy-roles”] #server settings server.name: kibana server.host: “0” server.ssl.supportedProtocols: - “TLSv1.2” `` > **···** > > On Monday, 23 April 2018 15:05:24 UTC+1, Search Guard wrote: > > > seems you mixed up elasticsearch.yml and kibana.yml > > > There is no “searchguard.ssl.http.enabled” configuration in kibana.yml > > > You need to define this in elasticsearch.yml > > > > > > Pls refer to the SG docs: [https://docs.search-guard.com/latest/index](https://docs.search-guard.com/latest/index) and the kibana docs: [https://www.elastic.co/guide/en/kibana/6.2/index.html](https://www.elastic.co/guide/en/kibana/6.2/index.html) > > > > On Monday, 23 April 2018 10:50:14 UTC+2, …ard Lai… wrote: > > > > > The following is my Kibana configuration > > > > > xpack.security.enabled: false > > > > xpack.monitoring.enabled: true > > > > [server.name](http://server.name): kibana > > > > server.host: “0” > > > > elasticsearch.url: [https://XXX:9200](https://XXX:9200) > > > > elasticsearch.username: “XXXXXX” > > > > elasticsearch.password: “XXXXXX” > > > > searchguard.ssl.http.enabled: true > > > > elasticsearch.ssl.verificationMode: certificate