Solved Page Fails to Load on BBC
-
@Pesala said in Page Fails to Load on BBC:
@Catweazle I have since enabled the setting:
DNS to Help Resolve Navigation ErrorsHowever, I still see the error.
-
@Pesala I don't think that setting is relevant here. But I'd still keep it off, it makes no difference, I always keep it off.
Better to try disabling DoH and DNSCrypt.
I.e
chrome://settings/security
and turn off "Use secure DNS". This will make the browser use your local DNS through your ISP.How you turn off DNScrypt I have no idea, maybe just exit the client?
-
@Pathduck Thanks. I have now done that. Let us see if the problem returns.
-
@Pathduck , I use DNScrypt in the SO and I don't have any problems with it. I think it's only a problem with the DNS settings in Vivaldi, if not, it can be only the DNS settings of the ISP which can't resolve the URL.
-
That did not take very long. The problem has not disappeared.
-
@Pesala I can access the site and browse through News etc with no problems.
Just default DNS settings, using my ISP.
One thing you didn't mention, are you "logging in" to bbc - I just browsed without login.
-
@Pesala OK that's too bad
I think you'll need to bring out the big guns...
-
Try keeping Devtools (F12), network tab, open while browsing to recreate the issue. When it happens, note if you see anything in the network log or console tab. Should only be one entry if it fails, click it and note down any messages.
-
Try saving a network log from:
vivaldi://net-export
Since it might take a while for the issue to appear, the log might be quite large. Also probably an idea to keep DoH/DNSCrypt disabled to simplify things in the log.
If you want you can share the log with me and I can have a look if I can spot anything. Shouldn't contain any private info apart from local IPs and URL visited. Recreate the issue in a separate clean profile to let you continue browsing in your regular one if you need to, depending on how long this issue takes to recreate.
-
-
-
@Pesala Thanks, I'll have a look and update as I find stuff.
First thing, from your screenshot, you get ERR_BLOCKED_BY_CLIENT. Only way to get these is AFAIK from an adblocker running. In this case it looks like those are trackers usually blocked so shouldn't matter for site functionality anyway.
Update: Do you know the URL of the page that failed? I forgot to say it would help to know that request actually failed?
Update: Seeing several errors like this:
t=1188 [st=0] +SOCKET_ALIVE [dt=1] --> source_dependency = 1 (NETWORK_QUALITY_ESTIMATOR) t=1188 [st=0] +UDP_CONNECT [dt=1] --> address = "[2001:4860:4860::8888]:53" t=1189 [st=1] -UDP_CONNECT --> net_error = -109 (ERR_ADDRESS_UNREACHABLE) t=1189 [st=1] -SOCKET_ALIVE
But apparently this is just Chromium trying to determine IPv67 connectivity by connecting to Google servers, so good that it fails.
Update: The only instances of ERR_FAILED I find are like this:
t=11572 [st= 0] HTTP_CACHE_DOOM_ENTRY [dt=1] --> net_error = -2 (ERR_FAILED)
Apparently something with retrieve from cache failing? Not sure. You have tried to clear cache+cookies from BBC?
Update: I also find no entries from for instance
chartbeat.com
ormybbc-analytics
in the logs. Did you capture this log while the issue was reproduced and also the image above was captured?Update: That's all I was able to see from the logs. It's important that the log is captured and saved when the issue occurs, not sure if I was clear on that. And also to make a note of the URL when you get the ERR_FAILED message so it's easier to find, as well as the approximate time the error occurred.
Then when it fails, open devtools and do a forced reload (Ctrl+R), then look at the console and network tabs.
-
@Pathduck I had a lot more errors today, so I have cleared all BBC cookies. Let's see if that solves the problem.
Edit: The problem is still occurring.
-
FWIW privacy implication of enabling:
Resolving navigation errors with DNS
The Google DNS Service will give you the IP address of the website you want to visit in case your ISP (Internet Service Provider) fails to do so properly (in some cases the ISP may have faulty DNSs).
For some of you, this service will not be extremely useful, as your ISP is probably doing a good job already. For others, it will be helpful, e.g. if you live in parts of the world where ISPs routinely return errors in order to blacklist banned websites. With the Google DNS Service enabled, you have a workaround that gives you access to websites blocked via DNS.
The privacy implications of this, of course, are that they also see your typos, like “vvaldi.com” and can, therefore, work out what website you are trying to visit.
The Google DNS server addresses – 8.8.8.8 and 8.8.4.4 – have been hardcoded into Chromium, on which Vivaldi is built. In the future, we may consider switching to something else, for example, Cloudflare’s 1.1.1.1. For now, you can opt out by unchecking “Use Google DNS Service to Help Resolve Errors” in the Privacy settings.
[Source: Vivaldi’s powerful privacy settings] -
@yojimbo274064400 Yes, I know that it is better to disable it, but I was willing to forgo some privacy to get fewer errors. Since enabling the setting does not solve the issue, I have disabled it again.
-
This post is deleted! -
@Pesala Yeah, really strange issue, and would expect more reports if this was a general problem with Vivaldi + BBC.
Do you only get this issue if you're signed in to the site?
I think the best way forward is to capture a HAR log while recreating the issue. Make sure that "Preserve Log" is selected and try to recreate the issue with as few page loads as possible, then save the file, zip it and share somewhere. If you're signed in, might be an idea to stay signed out since it might contain data like cookies+session data.
Some guides:
https://kb.acronis.com/content/58514
https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting -
@Pathduck I lack the time and skills to diagnose this issue. The best I can do is report it with my specs and settings and see if anyone else can reproduce it. It still occurs if I am logged out.
It still happens without any ad-blocking.
There is no point filing a bug report unless someone else encounters the issue.
-
@Pesala Fair enough, I only read the BBC news (daily) but obviously can't access the iPlayer or any UK-only services.
I've just signed up with a throwaway email and will try a bit.
It should only take 10 mins or so to create a HAR file, at least if the issue happens as often as it seems to for you.
-
This post is deleted! -
PPesala marked this topic as a question on
-
I have not seen this issue again for a while. Maybe it was fixed by some change in updates, or the Russians are too busy to harass the BBC at the moment.
-
PPesala has marked this topic as solved on