Ok, I'm a dummy. I failed to sudo the above. Did that now it seems to connect http.
Sorry for being such a pain. 30 years ago I managed IT for a company and I vividly recall the frustration of people not following instructions during a support session. I also note that all the items in the Pi-hole diagnosis page have cleared. Amazing what happens when people read and follow instructions. By the way, I'll be 80 in a few months, no excuse though.
2 Likes
I have seen this happen myself - after my initial update of my docker (don't worry about the terminology here!) container I noticed the web interface ran very slowly on https - but a subsequent reboot seems to have corrected that, and now it is smooth. 
There is a feature request and some active discussion around bringing back the table for managing DHCP leases:
https://discourse.pi-hole.net/t/make-static-dhcp-lease-gui-user-friendly-as-v5
I always fully expect anyone I'm supported to have not read anything I've said to them 
Happiest of birthdays in a few months!
I'm going to leave everything as-is. It works thanks to you!!
Much appreciation
2 Likes
HTTPS is not needed if you are running Pi-hole just inside your local network.
Thank you. That was discussed and addressed earlier in this thread.The forced https issue and it's effects on the behavior of Pi-hole was fixed with the help of one of the developers. I posted this comment for his/her information as it related to the fix.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.