Kapersky is intercepting https traffic. You either need to disable this or
import the Kapersky certificate into SeaMonkey. I am not using Kapersky and
would never allow this to happen anyway so I can't help you with locating the
certificate. It is essentially a Kapersky problem because the installer does
not do this for other than the few browsers it knows.
FRG
Henrik37 wrote:
David E. Ross wrote:
On 12/18/2017 1:17 PM, Henrik37 wrote:
Oops - after a complete reboot, SM 2.49.1 does appear to have solved the
problem.
Does anyone have any idea or explanation about what has been going on?
Oops again - SM 2.49.1 DIDN'T fix my problem after all. More ideas sought.
Have you tried starting SeaMonkey in Safe Mode?
Tried safe mode. Still the same error messages.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
