jacklul
Senior Member
Really? That's kinda weird because Content-Length header indicates there is content.If you mean the response tab there‘s nothing to be seen
Really? That's kinda weird because Content-Length header indicates there is content.If you mean the response tab there‘s nothing to be seen
I will look through the source code and try to find potential issue with the empty response.Yes, unfortunately there is indeed nothing to see. Empty. Have now tried different browsers, Edge & Chrome (Windows).
And no matter which browser I use, whether Safari on MacOS or iPad, or Chrome and Opera (Windows), after clicking on Interfaces tab it no longer responds. Pihole itself works great.
One more point: Is it correct that the https setting must be applied again after each re-logging in?
One more thing (no complaint or criticism): The first call of the Pihole admin interface seems to be quite sluggish, is there a way to improve that?
Thanks! Take all the time you need!I will look through the source code and try to find potential issue with the empty response.
Yes, on the login page. If I select https, I have to do it again the next time I log in. If I bookmark the https connection, it doesn't open the login page.Which https setting, you mean the insecure connection warning on login page ? If you just bookmark it with https already on he address the there will be no issue.
I can't report that; when I'm connected via https, everything works smoothly and quickly in the UI.I remember people reported slow web UI with https in the past.
I personally have "https://pi.hole/admin" bookmarked and it works without such issues.Yes, on the login page. If I select https, I have to do it again the next time I log in. If I bookmark the https connection, it doesn't open the login page.
When Pi-hole v6 was in the beta and early release people reported issues with HTTPS connection, I think it had some issues with the crypto library handling depending on the CPU or other things, I'm not sure about details on this.I can't report that; when I'm connected via https, everything works smoothly and quickly in the UI.
It would be interesting to know if other users are also experiencing this error with the interfaces page.
Perhaps I made some other mistakes during the installation?
That doesn't work for me. Nothing is opened, "Server not found". So I have to use the IP address.I personally have "https://pi.hole/admin" bookmarked and it works without such issues.
What does it open instead if not the login page?
To be honest, I don't dare to do that...If you're willing - you might try installing development version of the package (pi-hole-dev) and reporting back if there is any difference. Note that updating to development version can be a one-way update - you might not be able to go back to stable version.
I'm pretty sure you missed a step in the guide and didn't set 'dns.reply.host.IPv4=192.168.x.x' or 'webserver.port' has no entry for '192.168.x.x:443s'.That doesn't work for me. Nothing is opened, "Server not found". So I have to use the IP address.
Update: So, I Noob have now also found the setting... but, it only works like this: https://pi.hole:5443/admin/login
How is it going without 5443 ..?
All settings now appear to be correct. I can't understand why "5443" has crept in at webserver.port. Well.I'm pretty sure you missed a step in the guide and didn't set 'dns.reply.host.IPv4=192.168.x.x' or 'webserver.port' has no entry for '192.168.x.x:443s'.
I certainly would consider adding this to amtm. But there is nothing to add at the moment as there is no install script, much less any other compatibility with what amtm expects.It would be fantastic if this excellent project is included in AMTM.
@jacklul @bibikalka and Maestro @thelonelycoder
I keep 5080 and 5443 entries in there just incase the extra IP and pi.hole domain stops working so I have a fallback way of getting into Pi-hole UI.All settings now appear to be correct. I can't understand why "5443" has crept in at webserver.port. Well.
Interfaces page is just an extra functionality that shouldn't affect the blockingIf interfaces would still work now would be completely happy...![]()
Alternatively, you can enable 'debug.netlink' option (Settings -> All -> Debug), open the interfaces page and share the FTL.log with me (it may contain sensitive data so use the tool I linked earlier).To be honest, I don't dare to do that...![]()
Some caveats:It would be fantastic if this excellent project is included in AMTM.
Some caveats:
- I'm not using Merlin's firmware and I don't want to blindly create untested install scripts
- I'm not sure if you can add 'pihole' user (in USB->Samba) through the SSH/script
- Extra IP step might be problematic - what if there isn't available IP
Some caveats:
- I'm not using Merlin's firmware and I don't want to blindly create untested install scripts
- I'm not sure if you can add 'pihole' user (in USB->Samba) through the SSH/script
- Extra IP step might be problematic - what if there isn't available IP to use? (everything reserved by DHCP)
Bitte, gärn gscheh.Merci vielmal @thelonelycoder!
No, I could only provide financial support...Bitte, gärn gscheh.
Are you going to give it a go at coding this?
Are you going to give it a go at coding this?
@Viktor Jaep, are you ready to take on piHOLEMON?I nominate @SomeWhereOverTheRainBow for this! He would do amazing!![]()
That's exactly what I'm NOT saying.@Viktor Jaep, are you ready to take on piHOLEMON?
Now that you've been brought into play here, resistance is pointless. You have been assimilated, so to speak, my lord. - Seriously, if it is possible, try to provide support.That's exactly what I'm NOT saying.I thought I'd get ahead of the game before <INSERT-NAME-HERE>-MON names started being suggested. Lol
We use essential cookies to make this site work, and optional cookies to enhance your experience.