Can't access internet v3.2.1 - Other devices OK

v3-2-1

#1

Please follow the below template, it will help us to help you!

Expected Behaviour:

Internet working as normal and having Queries working

Actual Behaviour:

From my Raspberry Pi 3, Pi Hole 3.2.1, I can’t access internet. I can’t ping anything other then, pi.hole, 192.168.0.150 (my pi’s IP and my DNS setting on my D-Link 826L)

Having issues getting Queries to work as well.

I changed my eth0 to static in the dhcp file. made my eth0 manual in the interfaces file.

Turned off DHCP on my router and enabled it on pi-hole admin interface.

I originally had the latest pi hole but was having issues with the extra addon. So i did the downgrade to 3.2.1

Debug Token:

Pi-hole
Toggle navigation
retropie
Pi-hole logoPi-hole
Pi-hole logo
Status

Active Temp: 45.1 °C
Load: 0.37 0.2 0.18
Memory usage: 29.1 %
MAIN NAVIGATION
Dashboard
Query Log
Long term data
Whitelist
Blacklist
Disable
Tools
Update Lists
Query adlists
Audit log
Tail pihole.log
Tail pihole-FTL.log
Generate debug log
Settings
Logout
Donate
Help
Generate debug log
Upload debug log and provide token once finished

Once you click this button a debug log will be generated and can automatically be uploaded if we detect a working internet connection.

This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations.  This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected.  Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2018-06-03:21:59:36 debug log has been initiated.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v3.2.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: HEAD (https://discourse.pi-hole.net/t/the-pihole-command-with-examples/738#checkout)
[i] Commit: v3.2.1-0-ge602008

*** [ DIAGNOSING ]: Web version
[i] Web: v3.2.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: HEAD (https://discourse.pi-hole.net/t/the-pihole-command-with-examples/738#checkout)
[i] Commit: v3.2.1-0-g31dddd8

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v2.13.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)

*** [ DIAGNOSING ]: dnsmasq version
[i] 2.72

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35

*** [ DIAGNOSING ]: php version
[i] 5.6.33

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 8 (jessie)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.0.150/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
   fe80::c746:2f4:ba3a:8576 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.0.1
   * Pinging 192.168.0.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)


*** [ DIAGNOSING ]: Ports in use
[139] is in use by smbd
[22] is in use by sshd
[445] is in use by smbd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] track.theprovision.net is 192.168.0.150 via localhost (127.0.0.1)
[✓] track.theprovision.net is 192.168.0.150 via Pi-hole (192.168.0.150)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.0.150/24
    IPV6_ADDRESS=
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    QUERY_LOGGING=true
    INSTALL_WEB=true
    LIGHTTPD_ENABLED=1
    DHCP_ACTIVE=true
    DHCP_START=192.168.0.200
    DHCP_END=192.168.0.251
    DHCP_ROUTER=192.168.0.1
    DHCP_LEASETIME=24
    PIHOLE_DOMAIN=local
    DHCP_IPv6=false

*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 4554709 Jun  3 19:14 /etc/pihole/gravity.list
   -----head of gravity.list------
   192.168.0.150 0.0.0.0
   192.168.0.150 0000mps.webpreview.dsl.net
   192.168.0.150 000.0x1f4b0.com
   192.168.0.150 0001.2waky.com

   -----tail of gravity.list------
   192.168.0.150 zztxdown.com
   192.168.0.150 zzz.clickbank.net
   192.168.0.150 zz.zeroredirect1.com
   192.168.0.150 zzzrtrcm2.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 633 Jun  3 19:14 /etc/pihole/adlists.default
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt

-rw-r--r-- 1 root root 633 Jun  3 19:14 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt

-rw-r--r-- 1 root root 45 Jun  3 19:14 /etc/pihole/local.list
   192.168.0.150 retropie
   192.168.0.150 pi.hole

-rw-r--r-- 1 root root 234 Jun  3 19:14 /etc/pihole/logrotate
   /var/log/pihole.log {
   	su root root
   	daily
   	copytruncate
   	rotate 5
   	compress
   	delaycompress
   	notifempty
   	nomail
   }
   /var/log/pihole-FTL.log {
   	su root root
   	weekly
   	copytruncate
   	rotate 3
   	compress
   	delaycompress
   	notifempty
   	nomail
   }

-rw-r--r-- 1 root root 117 Jun  3 19:14 /etc/pihole/whitelist.txt
   raw.githubusercontent.com
   mirror1.malwaredomains.com
   sysctl.org
   zeustracker.abuse.ch
   s3.amazonaws.com
   hosts-file.net

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1502 Jun  3 21:27 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/gravity.list
   addn-hosts=/etc/pihole/black.list
   addn-hosts=/etc/pihole/local.list
   localise-queries
   no-resolv
   cache-size=10000
   log-queries
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=8.8.8.8
   server=8.8.4.4
   interface=eth0

-rw-r--r-- 1 root root 485 Jun  3 21:27 /etc/dnsmasq.d/02-pihole-dhcp.conf
   dhcp-authoritative
   dhcp-range=192.168.0.200,192.168.0.251,24h
   dhcp-option=option:router,192.168.0.1
   dhcp-leasefile=/etc/pihole/dhcp.leases
   domain=local

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3027 Jun  3 19:14 /etc/lighttpd/lighttpd.conf
   server.modules = (
   	"mod_access",
   	"mod_accesslog",
   	"mod_auth",
   	"mod_expire",
   	"mod_compress",
   	"mod_redirect",
   	"mod_setenv",
   	"mod_rewrite"
   )
   server.document-root        = "/var/www/html"
   server.error-handler-404    = "pihole/index.php"
   server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
   server.errorlog             = "/var/log/lighttpd/error.log"
   server.pid-file             = "/var/run/lighttpd.pid"
   server.username             = "www-data"
   server.groupname            = "www-data"
   server.port                 = 80
   accesslog.filename          = "/var/log/lighttpd/access.log"
   accesslog.format            = "%{%s}t|%V|%r|%s|%b"
   index-file.names            = ( "index.php", "index.html", "index.lighttpd.html" )
   url.access-deny             = ( "~", ".inc", ".md", ".yml", ".ini" )
   static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
   compress.cache-dir          = "/var/cache/lighttpd/compress/"
   compress.filetype           = ( "application/javascript", "text/css", "text/html", "text/plain" )
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "/usr/share/lighttpd/create-mime.assign.pl"
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
   $HTTP["url"] =~ "^/admin/" {
       
       setenv.add-response-header = (
           "X-Pi-hole" => "The Pi-hole Web interface is working!",
           "X-Frame-Options" => "DENY"
       )
       $HTTP["url"] =~ ".ttf$" {
           
           setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
       }
   }
   $HTTP["url"] =~ "^/admin/\.(.*)" {
        url.access-deny = ("")
   }
   include_shell "cat external.conf 2>/dev/null"

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1630 Jun  3 19:14 /etc/cron.d/pihole
   36 4   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity
   00 00   * * *   root    PATH="$PATH:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate /etc/pihole/logrotate
   */10 *  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker local
   11 16  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
   @reboot root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 1277 Jun  3 20:27 /var/log/lighttpd/error.log
   2018-06-03 18:38:09: (log.c.164) server started 
   2018-06-03 18:46:40: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 18:46:53: (log.c.164) server started 
   2018-06-03 18:46:53: (log.c.164) server started 
   2018-06-03 19:14:26: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 19:14:44: (log.c.164) server started 
   2018-06-03 19:15:56: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 19:16:09: (log.c.164) server started 
   2018-06-03 19:23:59: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning:  parse_ini_file(/etc/pihole/pihole-FTL.conf): failed to open stream: No such file or directory in /var/www/html/admin/api_db.php on line 18
   2018-06-03 19:57:41: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 19:57:59: (log.c.164) server started 
   2018-06-03 19:59:47: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 20:00:04: (log.c.164) server started 
   2018-06-03 20:02:08: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 20:02:24: (log.c.164) server started 
   2018-06-03 20:12:20: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 20:12:37: (log.c.164) server started 
   2018-06-03 20:27:13: (server.c.1558) server stopped by UID = 0 PID = 1 
   2018-06-03 20:27:31: (log.c.164) server started 

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 26489 Jun  3 21:27 /var/log/pihole-FTL.log
   [2018-06-03 19:14:46.093] 
   [2018-06-03 19:14:46.093] FTL branch: v3.0
   [2018-06-03 19:14:46.093] FTL version: v3.0
   [2018-06-03 19:14:46.093] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d7
   [2018-06-03 19:14:46.093] FTL date: 2018-02-14 12:45:47 -0800
   [2018-06-03 19:14:46.093] FTL user: pihole
   [2018-06-03 19:14:46.093] Notice: Found no readable FTL config file
   [2018-06-03 19:14:46.093]         Using default settings
   [2018-06-03 19:14:46.093] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2018-06-03 19:14:46.093]    SOCKET_LISTENING: only local
   [2018-06-03 19:14:46.093]    QUERY_DISPLAY: Show queries
   [2018-06-03 19:14:46.093]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2018-06-03 19:14:46.093]    MAXDBDAYS: max age for stored queries is 365 days
   [2018-06-03 19:14:46.093]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2018-06-03 19:14:46.093]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2018-06-03 19:14:46.093]    DBINTERVAL: saving to DB file every minute
   [2018-06-03 19:14:46.093]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2018-06-03 19:14:46.093]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2018-06-03 19:14:46.094] Finished config file parsing
   [2018-06-03 19:14:46.101] Found no other running pihole-FTL process
   [2018-06-03 19:14:46.103] PID of FTL process: 3142
   [2018-06-03 19:14:46.103] Error: failed to read /etc/pihole/list.preEventHorizon
   [2018-06-03 19:14:46.103] Gravity list entries: -1
   [2018-06-03 19:14:46.103] No blacklist present
   [2018-06-03 19:14:46.103] No wildcard blocking list present

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 339702 Jun  3 22:02 /var/log/pihole.log
   -----head of pihole.log------
   Jun  3 18:46:47 dnsmasq[518]: started, version 2.72 cachesize 10000
   Jun  3 18:46:47 dnsmasq[518]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
   Jun  3 18:46:47 dnsmasq[518]: warning: ignoring resolv-file flag because no-resolv is set
   Jun  3 18:46:47 dnsmasq[518]: using nameserver 8.8.4.4#53
   Jun  3 18:46:47 dnsmasq[518]: using nameserver 8.8.8.8#53
   Jun  3 18:46:47 dnsmasq[518]: read /etc/hosts - 5 addresses
   Jun  3 18:46:47 dnsmasq[518]: failed to load names from /etc/pihole/local.list: No such file or directory
   Jun  3 18:46:47 dnsmasq[518]: failed to load names from /etc/pihole/black.list: No such file or directory
   Jun  3 18:46:47 dnsmasq[518]: failed to load names from /etc/pihole/gravity.list: No such file or directory
   Jun  3 19:14:27 dnsmasq[518]: exiting on receipt of SIGTERM
   Jun  3 19:14:43 dnsmasq[2938]: started, version 2.72 cachesize 10000
   Jun  3 19:14:43 dnsmasq[2938]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
   Jun  3 19:14:43 dnsmasq[2938]: warning: ignoring resolv-file flag because no-resolv is set
   Jun  3 19:14:43 dnsmasq[2938]: using nameserver 8.8.4.4#53
   Jun  3 19:14:43 dnsmasq[2938]: using nameserver 8.8.8.8#53
   Jun  3 19:14:43 dnsmasq[2938]: read /etc/hosts - 5 addresses
   Jun  3 19:14:43 dnsmasq[2938]: failed to load names from /etc/pihole/local.list: No such file or directory
   Jun  3 19:14:43 dnsmasq[2938]: failed to load names from /etc/pihole/black.list: No such file or directory
   Jun  3 19:14:43 dnsmasq[2938]: failed to load names from /etc/pihole/gravity.list: No such file or directory
   Jun  3 19:14:47 dnsmasq[2938]: query[AAAA] raw.githubusercontent.com from 127.0.0.1


********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

    * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
    * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
    * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[i] Debug script running in automated mode
    * Using openssl for transmission.
[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log

Pi-hole Version vDev (HEAD, v3.2.1-0-ge602008) Web Interface Version vDev (HEAD, v3.2.1-0-g31dddd8) FTL Version vDev (v2.13.2 , v2.13.2 )  Donate if you found this useful.

#2

You have some networking issues:

  • You can’t ping your router from the Pi, or you set the wrong gateway in your network settings.
  • You can’t resolve queries via an external DNS server.
  • You can’t access the internet

Also, FTL and dnsmasq fail to read in crucial data generated by pihole -g (although it seems dnsmasq was able to read in something recently, because it blocked one query).

You might want to start over with the latest version of Raspbian (Stretch).


#3

I have RetroPie on this card and wanted to try out Pi Hole on the build I have.

I am going to try to uninstall Pi Hole and see if I can get my network working again for now. Maybe I will wait for the next version and try again.

Thanks


#4

I unistalled 3.2.1, put my DNS back to 192.168.0.1 in my router. Restarted my modem and router. Eventually I was able to start pinging sites and was able to install the version of dnsmasq that supports the extra flag (v2.76).

I was able to install 3.3.1 properly.

I was still able to ping sites etc…

As I am using a Dlink router, am I only changing the DNS to 192.168.0.150 or is there other things I need to do? As soon as i change the DNS to that I lose the ability to ping the router and sites etc…


#5

I just had a quick look at the manual for your router.

From the looks of it, the DIR-826L does not allow you to specify a local DNS resolver. In the WAN settings, you can specify an upstream provides, but if you put something on your local network it will not work.

The only (limited) options to change the LAN DNS seem to be on the “Router Settings” tab, and your choice is “Enable DNS Relay”, which feeds your upstream provider to your hosts, or if it is disabled, the router serves the DNS requests.

So it seems you’ll need to use your Pi-hole as a DHCP server if you want to use it as your network’s DNS, which should be more successful now you’ve upgraded to 3.3.1.


#6

Hi robgill,

I put the DNS to 192.168.0.1 on the router and I disabled DHCP on the router.

In Pi Hole I enabled DHCP under the settings asit shows on the site you provided.

However I dont appear to be getting blocked ads or queries still.

I am finally able to create a token… 41zlcmmic9


#7

I’m assuming you mean you’ve set the DNS to 192.168.0.1 on the “INTERNET CONNECTION TYPE” page. The router will be going in circles. Try changing it to 8.8.8.8.

Then on the “NETWORK SETTINGS” page, if you haven’t already, uncheck “Enable DNS Relay”.

And on “DHCP SERVER SETTINGS”, make sure both “Always Broadcast” and “Enable DHCP Server” are unchecked.

You may need to restart both the router and any devices on your network to ensure that they obtain new DHCP leases from your Pi-hole which will provide them with the new DNS address of your Pi-hole.


#8

robgill :slight_smile:

Did what you said.

Everything looks to be working great now!

Thanks for the help


#9

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.