FMS 2.0 and STUNNEL? Using SSL Tunneling on FMS2 doesnot work!

[bluestreak84]

I am trying to use FMS in conjunction with STUNNEL to enable HTTPS SSL
tunneling using a flash client. We have been working on this for weeks to no
avail. The Stunnel configuration is set up correctly to redirect traffic from
port 443 (SSL) to port 1935(FMS) but after i approve the SSL on the client side
the connect just fails.

Has anyone gotten FMS2.0 SSL tunelling working? We are about to purchase the
full server but if SSL Tunneling doesn't work then it is useless to us.

Please help!

[BryanCrow]

When you use rtmps when connecting. STunnel should then (using the default
HTTPS forwarding) decrypt incomming HTTPS traffic on 443 and forward it as HTTP
traffic to port 80. If you changed your config for STunnel to forward to 1935
instead of 80, that should work. If you're still having issues, you might want
to double-check to make sure your SSL certificate is valid, and the root
authority is installed on the connecting machine. If you're not paying for a
cert, chances are your cert's root authority isn't being accepted by the
connecting machine.

For my setup, I'm using a hardware SSL Accelerator with a wildcard cert from
equifax. I have FMS2 configured to listen on 80, and it's working perfectly
(well... from windows anyway).

In any case, if you're going to be relying on a software SSL Accelerator, you
may as well just use FMS2's new SSL support. The FMS live docs have plenty of
documentation on how to install your cert and configure it properly.