# Enable Https for Luci

**URL:** <https://forum.openwrt.org/t/enable-https-for-luci/105784>\
**Category:** Network and Wireless Configuration\
**Created:** [September 8, 2021, 2:48pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784 "2021-09-08T14:48:22Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 2:48pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/1 "2021-09-08T14:48:22Z")

</div>

Hi,

I want to enable HTPS for Luci but I have some concerns about slow connection. Would you recommed this? If yes, how can I enable it via SSH or Luci?

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [September 8, 2021, 2:53pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/2 "2021-09-08T14:53:06Z")

</div>

on the LAN side, performance shouldn't really be an issue ....

> [@OpenWrt 21.02.0 - First Stable Release](https://forum.openwrt.org/t/openwrt-21-02-0-first-stable-release/105395):
>
> Hi, The OpenWrt community is proud to announce the first stable release of the OpenWrt 21.02 stable version series. It incorporates over 5800 commits since branching the previous OpenWrt 19.07 release and has been under development for about one and a half year. Highlights in OpenWrt 21.02.0 WPA3 support included by default WPA3 was already supported in 19.07 but it was not provided by the default set of packages in OpenWrt images. With 21.02, all packages necessary to provide WPA3 are inst…

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 3:00pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/3 "2021-09-08T15:00:08Z")

</div>

Ok. Let's go step by step. I'm new at this stuff. So I use Windows CMD for SSH connection.

SSH [root@192.168.1.1](mailto:root@192.168.1.1)

root@OpenWrt:~# (which commands do I need to enable it and disable it)

Thanks.

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [September 8, 2021, 3:00pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/4 "2021-09-08T15:00:37Z")

</div>

have you read the link provided ?

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 3:01pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/5 "2021-09-08T15:01:11Z")

</div>

Yes but quite confusing for me ☹ Sorry.

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [September 8, 2021, 3:02pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/6 "2021-09-08T15:02:39Z")

</div>

hardly, since the whole 2nd chapter is about what you want to do, and ends with a how to do it.

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 3:09pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/7 "2021-09-08T15:09:44Z")

</div>

Applied these codes, rebooted. 192.168.1.1 "your connection is not private"

```
uci set uhttpd.main.redirect_https=1
uci commit uhttpd
service uhttpd reload

```

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [September 8, 2021, 3:11pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/8 "2021-09-08T15:11:23Z")

</div>

did you read the explanation / information provided by the browser ?

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 3:13pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/9 "2021-09-08T15:13:33Z")

</div>

NET::ERR\_CERT\_AUTHORITY\_INVALID

This is error message.

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [September 8, 2021, 3:14pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/10 "2021-09-08T15:14:33Z")

</div>

no, that's the error _code_ ...

read the text attached to the error.

( [https://kinsta.com/knowledgebase/neterr-cert-authority-invalid/](https://kinsta.com/knowledgebase/neterr-cert-authority-invalid/) )

sorry, not doing the leg work for you.

---

<div class="post-metadata">

**Author:** ![takimata](https://forum.openwrt.org/user_avatar/forum.openwrt.org/takimata/32/114647_2.png) [@takimata](https://forum.openwrt.org/u/takimata)\
**Post date:** [September 8, 2021, 3:17pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/11 "2021-09-08T15:17:54Z")

</div>

To be fair, the description/information Chrome provides is really not helpful and slightly panicky (as is probably appropriate when it comes to public websites), it only talks about misconfigurations or attackers trying to steal your information. Neither of which is the case here.

@zrox: The reason is that the SSL certificate is not issued by any authority your browser recognizes. It can't be, the certificate has been made locally on the router. Basically you need to confirm "it's okay, I do know it is not an official certificate, I will accept this 'invalid' certificate." ... once.

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [September 8, 2021, 3:21pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/12 "2021-09-08T15:21:03Z")

</div>

indeed, but it's all there, _including_ the check box ...

it's not like there's a secret handshake or special code you need to know to actually do it,  
plain reading will get you pretty far 😑

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 3:22pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/13 "2021-09-08T15:22:45Z")

</div>

Please help me out this. @takimata

---

<div class="post-metadata">

**Author:** ![takimata](https://forum.openwrt.org/user_avatar/forum.openwrt.org/takimata/32/114647_2.png) [@takimata](https://forum.openwrt.org/u/takimata)\
**Post date:** [September 8, 2021, 3:31pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/18 "2021-09-08T15:31:04Z")

</div>

I may disagree with @frollic's particular choice of words, but I have to agree with their sentiment: You got all the information now. At some point you will have to read and understand the information you are given. We really can't do that for you, sorry.

---

<div class="post-metadata">

**Author:** ![takimata](https://forum.openwrt.org/user_avatar/forum.openwrt.org/takimata/32/114647_2.png) [@takimata](https://forum.openwrt.org/u/takimata)\
**Post date:** [September 8, 2021, 3:52pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/20 "2021-09-08T15:52:40Z")

</div>

It's okay to be frustrated once in a while. Calm down. We are all people here.

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 3:56pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/21 "2021-09-08T15:56:22Z")

</div>

Okay. If you wanna help me I'm here and listening.

---

<div class="post-metadata">

**Author:** ![takimata](https://forum.openwrt.org/user_avatar/forum.openwrt.org/takimata/32/114647_2.png) [@takimata](https://forum.openwrt.org/u/takimata)\
**Post date:** [September 8, 2021, 3:59pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/22 "2021-09-08T15:59:08Z")

</div>

![image](https://forum.openwrt.org/uploads/default/original/3X/2/d/2d7c580d6660d4dd37bc1614893470d983284404.png)

Now what did you learn from that? Do you know what you are actually confirming?

---

<div class="post-metadata">

**Author:** ![Zrox](https://forum.openwrt.org/letter_avatar/zrox/32/5_5575768a8748004e209b776fc1b2916d.png) [@Zrox](https://forum.openwrt.org/u/Zrox)\
**Post date:** [September 8, 2021, 4:00pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/23 "2021-09-08T16:00:29Z")

</div>

I know this but I don't want this warnings to show up.

---

<div class="post-metadata">

**Author:** ![mbo2o](https://forum.openwrt.org/user_avatar/forum.openwrt.org/mbo2o/32/5465_2.png) [@mbo2o](https://forum.openwrt.org/u/mbo2o)\
**Post date:** [September 8, 2021, 4:03pm UTC](https://forum.openwrt.org/t/enable-https-for-luci/105784/24 "2021-09-08T16:03:22Z")

</div>

Just click as the diagram shows.  
By doing this , the browser you are currently using will remember your decision and not give any more warnings.

Basically you are confirming that you trust the site you are visiting
