stunnel : SSL_connect: Peer suddenly disconnected
I am using stunnel to mount an azure nfs file share. The stunnel process log the following message Dec 18 17:55:20 vmubuntu18 stunnel: LOG3[23840]: SSL_connect: Peer suddenly disconnected The stunnel configure file is verifyChain = no debug = debug output = /etc/stunnel/microsoft/aznfs/nfsv4_fileShare/logs/stunnel_52.239.241.136.log pid = /etc/stunnel/microsoft/aznfs/nfsv4_fileShare/logs/stunnel_52.239.241.136.pid TIMEOUTidle = 61 [52.239.241.136] client = yes accept = 127.0.0.1:20049 connect = 52.239.241.136:2049 A trace with tcpdump display the following logs [cid:defde221-2fed-4b36-9480-0181f6f7d5a9] We observe a reset connection between azure server and my machine. Best regards Souheila
Hi Souheila, It does not look like your remote machine accepts TLS: $ *openssl s_client -connect 52.239.241.136:2049 * Connecting to 52.239.241.136 CONNECTED(00000003) 403754EAC87F0000:error:0A000126:SSL routines::unexpected eof while reading:../ssl/record/rec_layer_s3.c:696: Why exactly do you think that stunnel could be used to mount NFS file shares? Stunnel can be a TLS client, but not an NFS client. Those are _different_ protocols. Best regards, Mike On 12/18/25 6:15 PM, Souheila Hechaichi via stunnel-users wrote:
/I am using stunnel to mount an azure nfs file share. / /The stunnel process log the following message/ */Dec 18 17:55:20 vmubuntu18 stunnel: LOG3[23840]: SSL_connect: Peer suddenly disconnected/* / / /The stunnel configure file is/ /verifyChain = no/ /debug = debug/ /output = /etc/stunnel/microsoft/aznfs/nfsv4_fileShare/logs/stunnel_52.239.241.136.log/ /pid = /etc/stunnel/microsoft/aznfs/nfsv4_fileShare/logs/stunnel_52.239.241.136.pid/ /TIMEOUTidle = 61/ / / /[52.239.241.136]/ /client = yes/ /accept = 127.0.0.1:20049/ /connect = 52.239.241.136:2049 / /A trace with tcpdump display the following logs/ /We observe a reset connection between azure server and my machine./
Best regards Souheila
_______________________________________________ stunnel-users mailing list [email protected] To unsubscribe send an email [email protected]
Hey, I hope your help. The problem of 403754EAC87F0000:error:0A000126:SSL routines::unexpected eof while reading:../ssl/record/rec_layer_s3.c:696: is a bug in openssl version 3.x.x Whith my configuration OpenSSL 1.1.1f, the connection succeded but Its systematically closes [cid:a9ce4d8c-340b-42ba-9628-d4064d6771b3] And with tcpdump I observe a connection reset [cid:220c1431-e834-4932-a144-b72d24ecd539] Best regards; ________________________________ From: Michał Trojnara via stunnel-users <[email protected]> Sent: Thursday, December 18, 2025 8:24 PM To: [email protected] <[email protected]> Subject: [stunnel-users] Re: stunnel : SSL_connect: Peer suddenly disconnected Hi Souheila, It does not look like your remote machine accepts TLS: $ openssl s_client -connect 52.239.241.136:2049 Connecting to 52.239.241.136 CONNECTED(00000003) 403754EAC87F0000:error:0A000126:SSL routines::unexpected eof while reading:../ssl/record/rec_layer_s3.c:696: Why exactly do you think that stunnel could be used to mount NFS file shares? Stunnel can be a TLS client, but not an NFS client. Those are different protocols. Best regards, Mike On 12/18/25 6:15 PM, Souheila Hechaichi via stunnel-users wrote: I am using stunnel to mount an azure nfs file share. The stunnel process log the following message Dec 18 17:55:20 vmubuntu18 stunnel: LOG3[23840]: SSL_connect: Peer suddenly disconnected The stunnel configure file is verifyChain = no debug = debug output = /etc/stunnel/microsoft/aznfs/nfsv4_fileShare/logs/stunnel_52.239.241.136.log pid = /etc/stunnel/microsoft/aznfs/nfsv4_fileShare/logs/stunnel_52.239.241.136.pid TIMEOUTidle = 61 [52.239.241.136] client = yes accept = 127.0.0.1:20049 connect = 52.239.241.136:2049 A trace with tcpdump display the following logs [cid:[email protected]] We observe a reset connection between azure server and my machine. Best regards Souheila _______________________________________________ stunnel-users mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
participants (2)
-
Michał Trojnara -
Souheila Hechaichi