Error code: SSL_ERROR_RX_RECORD_TOO_LONG

[domadmin]

I have some users getting SSL/TLS errors in their browser when accessing the Zimbra web interface using the hostname. If I enter the IP address of the server then it loads after bypassing the certificate name mismatch error you would expect to see.

Their computers resolve the addresses for the server just fine, and this happens on all browsers. The error listed by firefox is a little more discriptive.

Code: Select all

Secure Connection Failed

An error occurred during a connection to zim.xxx.com. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

So far I have not found any rhyme or reason for this. Just curious if anyone knows of anything off the top their heads.

Zimbra 8.8.15_GA_4372 (build 20220726082327)
CentOS 7
Two network interfaces on separate ISPs (I have tried accessing each IP individually with the same results)

[adrian.gibanel.btactic]

Code: Select all

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

When this error happens with Apache it usually means that http is being serviced in an https port.

So if you telnet to the 443 port you should be able to do

Code: Select all

GET /

and you will get a plain http response instead of the https expected response.
Using:

Code: Select all

http://mail.example.net:443

on your browser should also do the trick and show you a non-encrypted http page which you do not want.

So there's something probably wrong on the proxy port configuration.

Check Ports - Zimbra Wiki , Proxy Guide - Zimbra Wiki and Installing , Configuring, Disabling the Zimbra Proxy - Zimbra Wiki.

[domadmin]

Thanks, I will give this a shot tomorrow when I am back in the office. Since this only happens to some users periodically, I have to remote into their machines to run these tests. The server responds as you would expect on every device I own. Windows, Linux, Android, etc