Some Websites load very slow

Hey Guys

Last time i got a flawless Support here, so i would give it a try again :slight_smile:
I've seen the other Posts with similar Problems, but i can't get a solution oft them.
As i said in the Description, some Websites have a really long load time, sometimes it takes Minutes to open one of these Sites.

Examples are
www.pcgameshardware.de
www.heise.de

I've tried to load the Websites without the Pi-Hole activated in my Settings and it works like it should.
I updated the System and the List to the newest Versions and I also try a fresh Install with no luck.
The Websites are not listed in any list I activated in the Pi-Hole Settings, I've tried different Upstream DNS but nothing could help me out here.

When you need more Informations, tell me and i will post them here :slight_smile:

I tested both sites and they load like expected. The loading also finishes within less than like two seconds.

When you write [quote="Select25, post:1, topic:1876"]
sometimes it takes Minutes to open one of these Sites.
[/quote]

you mean that no content at all is shown within the time you wait or does the content come and just the loading indicator of the webpage does never go away?

Can you provide a debug token (pihole -d and upload the log)?

Yeah thats right, when i try to load the Paige it stays totally blank and the loading Indicator stays at one point, but after a little Time it will shown up as it should.
Then when I klick one of the Links there it will take some time again and again.
I've run the command while open the two Websites and sent you the Token via PM.

Sounds like the firewall is enabled on whatever device you installed pi-hole on. If the devices in your network cannot reach the pi-hole server on TCP port 80 and 443 then you will experience slowness like what you describe.

Is the firewall enabled on your pi-hole server?

How can I find out? :smiley: Tell me and i will have a look.

sudo iptables -L is a good place to start. Have you run a pihole -d yet?

Yes I run the debug command and sent the token via pm to DL6ER
I also run the other command and that's the output

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Can you post the token? There's currently only 6 people on the planet that can access your data with the token, so its not something that needs to be protected. You can try to access https://tricorder.pi-hole.net and see that it's not accessible to people not in the approved list.

Okay good to know :slight_smile:
Here is the token
y1bp2mvt6l

Okay, the query for the domain name and the response with the IP address for the domain happen in the same second. So the DNS server is responding quickly. The next step would be to try to check the webpage rendering. What OS is running on the client? And which browser are you using?

Rasbian jessy light
And Main OS is Mac OS Sierra with the Safari browser.

Alright, on the Pi-hole, try the following command, and post the results please. (There is no personally identifiable information generated, this will just let us know if the Pi is able to view the site correctly locally first.)

curl -i -v http://www.pcgameshardware.de/ | head -n 20

  • Hostname was NOT found in DNS cache
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 2400:cb00:2048:1::6814:c2f...
  • Connected to www.pcgameshardware.de (2400:cb00:2048:1::6814:c2f) port 80 (#0)

GET / HTTP/1.1
User-Agent: curl/7.38.0
Host: www.pcgameshardware.de
Accept: /

< HTTP/1.1 200 OK
< Date: Sat, 25 Feb 2017 07:18:17 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=ded56ddc949e214e99a041d43ed41b4721488007097; expires=Sun, 25-Feb-18 07:18:17 GMT; path=/; domain=.pcgameshardware.de; HttpOnly
< Set-Cookie: CFID=825212191;expires=Mon, 18-Feb-2047 07:18:17 GMT;path=/
< Set-Cookie: CFTOKEN=c34b0d427765f6c4-74226E30-A69D-2108-D41580A6F90392C1;expires=Mon, 18-Feb-2047 07:18:17 GMT;path=/
< Set-Cookie: CPTBP=7666491;domain=pcgameshardware.de;path=/
< X-UA-Compatible: IE=edge
< Cache-Control: max-age=0
< Expires: Sat, 25 Feb 2017 07:18:17 GMT
< X-Clacks-Overhead: GNU Terry Pratchett
< Vary: Accept-Encoding
< Set-Cookie: PCGHWLBCOOKIE=s1; path=/
< Cache-control: private

  • Server cloudflare-nginx is not blacklisted
    < Server: cloudflare-nginx
    < CF-RAY: 336961e9c4bb6475-FRA
    <
    { [data not shown]
    HTTP/1.1 200 OK
    Date: Sat, 25 Feb 2017 07:18:17 GMT
    Content-Type: text/html; charset=UTF-8
    Transfer-Encoding: chunked
    Connection: keep-alive
    Set-Cookie: __cfduid=ded56ddc949e214e99a041d43ed41b4721488007097; expires=Sun, 25-Feb-18 07:18:17 GMT; path=/; domain=.pcgameshardware.de; HttpOnly
    Set-Cookie: CFID=825212191;expires=Mon, 18-Feb-2047 07:18:17 GMT;path=/
    Set-Cookie: CFTOKEN=c34b0d427765f6c4-74226E30-A69D-2108-D41580A6F90392C1;expires=Mon, 18-Feb-2047 07:18:17 GMT;path=/
    Set-Cookie: CPTBP=7666491;domain=pcgameshardware.de;path=/
    X-UA-Compatible: IE=edge
    Cache-Control: max-age=0
    Expires: Sat, 25 Feb 2017 07:18:17 GMT
    X-Clacks-Overhead: GNU Terry Pratchett
    Vary: Accept-Encoding
    Set-Cookie: PCGHWLBCOOKIE=s1; path=/
    Cache-control: private
    Server: cloudflare-nginx
    CF-RAY: 336961e9c4bb6475-FRA
_cf_loadingtexthtml="";
  • Failed writing body (840 != 1220)
  • Failed writing data
  • Closing connection 0
    curl: (23) Failed writing body (840 != 1220)

Hi there,
I don't want to hijack this thread, but I encounter simmilar problems with different sites.

Especially pcgameshardware makes no problem, but heise does. Here's my curl head result:

  • Hostname was NOT found in DNS cache
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 2a02:2e0:3fe:1001:7777:772e:2:85...
  • Connected to www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85) port 80 (#0)

GET / HTTP/1.1
User-Agent: curl/7.38.0
Host: www.heise.de
Accept: /

< HTTP/1.1 301 Moved Permanently

  • Server nginx is not blacklisted
    < Server: nginx
    < Content-Type: text/html
    < Location: https://www.heise.de/
    < Last-Modified: Sat, 25 Feb 2017 12:04:01 GMT
    < Cache-Control: public,
    < Content-Length: 178
    < Accept-Ranges: bytes
    < Date: Sat, 25 Feb 2017 12:04:12 GMT
    < Age: 11
    < Connection: keep-alive
    < Vary: X-Forwarded-Proto,User-Agent,X-Export-Format,X-Export-Agent
    <
    { [data not shown]
    100 178 100 178 0 0 1340 0 --:--:-- --:--:-- --:--:-- 1390
  • Connection #0 to host www.heise.de left intact
    HTTP/1.1 301 Moved Permanently
    Server: nginx
    Content-Type: text/html
    Location: https://www.heise.de/
    Last-Modified: Sat, 25 Feb 2017 12:04:01 GMT
    Cache-Control: public,
    Content-Length: 178
    Accept-Ranges: bytes
    Date: Sat, 25 Feb 2017 12:04:12 GMT
    Age: 11
    Connection: keep-alive
    Vary: X-Forwarded-Proto,User-Agent,X-Export-Format,X-Export-Agent
301 Moved Permanently

301 Moved Permanently


nginx

I'm also on Mac OS Sierra and FF/Safari.

In addition I notice a very high cpu usage on my mac. This recently also happened with"csi.gstatic.com" ... It took ages until the website was loaded - every page! Maybe this helps, too, in resolving the issue.

Thx for any support. Cheers.
Axel

Hi there,
I don't want to hijack this thread

Please open a new one then.

Can you run a new debug, as the old one timed out. There may be an issues with IPv6 as it appears that your client is using that protocol.

Ok I've done a debug run again
Here is the token

fjozujyxt3

Okay, this looks like the bug we've found with some ISPs. They rotate out IPv6 addresses on schedule, sometimes daily, which causes an issue. When you installed Pi-hole, it detected the IPv6 address in use at that time, and that address ended in d00c:5a81 which is the value you'll find in /etc/setupVars.conf. However since that time, your IPv6 address has been changed, to ending in f420:d112, that is what ip addr would show.

The behaviour we would expect from this bug would be that some sites and assets would timeout and cause slow browsing. We are working on a solution for this problem.

1 Like

Okay :slight_smile: many thanks to your help!
So, the Pi-Hole should work normal when I update the IPv6 address by myself in the SetupVars.conf File?
I'm not a Pro in Coding but when you say that the Pi-Hole setup detects the Actual IPv6 adress, isn't it possible to make a simple script that would update that File one ore two times a day?

If you update the setupVars.conf and then run pihole -g to pull in those changes immediately. The problem with the cron approach and scripting is that if the IPv6 address changes and the script doesn't run until 6 hours later, then you have 6 hours of timeouts and the issue becomes troubleshooting a transient condition. There is the option of using hooks to check when the IP changes, but that's getting deeper into a users system than most would like us to go. It's also a regional issue, here where I live, my IPv6 allocation hasn't changed in over a year, and DT sounds like they change once a day. Hitting yet another moving target.