Re: Jabberd2: nss: Handshake failed

Robb, hello. Old SSL and failed to start, but STARTTLS (5222 TLS) is working very well. This is not exactly what we need, because we use VPN. I think you need to fix the problem, because it is Thank you for your time. 11.04.2016, 13:24, "Eion Robb" : > According to >

Re: Jabberd2: nss: Handshake failed

I also tested the system in a self-signed certificate of different lengths (384 - 4096). It also did not affect the situation. ps I use googlt translator. It may incorrectly translate. I beg your forgiveness for it. 11.04.2016, 13:24, "Eion Robb" : > According to >

Re: Jabberd2: nss: Handshake failed

Yes, I have seen this information. I have to really understand why this error occurs, as I successfully connect to a host other tools. It may make sense to debug the library itself and its NSS tools. By the way, try to collect pidgin supporting gnutls also did not give a positive result.

Re: Jabberd2: nss: Handshake failed

According to https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/SSL_functions/sslerr.html error -12263 from NSS means: SSL_ERROR_RX_RECORD_TOO_LONG -12263 "SSL received a record that exceeded the maximum permissible length." This generally indicates that the remote peer system has a

Re: Jabberd2: nss: Handshake failed

ports to the server are closed. If necessary, we will open. Please let us know one or more IP addresses. 11.04.2016, 11:07, "Eion Robb" : > Hi there, > > Just wondering if you've tried using the "NSS Preferences" plugin in Pidgin > to adjust what methods of TLS/SSL encryption

Jabberd2: nss: Handshake failed

Dear support team, good afternoon. I'm having serious problems with the product. The fact that we are trying to make a stand-alone Jabber server. As a customer of our employees are already using Pidgin. We believe that this is the best client IM. But, unfortunately, there was an error SSL. In