Your error message indicate that the TCP connection was successful, but the handshake failed.
I guess this can be due to several reasons including a firewall, openssl version or TLS version e.t.c. But it is impossible say the reason by looking at this error message.
By the way which TLS version is supported, try specifying the version [-tls1] [-tls1_1] [-tls1_2] [-tls1_3], for example:-
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
# cat /var/log/messages | egrep -i "error|warn|critical|panic|exceed|alert|down|up"
Jul 10 09:30:06 plbp1s nanny: shutting down 202.61.9.147:443 due to connection failure
Jul 10 10:30:06 plbp1s nanny: shutting down 202.61.9.149:443 due to connection failure
443 is I understood it is port... (1 Reply)
Can someone please give me the conf file line to allow access to myexample.com and only that site, and only through http and https?
So far I have only that site accessible via http, but all https sites are opened.
Squid 3.1 on Cent 6
---------- Post updated at 12:06 PM ---------- Previous... (0 Replies)
I am trying to install Sun Java Web Server using an ordinary user with no root/sudo rights.
I need to allow this web server to use ports 80 and 443. How can this be done?:confused: (1 Reply)
Hi,
I need to call an API (GetUsageDetails)from inside a shell script which takes an input argument acct_nbr.
The output of API will be like :
<usageAccum accumId="450" accumCaptn="PM_125" inclUnits="1410.00" inclUnitsUsed="744.00" shared="true" pooled="false" prorated="false"... (1 Reply)
Hello,
I have a server in our DMZ that only has ports 80 and 443 open to the public networks. It runs webmail for our 10K employees' accounts. It's not necessary for our employees to access the server from anywhere except North America so I have blocked access from most of the world due to... (5 Replies)
Discussion started by: randomxs
5 Replies
LEARN ABOUT MINIX
ssl_connect
SSL_connect(3SSL) OpenSSL SSL_connect(3SSL)NAME
SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
SYNOPSIS
#include <openssl/ssl.h>
int SSL_connect(SSL *ssl);
DESCRIPTION
SSL_connect() initiates the TLS/SSL handshake with a server. The communication channel must already have been set and assigned to the ssl
by setting an underlying BIO.
NOTES
The behaviour of SSL_connect() depends on the underlying BIO.
If the underlying BIO is blocking, SSL_connect() will only return once the handshake has been finished or an error occurred.
If the underlying BIO is non-blocking, SSL_connect() will also return when the underlying BIO could not satisfy the needs of SSL_connect()
to continue the handshake, indicating the problem by the return value -1. In this case a call to SSL_get_error() with the return value of
SSL_connect() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking
appropriate action to satisfy the needs of SSL_connect(). The action depends on the underlying BIO. When using a non-blocking socket,
nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must
be written into or retrieved out of the BIO before being able to continue.
RETURN VALUES
The following return values can occur:
<0 The TLS/SSL handshake was not successful, because a fatal error occurred either at the protocol level or a connection failure occurred.
The shutdown was not clean. It can also occur of action is need to continue the operation for non-blocking BIOs. Call SSL_get_error()
with the return value ret to find out the reason.
0 The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call
SSL_get_error() with the return value ret to find out the reason.
1 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established.
SEE ALSO SSL_get_error(3), SSL_accept(3), SSL_shutdown(3), ssl(3), bio(3), SSL_set_connect_state(3), SSL_do_handshake(3), SSL_CTX_new(3)1.0.1e 2014-08-06 SSL_connect(3SSL)