Solved Page Fails to Load on BBC

[Priest72]

This post is deleted!

[JacobDavis]

This is indeed strange, can you access this page if you are using incognito mode in another browser?

[Pesala]

@JacobDavis I can access the pages in a regular window, but the error message sometimes appears for a second or two.

Unless I use a New Private Window all day, I might not be able to reproduce it.

[Pesala]

Still happening. Here is another screenshot.

[Catweazle]

@Pesala Maybe an DNS problem ????
No problems here (Quad9 DNS)

[Pesala]

@Catweazle I have since enabled the setting:

DNS to Help Resolve Navigation Errors

However, I still see the error.

[Catweazle]

@Pesala , no the settings of Vivaldi, the used DNS in your system network settings. If your used DNS can't resolve the direction, Vivaldi can't change this

[Mrchriz82]

I don't think this is a Vivaldi problem. I'm seeing the same in Chrome specifically the BBC site. It seems to redirect to the correct page after a few seconds here. I'm on now broadband in the UK and haven't played with DNS as yet. This thread came up when I Google searched for the issue so thought I'd mention my experience.

[Pesala]

@Mrchriz82 Thanks for the reply. I think we can blame it on the Russians. They may be launching Denial of Service attacks.

[Pesala]

Still happening

[mib2berlin]

@Pesala
Hi, all links open immediately for me, even I set my VPN location to the UK.
The page switch to https://www.bbc.com if I open the link of your first post not https://www.bbc.co.uk

Cheers, mib

[Pathduck]

From what I understand ERR_FAILED means the connection fails early on, during network socket creation, before DNS resolve and TCP setup. So most likely candidate then is something on the local system aborting connections before they get an further, like a local VPN/Proxy or similar, possibly an AV/security solution.

You mentioned custom DNS and using DNSCrypt. Do you get the same errors if these are turned off? I.e. turn off DoH and turn off DNSCrypt.

Also, keep the devtools open while testing, and when it fails, do you see anything in the network log or console?

[Pesala]

@Pathduck Earlier, I enabled it to see if it would help:

DNS to Help Resolve Navigation Errors

It made no difference, so I disabled it again. I have re-enabled it again, and will see if the error recurs.

[Pesala]

@Pesala said in Page Fails to Load on BBC:

@Catweazle I have since enabled the setting:

DNS to Help Resolve Navigation Errors

However, I still see the error.

[Pathduck]

@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?

[Pesala]

@Pathduck Thanks. I have now done that. Let us see if the problem returns.

[Catweazle]

@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.

[Pesala]

That did not take very long. The problem has not disappeared.

[TbGbe]

@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.

[Pathduck]

@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.