I've just hit a new problem with Seamonkey 2.30.
Just finished installing a new small Linux server. I needed to access
the web page on the server. Fired up Seamonkey, entered https:<IP> and
the port number. And got this message:
"An error occurred during a connection to test1:10000. The key does not
support the requested operation. (Error code: sec_error_invalid_key)
The page you are trying to view cannot be shown because the authenticity
of the received data could not be verified.
Please contact the web site owners to inform them of this problem."
And it won't let me log on. Wonderful.... I know the key is not offical.
And I don't care - its on my internal network. At least in older
versions I was given a warning and allowed to make an exception. Seems
that I'm now to be "protected", even when I do know exactly what I'm doing!
Firefox exhibits exactly the same over protective nonsense. In the end,
I had to use Chromium to access the setup page.
Is this expected behaviour, or is it something I've (yet again) got
messed up in my profile?
I've used Seamonkey since the old Mozilla suite. But if this is about to
become standard, it is about to get dropped. Permanently!
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
Firefox/33.0 SeaMonkey/2.30
Paul.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
