# Kibana cannot be accessed on different port other than 5601 **URL:** \ **Category:** Kibana\ **Created:** [October 11, 2018, 2:13pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068 "2018-10-11T14:13:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vnallamothu](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@vnallamothu](https://discuss.elastic.co/u/vnallamothu)\ **Post date:** [October 11, 2018, 2:13pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068/1 "2018-10-11T14:13:04Z")
I cannot access Kibana on different port other than 5601. I changed the server.port property in Kibana.yml file to several different unused ports. But I cannot access it from those ports. I can only access it on port 5601. ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [October 11, 2018, 2:20pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068/2 "2018-10-11T14:20:45Z")
hmm, thats all is needed to load it on a different port - To change the host or port number, or connect to Elasticsearch running on a different machine, you’ll need to update your `kibana.yml` file. Did you restart your service , post the changes to make the changes apply? Any logs to support or any kind of screenshot you could provide? Cheers Rshmi ---
**Author:** ![vnallamothu](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@vnallamothu](https://discuss.elastic.co/u/vnallamothu)\ **Post date:** [October 11, 2018, 2:34pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068/3 "2018-10-11T14:34:48Z")
Yes, I did restart both elasticsearch and kibana services. My log files are full of logs as of now and it is taking a while to load them. Can I delete the logs and regenerate them after restarting the service? ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [October 11, 2018, 2:42pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068/4 "2018-10-11T14:42:09Z")
Yea, if you don't care about the old logs, you can always restart the service and logs will start collecting as well. Cheers Rashmi ---
**Author:** ![vnallamothu](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@vnallamothu](https://discuss.elastic.co/u/vnallamothu)\ **Post date:** [October 11, 2018, 3:00pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068/5 "2018-10-11T15:00:06Z")
I've cleared all logs. Now after I change the server.port property to 5602 and restarted the service, I see following logs in kibana.log file: ``` {"type":"log","@timestamp":"2018-10-11T14:53:00Z","tags":["listening","info"],"pid":6884,"message":"Server running at http://10.*.*.*:5602"} {"type":"log","@timestamp":"2018-10-11T14:53:00Z","tags":["status","ui settings","info"],"pid":6884,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} ``` When I access the kibana page on 5602 poet, it says: " This site can’t be reached **10._._.** \* took too long to respond. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 8, 2018, 3:00pm UTC](https://discuss.elastic.co/t/kibana-cannot-be-accessed-on-different-port-other-than-5601/152068/6 "2018-11-08T15:00:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.