Pihole beta 5

[JBakers]

The beta5 broke the Dashboard/summary page. Clients and domain pages continue to work.

[Schnuecks]

Same here with the beta

[jdrch]

Yeah please get this fixed so at least it's working by the time 5.0 is released.

[biship]

Please fix

[jdrch]

Welp, still not fixed despite 5.0's release, but based on 5.0's release notes it seems all apps that interact with Pi-hole's inner functionality basically need to be rewritten due the app's transition to a database backend. At least the Enable/Disable toggle works.

[sterrenb]

I noticed the Pihole 5.0 release as well! Will try and make a release that works for the new version.

[peatrick]

I noticed the Pihole 5.0 release as well! Will try and make a release that works for the new version.

Awesome, thanks, sir! Will be seriously looking forward to this update if you can make it work. Appreciate your continued efforts.

[sterrenb]

Since releases on the Play Store currently have a long expected delay, I just created a pre-release of the 5.0.0 build. It contains a fat APK that is not verified. The only guarantee I will give is that it works on my machine. :)

I expect to slowly start deploying to the closed alpha and open beta on the Play Store again. Some features are missing compared to previous versions, so be doubly warned of unstable releases!

[Anoni-Mouse]

The beta5 broke the Dashboard/summary page. Clients and domain pages continue to work.

I have pihole 5 installed and since then the app doesn't work. I removed it then reinstalled it but when I open it I only get a black screen

[jdrch]

The beta5 broke the Dashboard/summary page. Clients and domain pages continue to work.

I have pihole 5 installed and since then the app doesn't work. I removed it then reinstalled it but when I open it I only get a black screen

Enable/Disable (The Play/Pause button at the top right of the main window) should still work. Or at least it does on my Note9 running Android 10.

[Anoni-Mouse]

I also have Note 9 with Android 10, but since I removed the app and reinstalled it, I see nothing at all, just black screen!

[jdrch]

🤔

[Anoni-Mouse]

I solved the issue, I had to go to app settings and flush data. For some reason un installing the app didn't remove the data.

[jdrch]

@Anoni-Mouse Did clearing data get the entire app working again, or just the enable/disable toggle?

Also it might be a good idea to edit your comment to remove our GitHub auth codes that somehow got dumped into it via the email reply ...

I just contacted GitHub about that as there's no way that content should have made it into the actual comment.

[Schnuecks]

Looks good so far, i must uninstall the prvious one and install the alpha. Then i got the dashboard with authentication erros, re-entered the api code, restart the app and now all is there. only problem is that my dns resolvers is shown as null. because i use custom upstream servers.

[Anoni-Mouse]

@Anoni-Mouse Did clearing data get the entire app working again, or just the enable/disable toggle?

Also it might be a good idea to edit your comment to remove our GitHub auth codes that somehow got dumped into it via the email reply ...

I just contacted GitHub about that as there's no way that content should have made it into the actual comment.

Thanks pal. It was because I replied directly from my email. Thanks for bringing this to my attention.

Well, after I upgraded to Pihole 5, the app showed blank content on my dashboard, so one of the things I tried to do was to uninstall the app, and try to install it back. When I open the app, it just gave be black screen no matter how long I waited. I had this idea that the uninstall might not have cleaned everything so from the newly installed app, I went to Android App in settings, and saw that there were 200 MB of app data/cache, so I cleared everything and opened the app successfully. But I also had to reconfigure all the app settings. I got it working, but the problem of the dashboard still persist, i.e., a blank view. All the other settings and windows seem to work fine

[sterrenb]

For anyone wanting to try out the signed alpha builds for version 5, you can join the closed alpha on Google Play here: https://play.google.com/apps/testing/sterrenburg.github.flutterhole.

[Schnuecks]

this beta version keeps complete blank. the alpha from the assets works fine. the beta is versioned with 2.1.4. i think i must wait if available via play store?

[ryanjmchale]

I'm assuming the beta requires updating on the play store as its still the October build.

[biship]

That link signed me up for the beta version, which is the Oct 2019 build.

[tjeffree]

I'm assuming the beta requires updating on the play store as its still the October build.

That link signed me up for the beta version, which is the Oct 2019 build.

@sterrenburg says above:

I expect to slowly start deploying to the closed alpha and open beta on the Play Store again. Some features are missing compared to previous versions, so be doubly warned of unstable releases!

So I think patience is key here.

[sterrenb]

A beta version is now available on the Play Store beta.

If you are interested in beta testing, you can join via https://play.google.com/apps/testing/sterrenburg.github.flutterhole.

[Anoni-Mouse]

I get the email about Beta Testing, and I became a beta tester, yet I see no beta version in the store

[sterrenb]

I get the email about Beta Testing, and I became a beta tester, yet I see no beta version in the store

@Anoni-Mouse don't quote me on this, but I believe the beta rollout takes some time to propagate to all regions. Please check again in a few hours, if it still doesn't show up, I will look into it!

[Anoni-Mouse]

Woooohooo, I finally got the beta and it is working! Thanks

[jdrch]

Looks good so far, i must uninstall the prvious one and install the alpha. Then i got the dashboard with authentication erros, re-entered the api code, restart the app and now all is there. only problem is that my dns resolvers is shown as null. because i use custom upstream servers.

@sterrenburg Is a complete reinstall necessary for full functionality? I got the beta build and plots are down but the number totals at the top are there.

[Anoni-Mouse]

Ok so here are the latest updates regarding this great project. If I update Flutterhole beta over the existing version, I get errors even if the configuration is correct (cannot see queries, white/black lists). I had to completely uninstall the app, install the beta version and for security I have flushed the beta version data. Then I entered all the required settings and everything is working like a charm!

[gorillap]

My interface was also broken after the 5.0 update. I cleared date, deleted.my pihole and set it up again. Instead of using the default info, I entered http://192.168.1.xxx (direct IP address) and pasted the API.key and everything populated normally on all pages.... Except for the primary reason that I used this app... The live query log is still not showing

[jdrch]

Ok so here are the latest updates regarding this great project. If I update Flutterhole beta over the existing version, I get errors even if the configuration is correct (cannot see queries, white/black lists). I had to completely uninstall the app, install the beta version and for security I have flushed the beta version data. Then I entered all the required settings and everything is working like a charm!

I guess that makes sense given Pi-hole's database backend change. Thanks. Created an issue for it on my end.

[gorillap]

I cleared data and re-configured as well as uninstall and reinstall/reconfigure. I'm able to get basic general stats, but still no live query log with option to whitelist/blacklist domains which is my primary reason for using this application.

[biship]

I can't even connect to my pihole from the app. hostname, port & api are fine. No idea why not.

[jdrch]

@biship There might be a trailing space in your API key. Delete the last character in the field for it in Flutterhole and see if that works.

[biship]

No trailing space. I am using nginx with a password, which I can't enter in the app. So I wonder if the app gets the login page and fails.

[Anoni-Mouse]

Here are some screenshots of what I see. The UI has been changed a bit and logging is seen if you click the zZZ icon

[gorillap]

That has not helped. The "zzz" button does what it is supposed to do and brings up and option to pause/sleep

[gorillap]

[gorillap]

There is no general/universal/network log visible. Selecting each device individually shows the query log for that specific device , but there is no ability to whitelist/blocklist from that list.

[sstolk90]

Also in the pie charts of the forward destinations the numbers are not matching the colors in the legenda.

[sterrenb]

@biship There might be a trailing space in your API key. Delete the last character in the field for it in Flutterhole and see if that works.

Regarding whitespace in API tokens: this should be working properly now, since we trim the input string after scanning the QR code. This lead to some issues in previous versions too.

Also in the pie charts of the forward destinations the numbers are not matching the colors in the legenda.

This was a bug, and the fix will be in the upcoming release.

There is no general/universal/network log visible. Selecting each device individually shows the query log for that specific device , but there is no ability to whitelist/blocklist from that list.

The API Log page contains all HTTP requests that the app sent out. This is more for my own debugging purposes, but it might be insightful to see what kind of requests you are sending.

Try looking for requests with a query parameter disable=<time_in_seconds>; are any of these requests sent? Do they contain an auth parameter? Issue #77 also has some issues regarding the API token, take a look there too.

[timocapa]

My PiHole isn't password protected, so I can't grab the API Key

The dashboard doesn't work and complains about being unauthenticated despite authentication not being required I believe

[sterrenb]

My PiHole isn't password protected, so I can't grab the API Key

The dashboard doesn't work and complains about being unauthenticated despite authentication not being required I believe

@timocapa that is correct, the app breaks with a Pi-hole that is not password protected. please check #79 for progress!

[timocapa]

Ah, I apologize, I didn't see that. :)

[jdrch]

OK, got everything up and running, thanks @sterrenburg for the quick fix and thanks @Anoni-Mouse + @gorillap + @sstolk90 for the details.

1 minor warning: be sure to allow the app to autodetect your Pi-hole instance 1st, then edit that instance in the settings with your API key, etc. If you try to create a standalone entry from scratch you'll wind up with 2 Pi-hole entries in the settings and deleting one of them deletes both.

[jdrch]

My PiHole isn't password protected, so I can't grab the API Key

Add a password, then allow others to toggle it if needed (I'm assuming allowing other people to turn it on or off is why you're not using a password) using the API key + Flutterhole as well Remote Switch for Pi-hole on Firefox and Chrome.

[gorillap]

There is no general/universal/network log visible. Selecting each device individually shows the query log for that specific device , but there is no ability to whitelist/blocklist from that list.

The API Log page contains all HTTP requests that the app sent out. This is more for my own debugging purposes, but it might be insightful to see what kind of requests you are sending.

Try looking for requests with a query parameter disable=<time_in_seconds>; are any of these requests sent? Do they contain an auth parameter? Issue #77 also has some issues regarding the API token, take a look there too.

The API log shows no DNS queries, only GET /admin/api.php 55ms GET /admin/api.php 65ms GET /admin/api.php 67ms GET /admin/api.php 121ms

This still doesn't touch on the primary issue. There has always been a selectable "Query log" that shows a realtime view of all queries on the network passing through the PiHole. From there, you could always select them to blacklist or whitelist in realtime as well. It was an interface into the "query log" that is in the PiHole web interface. This is no longer available. The only thing close it clicking on each individual device and seeing those queries, but even from those, there is no option to whitelist or blacklist domains being queried.

[sterrenb]

@gorrilap The dedicated Query Log page is on top of my priority list, so this should find its way into an upcoming build.

Regarding black/whitelists I am at a stand still, please check out issue #76. The endpoints from V4 broke and I haven't found a working solution for V5 yet.

[gorillap]

Awesome, than you very much for all your work on this.

On Mon, May 18, 2020, 6:25 AM Thomas notifications@github.com wrote:

@gorrilap The dedicated Query Log page is on top of my priority list, so this should find its way into an upcoming build.

Regarding black/whitelists I am at a stand still, please check out issue

76 https://github.com/sterrenburg/flutterhole/issues/76. The endpoints

from V4 broke and I haven't found a working solution for V5 yet.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sterrenburg/flutterhole/issues/69#issuecomment-630118537, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6MAMDFBG6PZ7DMN7AX2JTRSELLHANCNFSM4KLQUVPQ .

[gorillap]

Perhaps a temporary workaround could be to just open the query log via webview within the app. Obviously people can just save a bookmark on the mobile desktop to this link, but this might be an easy workaround until the issue is resolved.

http://192.168.1.xxx/admin/queries.php

On Mon, May 18, 2020, 7:33 AM Ryan Hall ryanhall@consultant.com wrote:

Awesome, than you very much for all your work on this.

On Mon, May 18, 2020, 6:25 AM Thomas notifications@github.com wrote:

@gorrilap The dedicated Query Log page is on top of my priority list, so this should find its way into an upcoming build.

Regarding black/whitelists I am at a stand still, please check out issue

76 https://github.com/sterrenburg/flutterhole/issues/76. The

endpoints from V4 broke and I haven't found a working solution for V5 yet.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sterrenburg/flutterhole/issues/69#issuecomment-630118537, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6MAMDFBG6PZ7DMN7AX2JTRSELLHANCNFSM4KLQUVPQ .

[FerhatAkgun]

Getting the new update 5.0.121 beta few minutes ago via playstore, broke flutterhole for me. I tried configuring via API token or basic auth. Non of those worked. Cleared cache and reinstalled.

The main screen/dashboard is stuck in loading.

API log just shows GET /admin/api.php 200

[jdrch]

Getting the new update 5.0.121 beta few minutes ago via playstore, broke flutterhole for me. I tried configuring via API token or basic auth. Non of those worked. Cleared cache and reinstalled.

The main screen/dashboard is stuck in loading.

API log just shows GET /admin/api.php 200

Not seeing this on my end. Make sure you clear the app data also in addition to clear the cache before you uninstall.

[FerhatAkgun]

Getting the new update 5.0.121 beta few minutes ago via playstore, broke flutterhole for me. I tried configuring via API token or basic auth. Non of those worked. Cleared cache and reinstalled. The main screen/dashboard is stuck in loading. API log just shows GET /admin/api.php 200

Not seeing this on my end. Make sure you clear the app data also in addition to clear the cache before you uninstall.

I have fully cleared app data, which clears also the cache. Uninstalled it and configured it again after installing. Still same behavior.

I am using it on Android 10. PI Hole version is 4.4 Web interface version 4.3.3 FTL version 4.3.1

I guess the new flutterhole is not backwards compatible. That should be the problem I guess.