FS#62577 - [stunnel] can not connect to internet after upgrading stunnel 5.50-1 to 5.51-1

Attached to Project: Community Packages
Opened by Ali (strongsaxophone) - Thursday, 09 May 2019, 09:22 GMT
Last edited by Balló György (City-busz) - Sunday, 01 September 2019, 08:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Can not connect to internet after upgrading stunnel 5.50-1 to 5.51-1 and the log through journalctl -xe is:

"
May 09 13:22:23 archlinux stunnel[469]: LOG5[1819]: Connection reset: 287 byte(s) sent to TLS, 0 byte(s) sent to socket
May 09 13:22:23 archlinux stunnel[469]: LOG5[1820]: Service [proxy] accepted connection from 127....
May 09 13:22:23 archlinux stunnel[469]: LOG5[1820]: s_connect: connected 107....
May 09 13:22:23 archlinux stunnel[469]: LOG5[1820]: Service [proxy] connected remote server from 192.....
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: transfer() loop executes not transferring any data
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: please report the problem to Michal.Trojnara@stunnel.org
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: stunnel 5.51 on x86_64-pc-linux-gnu platform
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: Compiled/running with OpenSSL 1.1.1b 26 Feb 2019
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: protocol=TLSv1.2, SSL_pending=0
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: sock_open_rd=Y, sock_open_wr=Y
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: SSL_RECEIVED_SHUTDOWN=n, SSL_SENT_SHUTDOWN=n
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: sock_can_rd=n, sock_can_wr=n
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: ssl_can_rd=n, ssl_can_wr=n
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: read_wants_read=Y, read_wants_write=n
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: write_wants_read=n, write_wants_write=n
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: shutdown_wants_read=n, shutdown_wants_write=n
May 09 13:22:24 archlinux stunnel[469]: LOG3[1820]: socket input buffer: 0 byte(s), TLS input buffer: 0 byte(s)
May 09 13:22:24 archlinux stunnel[469]: LOG5[1820]: Connection reset: 287 byte(s) sent to TLS, 0 byte(s) sent to socket
"


Additional info:
package version(s) : stunnel 5.51-1



Steps to reproduce: Upgrade stunnel 5.50-1 to 5.51-1
This task depends upon

Closed by  Balló György (City-busz)
Sunday, 01 September 2019, 08:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  stunnel 5.54
Comment by Isaac Newman (newmanisaac) - Thursday, 09 May 2019, 13:39 GMT
This may have been fixed upstream in version 5.52 or 5.53. I was having what appears to be the same problem and upgrading to 5.53 solved it.
Comment by Sergej Pupykin (sergej) - Monday, 20 May 2019, 14:18 GMT
Can confirm that updating to stunnel-5.53 solves this issue
Comment by Eric Wang (enihcam) - Wednesday, 22 May 2019, 05:45 GMT
The latest version is 5.54 now.
Comment by Jay Somedon (jsomedon) - Thursday, 23 May 2019, 20:40 GMT
Had exact same issue in 5.51 and solved by upgrading to 5.54.

Loading...