On 12/09/2019 07:45, Johann Klammer wrote:
On 09/11/2019 07:05 PM, R D S wrote:

"The page you are trying to view cannot be shown because the authenticity of the received data could not be verified"

What would be the process for diagnosing this problem? Could it possibly be at ISP level?

Might be a SSL/HTTPS booboo. It's not always on your side. A lot of webservers seem rather broken in that they more or less randomly cut connections. try to bring up your browsers error console.
The error messages are not always very telling and sometimes outright arbitrary,
so you might have to continue with tshark
or similar packet capture tool and maybe ssldump, openssl, s_client to try and replicate
the failing request or which part of it triggers the bug in /their/ web server. Then you
write angry emails and hope they fix it.



Does the below mean anything to anyone?

Analytics utag.js:209
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIURI.host]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
resource://gre/modules/WebRequest.jsm :: canModify :: line 896" data:
no] (unknown)
[Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIURI.host]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
resource://gre/modules/WebRequest.jsm :: canModify :: line 896" data: no]