Currently our only experience of this error is in conjunction with the error AssertionError [ERR_ASSERTION].
Thorium is built using Electron and Node.js, so it uses Node's built-in list of trusted authorities rather than the one on the user's OS, which makes it pickier than a browser about what it will accept. It does not respect the operating system's certificate store so users cannot resolve the issue themselves. If the user's operating system trusts a certificate that Node does not include in its list of trusted authorities (like an organization's own certificate), this is likely the result.
The likely culprits are:
- Antivirus / endpoint security performing HTTPS inspection: Kaspersky, ESET, Bitdefender, Avast are the usual Windows suspects. They intercept encrypted traffic to scan it, which breaks apps like Thorium.
- Corporate proxy or firewall doing the same thing (Zscaler etc.)
- Captive portal (hotel / café wifi)
If you receive this error:
- If you are using a public WiFi connection, please switch to a different WiFi network if possible.
- If you are using a VPN, please disconnect from the VPN and retry the download.
- If you are using an Antivirus or firewall that may be causing the issue please temporarily deactivate it and retry the download. (Please remember to re-enable it after)
If you can't disable these, or don't want to, or following all of these steps does not resolve the issue, please contact Thorium Reader's developer EDR Lab for support. As Thorium is third party software we have limited ability to provide support.
Comments
0 comments
Article is closed for comments.