# Kibana HTTPS - Impossible to use verification mode "full" for docker services? **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [March 24, 2020, 9:14pm UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917 "2020-03-24T21:14:37Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![J7mbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/j7mbo/32/64999_2.png) [@J7mbo](https://discuss.elastic.co/u/J7mbo)\ **Post date:** [March 24, 2020, 9:14pm UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/1 "2020-03-24T21:14:37Z")
Docker services use their internal DNS to resolve "elasticsearch", so I can point kibana at "[https://elasticsearch:9200](https://elasticsearch:9200)". The problem is, I have to set verification mode to "certificate" because the https certificate is for my domain, not for "elasticsearch". I googled "subject alternative names" and it doesn't look like I can generate a certificate (I'm using letsencrypt) for "elasticsearch" - because anyone could do that! So, if I'm using docker, and dns resolution is via docker, **must we always use certificate instead of full**? Or is there something else I'm missing? ---
**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\ **Post date:** [March 25, 2020, 7:38am UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/2 "2020-03-25T07:38:10Z")
It seems so. As I can see, it's the recommended way to use self-signed certificates [https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-tls-docker.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-tls-docker.html) ---
**Author:** ![J7mbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/j7mbo/32/64999_2.png) [@J7mbo](https://discuss.elastic.co/u/J7mbo)\ **Post date:** [March 25, 2020, 8:13am UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/3 "2020-03-25T08:13:09Z")
Is it possible to use both a real certificate + key so it resolves to a public domain name, and a self-signed certificate + key with CA that signed it (as the docs show), so that I can have the best of both worlds? Publicly I would be able to visit this on https by it's domain name, and then Kibana could use full verification mode when talking to Elasticsearch internally within docker. ---
**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\ **Post date:** [March 25, 2020, 9:37am UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/4 "2020-03-25T09:37:24Z")
Yes, you can configure `server.ssl` with your real cert and use a self-signed cert for `elasticsearch.ssl`. Would it work for you? ---
**Author:** ![J7mbo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/j7mbo/32/64999_2.png) [@J7mbo](https://discuss.elastic.co/u/J7mbo)\ **Post date:** [March 25, 2020, 9:45am UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/5 "2020-03-25T09:45:08Z")
I'm not sure. If I add: **verificationmode** and **authorities** , wouldn't these options be for everything? What would the config look like having both: - verification mode "full" with no authorities (for the real cert) - verification mode "certificate" with the self-signing authority (for the self-signed cert) - specifying separate key + cert pem paths for both I'm not sure how I can do that with the config. ---
**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\ **Post date:** [March 25, 2020, 12:32pm UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/6 "2020-03-25T12:32:38Z")
> If I add: **verificationmode** and **authorities** , wouldn't these options be for everything? no, `server.ssl` and `elasticsearch.ssl` are different config options. You cannot set `verificationmode` for server.ssl and have to use "real" certificate: > server.ssl.enabled: true > server.ssl.key: ... > server.ssl.certificate: ... > server.ssl. certificateAuthorities: ... you can use self-signed certificate for `elasticsearch.ssl` tho: > elasticsearch.ssl.certificateAuthorities: ... > elasticsearch.ssl.verificationMode: "certificate" ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 22, 2020, 12:32pm UTC](https://discuss.elastic.co/t/kibana-https-impossible-to-use-verification-mode-full-for-docker-services/224917/7 "2020-04-22T12:32:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.