Expecting to be able to see graphs and things on the web interface.
I also assume that I don't have to run dnsmasq.
PiHole seems to be up and running - ads seem to be blocked, but the stats are not available in the web interface and it reports that 'Lost connection to API'.
FTL is being reported as 'Offline', and I require the dnsmasq service to be started to remove the 'red dot' in the top left hand corner.
With V4 of Pi-Hole, dnsmasq code is included in pihole-FTL, so dnsmasq no longer runs as a separate process. When dnsmasq is running, FTL cannot listen on port 53. From your debug log:
It does not appear to be Pi-Hole doing the blocking. The actual IP address of the requested domain on your block list from your debug log (below) is 192.185.87.146, which was returned. If Pi-Hole had blocked this properly, the returned IP would be 0.0.0.0. Are you running a separate ad-blocker on that client?
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] centralcoastconservationsolutions.com is 192.185.87.146 via localhost (127.0.0.1)
[✓] centralcoastconservationsolutions.com is 192.185.87.146 via Pi-hole (192.168.101.6)
[✓] doubleclick.com is 216.58.213.110 via a remote, public DNS server (8.8.8.8)
Turn off and disable dnsmasq and restart pihole-FTL, and then post a new debug token.
sudo service dnsmasq stop
sudo service dnsmasq disable
sudo service pihole-FTL restart
Valid point well argued.
So I stopped dnsmasq, removed it from the startup and started the FTL.
It ran - but there was some problem with the /usr/bin/pihole-FTP capabilities. I had to edit the service script, and after that, it was all cool.