Strange. First thing is to check if it is actually working, on commandline in chroot:
head /var/log/pihole.log
You should see something similar to:
Oct 20 17:37:32 dnsmasq[21330]: started, version 2.72 cachesize 10000
Oct 20 17:37:32 dnsmasq[21330]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
Oct 20 17:37:32 dnsmasq[21330]: warning: ignoring resolv-file flag because no-resolv is set
Oct 20 17:37:32 dnsmasq[21330]: using nameserver 4.2.2.2#53
Oct 20 17:37:32 dnsmasq[21330]: using nameserver 4.2.2.1#53
Oct 20 17:37:32 dnsmasq[21330]: read /etc/hosts - 3 addresses
Oct 20 17:37:32 dnsmasq[21330]: bad name at /etc/pihole/gravity.list line 29670
Oct 20 17:37:32 dnsmasq[21330]: bad name at /etc/pihole/gravity.list line 100224
Oct 20 17:37:32 dnsmasq[21330]: read /etc/pihole/gravity.list - 100224 addresses
if not, you may need to restart dnsmasq, while in chroot:
service dnsmasq restart
On your laptop do a nslookup google.com - verify that it the server that responds is the pi-hole ip.
If not, back in chroot, install pi-hole once again:
curl -L https://install.pi-hole.net | bash
after that restart both the webserver and dnsmasq again
service dnsmasq restart
service lighttpd restart
check the log once again
head /var/log/pihole.log
this is as far as I can take you 