#1 2009-03-23 15:47:21

**_jareddd_**

Redirect rtmpt traffic through port 80 if 1935 closed down

Hi,

Does anyone know the code to add to a custom.ini to redirect rtmpt traffic through port 80 if 1935 is locked down?  We are in the process of procuring an ssl.  However in the mean time, I'd like to enable this until we are locked down with ssl.

I'm running Connect 7 Service Pack 2.

Thanks

Last edited by **_jareddd_** (2009-03-23 15:59:51)

**_Jasmeet_**

Re: Redirect rtmpt traffic through port 80 if 1935 closed down

Hi,

You can always Connect to listen on ports 443 or 80 if port 1935 is blocked.
To setup the extra ports for Connect Professional, the custom.ini must be manually modified.
This is how you can make changes to custom.ini.It includes RTMPT Sequence as well.

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/?rtmpt://localhost:8506/,

       rtmpt://external-host:80/?rtmpt://localhost:8506/

Save and Close the Custom.ini file.
Then Click on configure connect enterprise server,click on server settings and change HTTP port to 8080.
Save it and then restart the services.
I think this will help you.

**_jareddd_**

Re: Redirect rtmpt traffic through port 80 if 1935 closed down

Thanks for the reply, however is it required to change the default port to 8080?  Can't everything just go through port 80?