Hi,  

First apologies I posted this question on a google stunnel group, but I realise that does not have much activity, so posting here also.


I am trying to get stunnel up and running and getting the error in the subject. The full error text is:
 
"SSL_accept: ssl/record/ssl3_record.c:354: error:0A00010B:SSL routines::wrong version number"
 
I have a simple service which seems to load fine. I have stunnel up at the "server side" on a VM in azure and if I telnet to the VM public address I can see the activity in the stunnel logs on the VM, so I know at least a pipe is open.
 
I can hit the port server side and see the log activity in stunnel also.
 
If I try a telnet to the local stunnel accept port. I see the error above.
 
 
This is the full log.
 
2023.08.23 11:01:04 LOG7[service]: Found 1 ready file descriptor(s)
2023.08.23 11:01:04 LOG7[service]: FD=604 ifds=r-x ofds=---
2023.08.23 11:01:04 LOG7[service]: FD=664 ifds=r-x ofds=r--
2023.08.23 11:01:04 LOG7[service]: Service [dev-dev-testHarness] accepted (FD=708) from 127.0.0.1:10756
2023.08.23 11:01:04 LOG7[service]: Creating a new thread
2023.08.23 11:01:04 LOG7[service]: New thread created
2023.08.23 11:01:04 LOG7[4]: Service [dev-dev-testHarness] started
2023.08.23 11:01:04 LOG7[4]: Setting local socket options (FD=708)
2023.08.23 11:01:04 LOG7[4]: Option TCP_NODELAY set on local socket
2023.08.23 11:01:04 LOG5[4]: Service [dev-dev-testHarness] accepted connection from 127.0.0.1:10756
2023.08.23 11:01:04 LOG6[4]: Peer certificate not required
2023.08.23 11:01:04 LOG7[4]: TLS state (accept): before SSL initialization
2023.08.23 11:01:04 LOG7[4]: TLS alert (write): fatal: decode error
2023.08.23 11:01:04 LOG3[4]: SSL_accept: ssl/record/rec_layer_s3.c:303: error:0A000126:SSL routines::unexpected eof while reading
2023.08.23 11:01:04 LOG5[4]: Connection reset/closed: 0 byte(s) sent to TLS, 0 byte(s) sent to socket
2023.08.23 11:01:04 LOG7[4]: Local descriptor (FD=708) closed
2023.08.23 11:01:04 LOG7[4]: Service [dev-dev-testHarness] finished (0 left)
 
What am I missing, I haven't used stunnel for quite a while and previous effort were on linux and I did not see this problem then.
 
Using telnet/TNC as the local test tools and stunnel was installed with bare default installation. The only thing I have done different is to set a config fragment folder to separate services on the sever side and they report as loading fine.
 
any help greatly appreciated.
 
Stu