Can not access GitHub.com but is on White list in pi hole

Help
1

I am running pi hole with unbound and all works really well. But unfortunately I can not get access to www.github.com. It is in the white list and never shows as blocked. I have had this problem before I was using unbound. I could not update pi hole because GitHub could not be accessed. I was able to update to latest version pi hole by using mobile hot spot to by pass my network. Updated perfectly.
I have done dig www.github.com and all looks fine. I have created a debug token but not sure how to use it from here. I have another web page that won't go through either if that helps look into it further.

2

Post the token here. That lets us find the debug log on the server.

3

What is the output of this command from the Pi terminal:

pihole -q -adlist -all github.com

4

Hello and thank. Please see debug token 07pkfyxcej i will run the other command tonight

5

pi@raspberrypi:~ $ dig www.github.com

; <<>> DiG 9.10.3-P4-Raspbian <<>> www.github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51025
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.github.com.			IN	A

;; ANSWER SECTION:
www.github.com.		3600	IN	CNAME	github.com.
github.com.		3449	IN	A	192.30.255.113
github.com.		3449	IN	A	192.30.255.112

;; Query time: 359 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Feb 12 09:54:06 UTC 2019
;; MSG SIZE  rcvd: 89
6

Your dig command shows a valid reply which indicates that the domain is not being blocked by Pi-Hole.

Looking at your debug log, you have some configuration issues.

The assigned IP of the Pihole is on a /7 submask, whereas Pi-Hole is listening on /24

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.20.7/7 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)

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.20.7/24

This may be causing this error:

[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

7

Thank your for your advise. Sounds promising.
So if I change the text in the config file /etc/pihole/setupVars.conf
From/7 to /24 this will then fix the submask?

8

No. Pi-Hole is already setup in setupVars.conf to listen on /24, but the actual IP that the Pi has is the /7.

The fix would be in the static IP of the Pi.

9

Thanks again. Sorry for my lack of understanding. But could you please advise how I would change the static IP of the pi hole to make this fix. Step by step would be great. So sorry for asking.

10

Here are a few online references:

http://www.techsneeze.com/configuring-static-ip-raspberry-pi-running-raspbian/

11

Thanks again!. I will have a read and see what I can do.

12

Did you ever run this command? This will identify all occurences of that domain name in gravity, whitelist and blacklists.

13

Not yet. I will definitely do it as soon as I'm home. Though

14

Hi again. Looks like we might be heading in the right direction. Thanks so much for your help!!
This is what I have found thanks to you.

1st

pi@raspberrypi:~ $ pihole -q -adlist -all github.com
Match found in Whitelist
github.com
www.github.com
Match found in https://hosts-file.net/ad_servers.txt:
collector-cdn.github.com
pivotal.github.com
pi@raspberrypi:~ $

2nd

Not working

nterface eth0
static ip_address=192.168.2.20.7
static routers=192.168.20.1
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.20/7
static routers=192.168.20.1
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.20.1/7
static routers=203.111.96.126
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.20.7/24
static routers=192.168.20.1
static domain_name_servers=127.0.0.1

Working but should I have this many?
Changed the 192.168.2.20.7 to and all to /24

nterface eth0
static ip_address=192.168.2.20.7/24
static routers=192.168.20.1
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.20/24
static routers=192.168.20.1
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.20.1/24
static routers=203.111.96.126
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.20.7/24
static routers=192.168.20.1
static domain_name_servers=127.0.0.1

Now have access to www.github.com
But rardarr not updating still this is error msg.

MessageFailed to get response from: https://github.com/Radarr/Radarr/releases/download/v0.2.0.1293/Radarr.develop.0.2.0.1293.linux.tar.gz Error: ConnectFailure (No route to host)

Close

Radarr Ver. 0.2.0.1120

15

Please run a new debug log and post the token.

16

Hello, please see debug token below.
zfq4yxigfo
Thank you!

17

Your new debug log looks fine - no problems.

I don't think this is a Pi-Hole issue unless you see that DNS query blocked by Pi-Hole.

18

Excellent thanks for the help and fixing my problem. I will jump over to GitHub for my Rardarr problem.
Thanks again!

1 Like
19

Well woke up this morning and Rardarr had completed the update. Looks to be all the same problem!!! Everything is working really well!!!!!
Thanks again problem solved.

20

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