Morph browser - The connection is untrusted (for almost every website)
I am on the dev channel of Ubuntu Touch. I had a Nexus 5 for a few months and when on my home network the Morph browser was almost unusable, where I was constantly getting the message 'The connection is untrusted'.
I recently updated to the Xperia X and the problem went away for a month and has returned recently. I am using an adblocker inside my network. I get so many 'The connection is untrusted' messages that I have to always be on my mobile data connection for a responsive Morph browser experience.
Is anyone else experiencing this? or is there something I can do the help this behaviour of Morph browser?
That sounds like a network configuration issue rather than a UT or Morph browser issue.
The "connection is untrusted" message comes up in browsers when they connect to a SSL/TLS excrypted site (https:// via port 443, basically all the web these days), but do not know the certificate. This could be because the ca-certificate library is missing on the device, but for UT and really any consumer device this isn't the case (and then you would have the issue everywhere even on your mobile data plan).
But more typically this happens on self-signed websites, or connections that somehow got compromised by a man-in-the-middle. The latter is probably the issue in your case. Optimistically I would not assume the worst (that your firewall got hacked), but rather that you misconfigured your firewall or ad-blocker somehow so that it ends up with this problem.
Thank you for taking the time to reply.
Whats weird is that I do not have this issue on any of my other devices on this LAN, ie my thinkpad, an android phone, numerous tablets etc... It only apears when using the Morph browser on Ubuntu Touch.
I am using a pfSense router with pfBlockerNG installed. But like I mentioned previously, the problem disappeared for a month and then came back.
I'll have a look at my setup but its difficult to troubleshoot as I do not experience this on any other device.
Hmm, I am guessing, but maybe there is some completely new ca-certificate that your pfsense is using that other devices already got via an update, but UT is lagging behind in that regard?