Fedora 27 FTLDNS upgrade, spinning arrows, Clients (over time) chart will not load

[pheonix991]

I upgraded from the most recent pihole release to the FTLDNS and the Clients(Over Time) chart does not load. I'm using Fedora 27 in an X86_64 VM. No issues before this.

Expected Behavior:

Clients (Over Time) chart should load.

Actual Behavior:

Clients (Over Time) chart has spinning arrows and does not load statistics.

Debug Token:

Your debug token is: pjm13eyxyl

[mibere]

Hello,

please read and check

Why doesn't my Web interface load stats?

We often see users with broken Web interfaces after updating Pi-hole but it has also appeared during regular usage. The symptoms include: the Web interface has endless spinning indicators the Web interface looks distorted the query log is stuck on Processing none of the Web interface stats load The solution in most cases is to flush your Web browser's cache or service pihole-FTL restart [bc732d4a5ff67fa5e11aa4e840c9631774ce8646_1_690x408]

Why does my admin dashboard have weird grey colors and boxes?

If your dashboard looks something like screenshots below, the solution is to simply flush your browser cache and cookies [image] [image]. [Screenshot_2018-02-27_23-40-11]

[jacob.salmela]

@pheonix991

pjm13eyxyl

Try @mibere's suggestions. If those don't work, please try pihole -r > Repair

[silentdissonance]

I'm having a similar issue.

Ubuntu 17.10 server
FTLDNS
I've tried clearing cache and cookies in browser.

# pihole -up     
  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
  [i] FTL:              update available

  [i] FTL out of date

  [i] FTL Checks...
  [✓] Detected x86_64 architecture
  [i] Checking for existing FTL binary...
  [✓] Downloading and Installing FTL


fatal: unable to access 'https://github.com/pi-hole/AdminLTE.git/': Could not resolve host: github.com
  [i] Web Interface:    up to date

  [i] FTL version is now at 
  [✓] Starting pihole-FTL service
  [✓] Enabling pihole-FTL service to start on reboot

I've tried pihole -r, same problem.
pihole -d provided token tpblqn3yf8

Edit: I should mention, github.com resolves fine, both locally, and on the pihole.
Edit 2: screenshot.

[bcambl]

Were you on the latest stable release version prior to moving to the FTLDNS beta?

[pheonix991]

Clearing cache, using multiple computers and browsers was a no go. I cleared cache on those too. Updated and rebooted the VM, still no go.

I was on the latest stable(as far as I know, 3.3) before moving to FTL. I can restore the VM and try it all again if needed(yay snapshots).

Here's the latest debug.
Your debug token is: jpmakr77mg

[raab]

I'm not sure why I didn't see your post, but I'm getting the same issue as well, posted here Clients over time doesn’t update, just sits there with the spinning

[jacob.salmela]

I don't usually like the nuclear option, but try this (it will wipe out any customizations you have in the Web interface):

sudo rm -rf /var/www/html/admin
sudo git clone https://github.com/pi-hole/AdminLTE.git /var/www/html/admin
pihole checkout web FTLDNS

[silentdissonance]

I had literally just installed it fresh and new, on a brand new Ubuntu 17.10 CT under Proxmox. I don't think it was 'alive' for more than 15 minutes, total.

[silentdissonance]

Nuclear option took care of it, we're golden!

I have to assume something didn't setup right with the switch to FTLDNS in the web interface. No idea what, but this took care of it. Thanks!

[raab]

I've reverted back to master as I was having issues doing lookups to internal domain names with DNSSEC enabled, they were all returning servfail

Probably create a new thread for that at some point

Edit: Quickly tried the nuclear option, no go:

2018-03-28 20:03:19: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function resolveHostname(), 1 passed in /var/www/html/admin/api_FTL.php on line 308 and exactly 2 expected in /var/www/html/admin/scripts/pi-hole/php/FTL.php:143
2018-03-28 20:03:19: (mod_fastcgi.c.2543) FastCGI-stderr: Stack trace:
2018-03-28 20:03:19: (mod_fastcgi.c.2543) FastCGI-stderr: #0 /var/www/html/admin/api_FTL.php(308): resolveHostname('192.168.1.106')
2018-03-28 20:03:19: (mod_fastcgi.c.2543) FastCGI-stderr: #1 /var/www/html/admin/api.php(86): require('/var/www/html/a...')
2018-03-28 20:03:19: (mod_fastcgi.c.2543) FastCGI-stderr: #2 {main}
2018-03-28 20:03:19: (mod_fastcgi.c.2543) FastCGI-stderr: thrown in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 143

[zeit0dn1]

Had the same errors. Found the fix.

in /var/www/html/admin/api_FTL.php
change line 308 from
$forward_dest[resolveHostname($tmp[2])] = floatval($tmp[1]);

to

$forward_dest[resolveHostname($tmp[2],true)] = floatval($tmp[1]);

Chart works great now!!

It works if you use true or false…just seems to need a second parameter.

Maybe one of the dev’s will see this and add the fix into the branch they are working on.

[zeit0dn1]

Hey Blayne, this is Keith from work... yeah, I'm getting a bit involved...LOL

See my post in this thread. There is a function call with a missing parameter for the clients chart for the beta... I found the offending line and fixed it on my install and it works for me now. Perhaps you know someone who could verify and apply the fix to the codebase?

[bcambl]

hmm.. @DL6ER, can you review the proposed change made by @zeit0dn1
resolveHostname was introduced in the following commit:

Add name resolution capabilites (with caching) for web interface

[Mcat12]

See this thread as well:

Clients Chart Not Loading (Spinning Wheel)

Sorry, I apparently missed that, discourse emails are somehow still now very reliable for me (I anyhow get pinged way too often ). I'm in the train without a laptop near me, but I try to remember to look at this. Feel free to ping me again if I forget again...

[pheonix991]

Updated today, issue is solved for me. Thanks for the hard work. Sorry I wasn't able to get back before now.