Update list of ad-serving domains fails

Help
1

I'm running on a Centos 7 system and the PiHole does work. SELinux is disabled.

I don't have any issues to download the lists via a web browser or a curl command when I'm on the PiHole system.

But when I try to update the lists via the wed-admin interface I do get this result for all my lists:

:::
::: Neutrino emissions detected...
:::
::: Pulling source lists into range... done!
:::
::: Getting raw.githubusercontent.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting mirror1.malwaredomains.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting sysctl.org list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting zeustracker.abuse.ch list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting s3.amazonaws.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting s3.amazonaws.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting hosts-file.net list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)

The debug log doesn't show any problem.

Any idea for trouble shooting ?

Kind regards,
Thorsten

2

What is the debug token? We might find something you missed.

3

I'm not able to upload the log file.

I do get the error message : Ncat: Network unreachable

curl is still working, also INET access via browser.

So I also don't have a debug token.

4

Can you try copying the /var/log/pihole_debug.log file and uploading it somewhere?

5

Can you send me an email address to the account that I'm using here ? I can't post the log file in public.

6

You seem to be unable to ping an external IP address (8.8.8.8) or connect to outside servers (sometimes). Is the Pi-hole being affected by a restrictive firewall?

7

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