# Kibana - A secure connection is required for log in **URL:** \ **Category:** Kibana\ **Created:** [December 15, 2022, 1:26pm UTC](https://discuss.elastic.co/t/kibana-a-secure-connection-is-required-for-log-in/321311 "2022-12-15T13:26:16Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![SilasMuniz1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/silasmuniz1/32/108267_2.png) [@SilasMuniz1](https://discuss.elastic.co/u/SilasMuniz1)\ **Post date:** [December 15, 2022, 1:26pm UTC](https://discuss.elastic.co/t/kibana-a-secure-connection-is-required-for-log-in/321311/1 "2022-12-15T13:26:17Z")
Good morning, I am trying setup NGINX to use proxy reverse to access my kibana. The first idea is redirect traffic on [http://172.20.6.213:8080](http://172.20.6.213:8080) to [https://172.20.6.213:5601](https://172.20.6.213:5601). My nginx setup below: ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/4/64ed1aeea1e9f1844ba42e96d60507888e0e5bc2.jpeg) I received this message: ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/f/2fcd89ee13ad72b50e131bdb4f46cf238607b54a.png) I am using the same security files(.crt, .key and ca) that I used in kibana setup. Am I doing something wrong ? Regards, Silas Muniz ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [December 15, 2022, 1:58pm UTC](https://discuss.elastic.co/t/kibana-a-secure-connection-is-required-for-log-in/321311/2 "2022-12-15T13:58:13Z")
I don't think this will work, your Kibana is configured to listen on HTTPS, but your Nginx is using HTTP and Kibana won't accept it. You will need to disable HTTPS in Kibana, which is not recommended, or use a redirect directive in NGINX to redirect the traffic from `8080` to `5601`, you will need to check NGINX on how to do that. What is the reason to use NGINX in this case? ---
**Author:** ![SilasMuniz1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/silasmuniz1/32/108267_2.png) [@SilasMuniz1](https://discuss.elastic.co/u/SilasMuniz1)\ **Post date:** [December 17, 2022, 1:38am UTC](https://discuss.elastic.co/t/kibana-a-secure-connection-is-required-for-log-in/321311/3 "2022-12-17T01:38:53Z")
@leandrojmp I was need access kibana on port 443 (https). I've resolved this problem set up kibana.yml with server port 443 and public url [https://myip:443](https://myip:443). Now I access kibana just [https://myip](https://myip). To resolved problem about low port, I've used these commands: sudo setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana sudo setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana-plugin sudo setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana-keystore sudo setcap cap\_net\_bind\_service=+epi /usr/share/kibana/node/bin/node Thank you. Silas ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 14, 2023, 1:39am UTC](https://discuss.elastic.co/t/kibana-a-secure-connection-is-required-for-log-in/321311/4 "2023-01-14T01:39:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.