X-Header does not match or could not be retrieved in debug log

[Miko]

Setup

Router

Router: Fritz!Box 7390
FRITZ!OS: 06.83
IPv6: Off (my internet provider only supports IPv4
DNS Server: pi-hole IP
DHCP: off
DNS Rebind Protection, Domain name exceptions: pi.hole

Pi-hole

Board: Odroid C2
OS: DietPi
Pi-hole version is v4.0 (Latest: v4.0)
AdminLTE version is v4.0 (Latest: v4.0)
FTL version is v4.0 (Latest: v4.0)
DHCP: on

Expected Behaviour:

Everything is working great, however, I have a couple of issues in the debug log and wondering if someone could provide some advice on fixing them

Actual Behaviour:

[ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 403 Forbidden
Content-Type: text/html
Content-Length: 345
Date: Tue, 21 Aug 2018 08:29:56 GMT
Server: lighttpd/1.4.45

[✗] Web interface X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Set-Cookie: PHPSESSID=rc3029ircjd3nfgc6anmct1956; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Content-type: text/html; charset=UTF-8
Date: Tue, 21 Aug 2018 08:29:56 GMT
Server: lighttpd/1.4.45

Other

[✗] dnsmasq daemon is inactive

I believe this is a non issue, as in v.4 the pihole-FTL replaced the default dnsmasq daemon.

Is the above correct?

Debug Token:

vbm181cuya

Many thanks

[technicalpyro]

With 4.0 the default blocking method has been modified to be NULLROUTING so this is an expected bheaviour you can learn more here

[Mcat12]

The X-Header warnings can usually be ignored if everything else seems to be working.

The dnsmasq check in the debugger will be removed in the next release, since as you point out FTL has an embedded dnsmasq already.

[Miko]

Thank you @technicalpyro and @Mcat12