Trouble with stunnel.conf (version 5.41)

Mark Garciano <[email protected]>
Newsgroups gmane.network.stunnel.user
Message-ID <CY4PR07MB3429DCB1FE8A93D69F5DAC15DB140@CY4PR07MB3429.namprd07.prod.outlook.com>
Hi Stunnel users,

Any ideas why I get a "server down" message"?  Below is the conf file:

;---------------------------------------------------------------------------
; **************************************************************************

; * Global options *

; ************************************************************************** ;

; Debugging stuff (may useful for troubleshooting)

debug = 7

output = stunnel.log

;Disable FIPS mode to allow non-approved protocols and algorithms

fips = no

;**************************************************************************

; * Service defaults may also be specified in individual service sections *

; **************************************************************************

; Disable support for insecure SSLv2 protocol

options = NO_SSLv2

key = stunnel.pem

cert = stunnel.pem

client = yes

accept = 5001

connect = XXXXXXXXXXX.com:6443

TIMEOUTclose = 0

TIMEOUTconnect = 200

TIMEOUTidle = 86400
;---------------------------------------------------------------------------

HERE IS THE LOG WINDOW MESSAGE:
[!] Server is down
[ ] Running on Windows 6.1
[.] Reading configuration from file stunnel.conf
[.] UTF-8 byte order mark detected
[.] FIPS mode disabled
[ ] Compression disabled
[ ] Snagged 64 random bytes from C:/.rnd
[ ] Wrote 1024 new random bytes to C:/.rnd
[ ] PRNG seeded successfully
[ ] Initializing inetd mode configuration
[!] Service [(null)]: 'accept' option is only allowed in a [section]

Mark Garciano
Systems Programmer II
USC Libraries
Integrated Library Systems
213-740-3568

_______________________________________________
stunnel-users mailing list
[email protected]
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.