I am currently running a Azure VM on which I have installed ElasticSearch, Kibana and Filebeat. The idea is to have a reporting/dashboarding capability for log files which are also stored on the same VM.
Installation of the VM and this part of the ELK stack has been successful. I have also configured the Azure connectivity so that the Kibana 5601 is accessible externally (or at least that's what I think ;)). When running a Azure diagnostics it shows a green light for the connectivity to the VMs IP adrress and 5601 port. I also believe I have I have configured the Elastic and Kibana config files the right way:
- For both Elastic Search and Kibana I am running version 7.6.2.
- Elastic has not been changed from the standard and shows a local host address.
- Kibana shows the 5601 port and public IP address that was given by the Azure Portal.
- Within Azure I have 'connected' the puplic IP address to the private IP address of the network adapter.
When I try to access Kibana through a RDP session on the VM's Chrome browser, all is fine. Obviously I use the local IP address and port within the RDP environment. When I try to log in on on an external device using the public IP address and Kibana port 5601 there is no connection.
Does anybody have an idea how to solve this issues, which seems to be connectivity related?