Created attachment 394424 [details] This is how page looks like after nearly 50s of loading. Hi folks, first of all thanks for wonderfull distro you have made! The problem I'm observing in last few weeks is that wiki.gentoo.org is loading in order of seconds and minutes. After all, only plain html page is loaded without js - please see the attachment. This problem can be observed on several locations here in Czech, however it looks it is related to certain ISP, the 'o2'. Note that several browsers were tested with the same results. I have contacted the ISP with the details, but didn't hear from them yet. This is kind of strange behavior and I'm filling this bug in hope that we can find the solution. Here is some related informations: $ ping wiki.gentoo.org PING geese.gentoo.org (204.187.15.5) 56(84) bytes of data. 64 bytes from 204.187.15.5: icmp_seq=1 ttl=50 time=198 ms 64 bytes from 204.187.15.5: icmp_seq=2 ttl=52 time=202 ms 64 bytes from 204.187.15.5: icmp_seq=3 ttl=52 time=201 ms # tracepath 204.187.15.5 1?: [LOCALHOST] pmtu 1500 1: 192.168.8.138 0.859ms 1: 192.168.8.138 0.705ms 2: 208.9.broadband.iol.cz 0.953ms pmtu 1492 2: 88.103.200.43 21.467ms 3: 88.103.203.1 23.725ms asymm 5 4: 194.228.190.1 22.636ms 5: 194.228.190.193 22.482ms 6: no reply 7: Xe0-0-8-0-grtfraix4.red.telefonica-wholesale.net 30.878ms 8: no reply 9: xe-3-2-1.van10.ip4.gtt.net 209.564ms asymm 13 10: 10ge3.edge2.van.gt.net 242.196ms asymm 14 11: no reply 12: no reply 13: no reply 14: no reply ... Thanks
Your screenshot indicates you're having issues loading the central stylehseets. Can you load this? https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com/tyrian.min.css
(In reply to Alex Legler from comment #1) > Your screenshot indicates you're having issues loading the central > stylehseets. > > Can you load this? > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > rackcdn.com/tyrian.min.css Correct, no css, no js is loaded. The link you've provide cannot be loaded at all: "Server not found Firefox can't find the server at 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com."
Okay, so that's akamai that you cannot reach. What happens when executing this? curl -k -H 'Host: 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com' https://23.45.101.69/tyrian.min.css (one line)
(In reply to Alex Legler from comment #3) > Okay, so that's akamai that you cannot reach. > > What happens when executing this? > curl -k -H 'Host: > 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com' > https://23.45.101.69/tyrian.min.css > (one line) This will download the css and print it on stdout, like this: $ curl -k -H 'Host: 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com' https://23.45.101.69/tyrian.min.css .navbar-default{background-image:-webkit-linear-gradient(top, #54487a 0, #493f6a 100%);background-image:-o-linear-gradient(top, #54487a 0, #493f6a 100%);background-image:linear-gradient(to bottom, #54487a 0, #493f6a 100%);background-repeat:repeat-x;filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#ff54487a', endColorstr='#ff493f6a', GradientType=0)}@font-face{font-family:'Open Sans';font-style:normal;font-weight:400;src:local('Open Sans'),local('OpenSans'),url(OpenSans-Regular.woff) format('woff')}@font-face{font-family:'Open Sans';font-style:normal;font-weight:600;src:local('Open Sans Semibold'),local('OpenSans-Semibold'),url(OpenSans-Semibold.woff) format('woff')}@font-face{font-family:'Open Sans';font-style:normal;font-weight:700;src:local('Open Sans Bold'),local('OpenSans-Bold'),url(OpenSans-Bold.woff) format('woff')}@font-face{font-family:'Open Sans';font-style:italic;font-weight:400;src:local('Open Sans Italic'),....
Um, okay. Then how about curl -v https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com/tyrian.min.css ?
(In reply to Alex Legler from comment #5) > Um, okay. Then how about curl -v > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > rackcdn.com/tyrian.min.css ? $ curl -v https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com/tyrian.min.css * Hostname was NOT found in DNS cache
(In reply to Marek Matej from comment #6) > (In reply to Alex Legler from comment #5) > > Um, okay. Then how about curl -v > > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > > rackcdn.com/tyrian.min.css ? > > $ curl -v > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > rackcdn.com/tyrian.min.css > * Hostname was NOT found in DNS cache followed by (eventually) 'curl: (6) Couldn't resolve host'? You cannot resolve the DNS name. Finding out if that's a problem of your machine, or a caching resolver, or your ISP isn't really on-topic here, as the server itself is fine. If need be, please consult the support venues of either your OS (if that's Gentoo: IRC, Mailing Lists or Forums) or your ISP for further instructions on debugging DNS.
(In reply to Alex Legler from comment #7) > (In reply to Marek Matej from comment #6) > > (In reply to Alex Legler from comment #5) > > > Um, okay. Then how about curl -v > > > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > > > rackcdn.com/tyrian.min.css ? > > > > $ curl -v > > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > > rackcdn.com/tyrian.min.css > > * Hostname was NOT found in DNS cache > > followed by (eventually) 'curl: (6) Couldn't resolve host'? > > You cannot resolve the DNS name. Finding out if that's a problem of your > machine, or a caching resolver, or your ISP isn't really on-topic here, as > the server itself is fine. If need be, please consult the support venues of > either your OS (if that's Gentoo: IRC, Mailing Lists or Forums) or your ISP > for further instructions on debugging DNS. You're right, I did not wait for timeout: $ curl -v https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com/tyrian.min.css * Hostname was NOT found in DNS cache * Could not resolve host: 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com * Closing connection 0 curl: (6) Could not resolve host: 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com This is definitely not the problem of machine. I check this with multiple machines. Using Gentoo and Calculate linux on my machines. The issue is confirmed by several users on different OSes and platforms, which has the same ISP in common. o2.cz still didn't reply on this issue, so I'll wait and then ask again. Thanks for your time.
(In reply to Marek Matej from comment #8) > (In reply to Alex Legler from comment #7) > > (In reply to Marek Matej from comment #6) > > > (In reply to Alex Legler from comment #5) > > > > Um, okay. Then how about curl -v > > > > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > > > > rackcdn.com/tyrian.min.css ? > > > > > > $ curl -v > > > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > > > rackcdn.com/tyrian.min.css > > > * Hostname was NOT found in DNS cache > > > > followed by (eventually) 'curl: (6) Couldn't resolve host'? > > > > You cannot resolve the DNS name. Finding out if that's a problem of your > > machine, or a caching resolver, or your ISP isn't really on-topic here, as > > the server itself is fine. If need be, please consult the support venues of > > either your OS (if that's Gentoo: IRC, Mailing Lists or Forums) or your ISP > > for further instructions on debugging DNS. > > You're right, I did not wait for timeout: > > $ curl -v > https://1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5. > rackcdn.com/tyrian.min.css > * Hostname was NOT found in DNS cache > * Could not resolve host: > 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com > * Closing connection 0 > curl: (6) Could not resolve host: > 1b9a50f4f9de4348cd9f-e703bc50ba0aa66772a874f8c7698be7.ssl.cf5.rackcdn.com > > > This is definitely not the problem of machine. I check this with multiple > machines. Using Gentoo and Calculate linux on my machines. > > The issue is confirmed by several users on different OSes and platforms, > which has the same ISP in common. > > o2.cz still didn't reply on this issue, so I'll wait and then ask again. > > Thanks for your time. After changing nameserver to other than o2 default, problem is fixed. o2.cz guys has enough information to trace the problem, so maybe they'll eventualy fix it also. Thanks for your time Alex.
