Adobe Connect User Community
Menu

#1 2011-04-08 10:56:38

**_anhyzer_**

Can Connect 8 listen on 1935, 443, and 80?

Our Connect servers have successfully listened on 1935, 443, and 80 for many years (Breeze/Connect 4, 5, 6, 7) by adhering to this KB entry: http://kb2.adobe.com/cps/240/2405470e.html

The following lines in custom.ini allow users to connect to FMS on port 1935. When that's blocked, it falls back to 443, and when that's blocked, it falls back to port 80:

-----------------
HTTP_PORT=8080
HTTPS_PORT=8443
DEFAULT_FCS_HOSTPORT=:1935,443,80
RTMP_SEQUENCE=rtmp://external-host:1935/?rtmp://localhost:8506/,rtmp://external-host:443/?rtmp://localhost:8506/,rtmp://external-host:80/?rtmp://localhost:8506/,rtmpt://external-host:443/?rtmp://localhost:8506/,rtmpt://external-host:80/?rtmp://localhost:8506/
-----------------

This breaks in our Connect 8 test environment, I can't get to the "Configure Connect Enterprise" Web interface on the local server with that configuration. When I remove the "80" from DEFAULT_FCS_HOSTPORT, it works. At that point, FMS will fall back to 443 when 1935 is blocked, but it won't fall back to 80 if 443 is closed. Does this have anything to do with the new Tomcat directory in the Connect install directory? Do I need to configure Tomcat differently?

In short, is there any way to achieve fallback to both 443 and 80 with Connect 8?

Thanks in advance for any thoughts.

--Chris

Offline

#2 2011-04-08 14:04:32

**_anhyzer_**

Re: Can Connect 8 listen on 1935, 443, and 80?

I believe I've resolved this problem by editing {breeze_home}\appserv\conf\server.xml and changing the Connector on port 80 to port 8080. Everything seems to be working and a computer configured to block outgoing 1935 and 443 successfully connects to a meeting on port 80.

--Chris

Offline

#3 2011-06-07 10:33:47

**_chrisb78_**

Re: Can Connect 8 listen on 1935, 443, and 80?

Thank you Chris, it works well on our production server.

Offline

#4 2011-06-08 02:29:58

**_ytok_**

Re: Can Connect 8 listen on 1935, 443, and 80?

anhyzer wrote:

I believe I've resolved this problem by editing {breeze_home}\appserv\conf\server.xml and changing the Connector on port 80 to port 8080. Everything seems to be working and a computer configured to block outgoing 1935 and 443 successfully connects to a meeting on port 80.

--Chris

I don't know how to change the connector on port 80 to port 8080 by editing server.xml. Please show me how to do it.
Thanks a lot for your help.

Offline

#5 2011-06-08 22:16:40

**_lightrain_**

Re: Can Connect 8 listen on 1935, 443, and 80?

<Connector port="8080" protocol="HTTP/1.1"
           executor="httpThreadPool"   
           enableLookups="false"
               acceptCount="250"
               connectionTimeout="20000"
               redirectPort="443"
               URIEncoding="utf-8"/>

Offline

#6 2011-06-08 22:40:14

**_ytok_**

Re: Can Connect 8 listen on 1935, 443, and 80?

Hi lightrain,

Thanks a lot !!

Offline

Board footer