V6 timeout and HTTPS

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

I am expecting the previous 7 days sticky login I used to have in V5 and no auto logout of the web interface.
Also, I do not expect the new message asking to force HTTPs as it was never needed in V5 and I run on my local network

Actual Behaviour:

As of the upgrade to V6 I observed 2 issues:

  1. The Web interface times out / logs me out every few minutes, the option to stay logged in for 7 days no longer appears
  2. The browser shows an error that HTTPS is not enabled and my session isn't secured, I run my pihole instance on the local network and never needed HTTPS

Debug Token:

https://tricorder.pi-hole.net/Y8txgFvz/

2

The webserver timeout is listed in the /etc/piole/pihole.toml file. Its default is 1800 seconds. You can change the value there.

  [webserver.session]
    # Session timeout in seconds. If a session is inactive for more than this time, it will
    # be terminated. Sessions are continuously refreshed by the web interface, preventing
    # sessions from timing out while the web interface is open.
    # This option may also be used to make logins persistent for long times, e.g. 86400
    # seconds (24 hours), 604800 seconds (7 days) or 2592000 seconds (30 days). Note that
    # the total number of concurrent sessions is limited so setting this value too high
    # may result in users being rejected and unable to log in if there are already too
    # many sessions active.
    timeout = 1800
3

Thank you, that helps! Do you know how do I get rid of the HTTPS warning?

4

Maybe bind only Port 80 ??

5

I think the warning is likely just coded into the page to remind people its an unsecured connection. That would be a question for the devs though.

6

Yeah that's correct. I can't remember where I saw it (might be internal), but I saw some discussion around maybe making this warning/message less prominent.

HTTPs is great, but in almost all cases it's overkill on a local (closed) network. Unless you really don't trust the people you live with.

7

Since I have got other stuff running with Self Signed Certificates like OPNsense and the UniFi Controller the fact that Pi-Hole v6 has one too was a nice surprise for me :+1:

So one of the first things I did was bind it only to port 443 :sunglasses: :grin:

8

Every time I visit the unifi dashboard I think to myself "I must set up a certificate properly"

And then I find something more interesting to do

9

As you should! :grimacing: :+1: :+1:

IMHO it's not worth the hassle for those few visits per year :wink:
There are some scripts for it online tho if you feel like doing it anyway...