search

sterrenb / flutterhole

A third party Android application for the Pi-Hole® dashboard.
https://play.google.com/store/apps/details?id=sterrenburg.github.flutterhole
MIT License
400 stars 27 forks source link

HTTPS problems #84

Open p1r473 opened 4 years ago

p1r473 commented 4 years ago

Hi, I have my PiHole listening on HTTP on port 82 and on HTTPS on 445. I am able to get Flutterhole to work fine in 82/HTTP but not on 445/HTTPS. Has anyone else has luck? I do have the self signed cert option enabled. image image image

p1r473 commented 4 years ago

Manually trying to get to the page works fine: https://192.168.1.186:445/admin/api.php?topItems&auth= image

sterrenb commented 4 years ago

Hello @p1r473 👋 - Thanks for opening an issue!

Indeed the allow self signed checkbox should alllow for this kind of scenario. I will admit that my own Pi-hole is not on SSL, so the testing on this front is spotty.

Could you take a look at the API log page in the app, and see what kind of responses the authenticated queries give you? Perhaps we can uncover the reason for the failed connection status. Perhaps you will find some responses with a 4xx HTTP status code, indicating what kind of error occurs.

p1r473 commented 4 years ago

Thanks for taking a look! image image image

jonahwh commented 4 years ago

Just want to note for the record: I'm using SSL with an authority signed cert, and that is working.

p1r473 commented 4 years ago

I am using a LetsEncrypt cert

jhspyhard commented 3 years ago

I am experiencing this same issue on v5.2.3 with a self-created CA with the root cert added to my device CA Trust Store. Specifically, the app API log shows the same empty body and without header data in the request and response from the Pihole, as p1r473's screenshots above.