# Logstash- Unable to retrieve license information from license server

**URL:** <https://discuss.elastic.co/t/logstash-unable-to-retrieve-license-information-from-license-server/264979>\
**Category:** Logstash\
**Tags:** elastic-stack-monitoring, elastic-stack-security\
**Created:** [February 21, 2021, 11:57am UTC](https://discuss.elastic.co/t/logstash-unable-to-retrieve-license-information-from-license-server/264979 "2021-02-21T11:57:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [February 21, 2021, 6:59pm UTC](https://discuss.elastic.co/t/logstash-unable-to-retrieve-license-information-from-license-server/264979/4 "2021-02-21T18:59:22Z")

</div>

> [@anoopkv](#):
>
> xpack.monitoring.elasticsearch.ssl.verification\_mode

You are quoting the documentation for xpack.security.transport.ssl.verification\_mode. That has three options (full, certificate, none). As I understand it, xpack.monitoring.elasticsearch.ssl.verification\_mode has only two (certificate, which really means full, and none). And yes, folks are [aware](https://github.com/elastic/logstash/issues/9716) that this is confusing, but once you have made a less than perfect choice naming something it tends to be pretty hard to fix it without blowing up the installed base.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-unable-to-retrieve-license-information-from-license-server/264979)._