Nuno Silva wrote:
Could it be a clock sync problem? Your clock seems to be set to 2019-11-30, not 2019-10-30. That would explain the "out-of-date".
I think that the clock is the most likely issue, especially if the site that OP is trying to connect to is a financial provider. Inaccurate clocks are disruptive of some services (including certs), and financial institutions are especially sensitive in that area.
For what it is worth, I have a Linux box that I have in a virtual machine, and I don't have it active often. On occasions when I start it up and try to update the packages list from repositories, I sometimes see all sorts of errors about invalid certs (similar to what's been mentioned). On closer inspection, the problem always comes from this VM not keeping time well when it's inactive, and where the calendar is weeks off, usually behind. As soon as I get the calendar showing the correct time, then there's no problems.
With a full computer (rather than virtual machine, as I've described here), historically, the most common reason for a clock problem is a CMOS battery that's nearly out of power. That battery is what allows your BIOS to maintain system configuration when the power is off, and that includes the system clock as well. It's been years since I've seen that kind of problem, and I think it's pretty rare on modern machines (especially ones with UEFI rather than BIOS), but it's not impossible, either.
In any case, this is illustrative of why it's essential to have your system clock that's accurate, within a few seconds.(And why most modern computers make regular checks with time servers).
Smith _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
