# Installing ELK on a new Linux box on Azure **URL:** \ **Category:** Elasticsearch\ **Created:** [January 20, 2017, 6:20pm UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319 "2017-01-20T18:20:11Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Maurgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maurgi/32/14778_2.png) [@Maurgi](https://discuss.elastic.co/u/Maurgi)\ **Post date:** [January 20, 2017, 6:20pm UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/1 "2017-01-20T18:20:11Z")
I am a Linux n00b, sorry, but I am trying 🙂 What do I need to do to access Kibana from the another machine once I deploy to Linux? Problem: I just provisioned a new Ubuntu Linux box on Azure and installed Elastic search + Kibana. I followed the steps here: [https://www.elastic.co/start](https://www.elastic.co/start) But used the debian packages, so I started elasticsearch and kibana as services - There was no message when I launched 'sudo service kibana start' so I assume the service started correctly. Now the final steps says to open a browser and go [http://localhost:5601](http://localhost:5601), but of course I cannot do that on a SSH session, so I tried: http://"my Linux box IP":5601 from my PC, but no luck, the request times out. The firewall is not active I think, but I also tried to activate it and open port 5601 without luck. Any hint? Thx, Mauro. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 21, 2017, 8:01am UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/2 "2017-01-21T08:01:06Z")
You need to change `server.host` - [https://www.elastic.co/guide/en/kibana/current/settings.html](https://www.elastic.co/guide/en/kibana/current/settings.html) ---
**Author:** ![Maurgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maurgi/32/14778_2.png) [@Maurgi](https://discuss.elastic.co/u/Maurgi)\ **Post date:** [January 22, 2017, 1:46am UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/3 "2017-01-22T01:46:14Z")
I set it to 0.0.0.0 and then to the public IP address, but did not work. The connection timed out. ---
**Author:** ![Maurgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maurgi/32/14778_2.png) [@Maurgi](https://discuss.elastic.co/u/Maurgi)\ **Post date:** [January 22, 2017, 2:14am UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/4 "2017-01-22T02:14:30Z")
So elasticsearch seems started but I can't tell because of security? ```auto wget localhost:9200 --2017-01-22 02:12:41-- http://localhost:9200/ Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:9200... connected. HTTP request sent, awaiting response... 401 Unauthorized Username/Password Authentication Failed. ``` This is the kibana.yml: ```auto server.port: 5601 server.host: 40.112.217.143 ``` If I try to launch kibana I get the following: ```auto sudo /usr/share/kibana/bin/kibana log [02:14:10.150] [fatal] Error: listen EADDRNOTAVAIL 40.112.217.143:5601 at Object.exports._errnoException (util.js:1026:11) at exports._exceptionWithHostPort (util.js:1049:20) at Server._listen2 (net.js:1244:19) at listen (net.js:1293:10) at net.js:1403:9 at _combinedTickCallback (internal/process/next_tick.js:77:11) at process._tickCallback (internal/process/next_tick.js:98:9) FATAL { Error: listen EADDRNOTAVAIL 40.112.217.143:5601 at Object.exports._errnoException (util.js:1026:11) at exports._exceptionWithHostPort (util.js:1049:20) at Server._listen2 (net.js:1244:19) at listen (net.js:1293:10) ``` If I change the address to 127.0.0.1, then kibana starts and I can access it locally (wget gives me access denied but it connects), but I cannot connect to it remotely. Which address should I use? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 22, 2017, 3:15am UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/5 "2017-01-22T03:15:35Z")
Did you install X-Pack? > [@Maurgi](#): > > [02:14:10.150] [fatal] Error: listen EADDRNOTAVAIL 40.112.217.143:5601 Is that an IP attached to an interface on the host? ---
**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\ **Post date:** [January 23, 2017, 12:47pm UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/6 "2017-01-23T12:47:27Z")
I know this doesn't directly answer your question, but did you check out [our ARM template for installing Elasticsearch with Kibana on Azure](https://github.com/elastic/azure-marketplace)? The template is able to install an Elasticsearch cluster in a number of different topologies, complete with Kibana. Deploying from the command line with the Azure CLI (cross-platform) is as simple as ```auto # login to azure azure login # switch CLI to ARM mode azure config mode arm # create a resource group azure group create "" "" # specify a parameters.json file with the parameters and deploy the cluster using template and parameters azure group deployment create --template-uri https://raw.githubusercontent.com/elastic/azure-marketplace/master/src/mainTemplate.json --parameters-file parameters/password.parameters.json -g "" ``` It might save you a lot of time in configuring all of the resources required on Azure yourself (unless of course the aim is to become more acquainted with Azure resources 😄). ---
**Author:** ![Maurgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maurgi/32/14778_2.png) [@Maurgi](https://discuss.elastic.co/u/Maurgi)\ **Post date:** [January 24, 2017, 5:35pm UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/7 "2017-01-24T17:35:55Z")
I think the problem is that the IP is not addressable, the host only sees `10.0.0.XYZ` I think I need to configure a public IP on the Azure VM, but I am not sure how to do that, I will investigate more. No, I did not install X-Pack, will do next time, for now reverting to a Windows instance and using it locally remoting into it, I just needed a test instance, thanks. ---
**Author:** ![Maurgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maurgi/32/14778_2.png) [@Maurgi](https://discuss.elastic.co/u/Maurgi)\ **Post date:** [January 24, 2017, 5:37pm UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/8 "2017-01-24T17:37:47Z")
Thanks @forloop, I will give it a try. ---
**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\ **Post date:** [January 25, 2017, 1:17am UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/9 "2017-01-25T01:17:41Z")
Awesome! Feel free to open a discuss thread for any questions that you have about the ARM template 👍 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 22, 2017, 1:17am UTC](https://discuss.elastic.co/t/installing-elk-on-a-new-linux-box-on-azure/72319/10 "2017-02-22T01:17:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.