Hostname/IP does not match certificate's altnames

Elastic Stack Kibana
1

Hi there,
I am trying to enroll kibana with elasticsearch cluster.
Here is my deployment detail.

  1. I have deployed an Elasticsearch cluster on an EC2 instance using docker and, I am able to access it using the publicIP of the EC2.

  2. I am trying to run kibana in other EC2 instance in docker.
    So, when I am trying to connect to the Kibana, i am getting the following error:-

[2023-07-12T14:20:18.828+00:00][ERROR][plugins.interactiveSetup.elasticsearch] Failed to authenticate with host "https://ec2-44-200-137-40.compute-1.amazonaws.com:9200": Hostname/IP does not match certificate's altnames: Host: ec2-44-200-137-40.compute-1.amazonaws.com. is not in the cert's altnames: DNS:localhost, DNS:e3f66e0e6bf3, IP Address:FE80:0:0:0:F4B4:99FF:FE99:1B93, IP Address:172.17.0.2, IP Address:0:0:0:0:0:0:0:1, IP Address:127.0.0.1, IP Address:10.0.0.2, IP Address:FE80:0:0:0:70C4:12FF:FE38:73EA

Here is my kibana command: docker run -it -e ELASTICSEARCH_URL=https://ec2-44-200-137-40.compute-1.amazonaws.com:9200 -p 5601:5601 kibana:8.7.0

Can anyone please help me here. Which address should I provide in kibana?

Thanks in advance!

2

In your kibana command, perhaps you can use the public IP, which you said you can use to access the cluster.

Another thought is, you could add an entry to your local /etc/hosts file that maps e3f66e0e6bf3 to the IP. Then you could use e3f66e0e6bf3 as the IP since that seems to be a valid altname.

I'm not an expert here, so it might be normal for the IP to change and my advice wouldn't work. This might be a question for the AWS support staff, honestly.

3

I got the solution here, I just need to add --net=host in my command to map all the networking happening inside the docker container to the host.
Now it's working fine.
Thanks for taking out time to reply.

4

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