I don't know of any problems that would cause this. RTMP and RTMPS are really just using the socket layer to make the connections so I don't know why a firewall would interfere as long as the ports are open.
You could turn on the debug logging for the Endpoint.* and Protocol.* targets and that might give some clues on the server side why the connection is failing. It might also be worth using the <mx:TraceTarget/> on the client to see what errors the client is getting. You might check the file descriptor usage on the server as that is a commonly encountered problem with RTMP. You can run the "lsof" command on some systems to display the open files by a process and then check your limits to be sure you have enough of them available. Jeff ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ash Weaver Sent: Tuesday, September 04, 2007 12:09 PM To: [email protected] Subject: [flexcoders] Issues running RTMPS through firewall Hi all, Has anyone out there tried enabling RTMPS connections from a Flex client to LCDS running behind a firewall? Now if we test the app internally (i.e. inside the firewall), everything works just fine. It seems like things break down once we start going through a firewall. Here are the symptoms: A few RTMPS connections will go through and the app works fine for a short while. After that point, no RTMPS connections will work at all. Here's some info on the application: Client: - Flex 2 - has several assembler and topic message subscriptions - makes a number of RPC service calls to the backend Server: - jboss 4.05, embedded tomcat 55, LCDS 2.5 We've tried several different firewalls and even opened up all traffic through the firewall. The issue seems to have something to do with the fact that the firewall is forwarding traffic intended for an external IP address to an internal, different IP address. Has anyone run into this situation before? Does anyone know if, as an added layer of authentication, LCDS keeps track of the requested IP for RTMPS connections and chokes while comparing the external vs. internal IP? Thanks! Ash
