# Logstash and PKCS#12 format **URL:** \ **Category:** Logstash\ **Tags:** elastic-stack-security\ **Created:** [August 26, 2020, 6:07pm UTC](https://discuss.elastic.co/t/logstash-and-pkcs-12-format/246499 "2020-08-26T18:07:24Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ManuelF](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@ManuelF](https://discuss.elastic.co/u/ManuelF)\ **Post date:** [August 27, 2020, 8:05pm UTC](https://discuss.elastic.co/t/logstash-and-pkcs-12-format/246499/3 "2020-08-27T20:05:51Z")
## Update This [thread](https://discuss.elastic.co/t/certificates-and-keys-for-kibana-and-logstash-with-x-pack/150390/7) describes my issue as I'm having the same issue with the "CN=instance", but I am running Elasticsearch, Kibana and Logstash on the same machine, and users access Kibana by IP address (https://IP\_address:5601), so I don't have a FQDM. Logstash connects to Elasticsearch using `localhost` or `127.0.0.1` `xpack.monitoring.elasticsearch.hosts: ["https://127.0.0.1:9200"]` ``` elasticsearch { hosts => "https://127.0.0.1:9200" ``` What should I put after `--dns`? Should I use the IP address when generating the cert? ```auto bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12 --dns IP_address ``` Thank you --- _[View the full topic](https://discuss.elastic.co/t/logstash-and-pkcs-12-format/246499)._