When using multiple profiles I get SSL warnings for all https connections in the non-default profile
macOS: 10.14.5 FF: 67.0.2 (64-bit) Avast Security: 13.12
I created a new profile using the Profile Manager (about:profiles). I selected a directory for it next to the "xxxxx.default" directory (i.e. in "/Users/xxx/Library/Application Support/Firefox/Profiles/" parent directory).
When I launch the new profile, I get the following message when opening any HTTPS sites:
"Software is Preventing Firefox From Safely Connecting to This Site
en.wikipedia.org is most likely a safe site, but a secure connection could not be established. This issue is caused by Avast trusted CA, which is either software on your computer or your network."
I can add a security exception one by one except for sites that use HTTP Strict Transport Security in which case it's impossible to open the given site. How can this be resolved without disabling HTTPS scanning in Avast?
Cheers, Marcel
All Replies (7)
Please uninstall Avast, it's a terrible anti-virus program and does so many bad things (including HTTPS Scanning).
Hi Tyler,
Thanks for your input and I will consider it but overall your answer is not helpful because it does not address the problem. What I'm trying to get an answered is:
Why Avast has no problem in the default profile but it does in additional profiles?
How to fix this?
Saying about Avast Security that it is terrible is an opinionated answer. I want to find out the reasons behind the different behaviour of Firefox in different profiles.
Modified by marekful
I'm not sure why it's happening to one profile and not the others, but the root issue is Avast, which means uninstalling it will fix the issue.
Avast Security does efficiently block malicious scripts and websites. Just saying to uninstall it is unprofessional. What is your suggestion as an alternative?
I'd suggest you use uBlock Origin, and then run monthly scans with Malwarebytes. Since you use a Mac there are less concerns with viruses, and it's more about keeping all software up to date.
OK, thanks. I still consider this a problem with Firefox though since it doesn't affect the default profile and would like to learn why it's happening.
After restarting the OS the problem didn't persist...