OK that makes perfect sense to have client=no but in this case the SSL socket connection gets created only to shut itself down in 4 seconds. Why should this happen?
2007.04.26 07:21:44 LOG7[3568:2316]: connect_wait: waiting 10 seconds 2007.04.26 07:21:44 LOG7[3568:2316]: connect_wait: connected 2007.04.26 07:21:44 LOG5[3568:2316]: https connected remote server from 127.0.0.1:1360 2007.04.26 07:21:44 LOG7[3568:2316]: Remote FD=248 initialized 2007.04.26 07:21:44 LOG7[3568:2316]: TCP_NODELAY option set on remote socket 2007.04.26 07:21:48 LOG7[3568:2316]: SSL socket closed on SSL_read 2007.04.26 07:21:48 LOG7[3568:2316]: Socket write shutdown 2007.04.26 07:21:48 LOG5[3568:2316]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket 2007.04.26 07:21:48 LOG7[3568:2316]: https finished (0 left)
-----Original Message----- From: RUTSCHLE Yves [mailto:yves.rutschle@c-s.fr] Sent: Thursday, 26 April 2007 12:51 AM To: davids@evertech.com.au Cc: stunnel-users@mirt.net Subject: Re: [stunnel-users] Connecting via rtmps to Red5 server
David Schulberg wrote:
Red5 doesn't directly support ssl connectivity but using rtmps
protocol (rtmp
tunnelled via https) clients should be able to connect to Red5 if stunnel handles the encrypted traffic on port 443 and passes unencrypted communications back and forth to the Red5 on a port it expects to receive rtmp communication..
(refer
http://www.adobe.com/devnet/flashcom/articles/firewalls_proxy04.html)
So you have stunnel running on the server-side, awaiting SSL connections from the Flash application, right?
client = yes
in which case, you need to be running stunnel in server mode, i.e. without this line.
HTH, Y.