On 6/3/10, Daniel <[email protected]> wrote: > Lee wrote: >> Is there any way to get past this problem: >> >> ------------------------------------------------ >> >> Secure Connection Failed >> >> An error occurred during a connection to xx.xx.xx.xx:nnn. >> >> SSL peer reports incorrect Message Authentication Code. >> >> (Error code: ssl_error_bad_mac_alert) >> >> * The page you are trying to view can not 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. Alternatively, use the command found in the help menu to >> report this broken site. >> >> ------------------------------------------------ >> >> and SeaMonkey refuses to connect to the web server. >> >> For whatever it's worth, this is at work, IE makes the connection >> without any fussing& I have no idea what (or if) >> certificates/certificate servers have been added to IE. >> >> Thanks, >> Lee
> Lee, do you need to be using SSL?? I think so? It's a server with a web interface using a non-standard port that I get to with https://servername:port/ Probably not surprising - Firefox reports the same error: SSL peer reports incorrect Message Authentication Code. (Error code: ssl_error_bad_mac_alert) I'm not sure what changed between yesterday & today, but IE now says The security certificate presented by this website was not issued by a trusted certificate authority. The security certificate presented by this website was issued for a different website's address. but it still allows me to connect to the server. Thanks, Lee _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
