Please follow the below template, it will help us to help you!
Expected Behaviour:
no aw snap error
Actual Behaviour:
aw snap
Debug Token:
a4hkpirfxt
Reload the page works
Check your internet connection same aw snap
Clear your cache same aw snap
Close other tabs, extensions, & apps same aw snap
restart computer same aw snap
update chrome same aw snap
uninstall/install same aw snap
check for unwanted software same aw snap
problem exists on all browsers but as failed dns error
not consistence but random
network connection ipv4 shows 2 dns servers 1 pi and 2 router
have set Pi for dns server in router and in pi
router is set to dhcp
router is showing only 1 dns server = pi
pi set to google dns 8.8.8.8
router = asus rt-acrh13
it is ether pi blacklisting something google or the second dns router
out side of that it is working super fantastic
Your query log in Pi-Hole will show which domains have been requested and whether they were blocked by Pi-Hole. This is where you should start to see if Pi-Hole is blocking it.
What specific page were you trying to load and what does the screen on the browser show? You can take a screen snap or capture and post it here.
Is this as shown on a client computer? Please share a capture of what you are seeing.
I'm not following you here. The router has the Pi-Hole listed as it's only DNS server, correct? And where did you set Pi for dns server in pi?
pihole is not blocking nor causing a dns error in google aw snap error
yes i seen that and was asking if they could be blocking something google but after long review and trail and error i see that is not the case
network right click go to ipv4 properties- advance- dns show address of pi and adress of router on client computer
on router dns page is set to pi address (192.168.68.109) and in pi it is set according to direction it has its set to google 8.8.8.8
i have concluded that pi hole is not causing google aw snap error
it is related to google doesn't like ads being block so aw snap
it happens on any website at any time
on any of my computers across my network
this aw snap error goes way back into years of google crash reports earlest i have read is 2015
after trying all of the recommended options to repair it left me with the only thing left was pi hole dns
after white listing several google blocks and disabling pihole it still happened so that eliminated pihole
even the --no-sandbox trick didn't work