Skip to main content
October 12, 2010
Question

Can FMS be installed on the same IP as my main web server?

  • October 12, 2010
  • 1 reply
  • 1421 views

Hello all,

As stated in the title, can FMS and my Linux server share the same IP or must they be differemt?

Thanks!

wordman

    This topic has been closed for replies.

    1 reply

    October 13, 2010

    They -can- share the same IP, but ideally, you'll want to bind FMS to port 80 as well as port 1935. Since your http server will bind to port 80 as well, you'll want to have a second IP address for FMS (two servers can't bind to port 80 on the same IP).

    October 13, 2010

    Jay,

    I need to clarify and as I am so new, I want to be redundant here:

    You say they -can- share the same IP, as long as FMS is bound to port 1935 and 80. It's where you say "Since your http server will bind to port 80 as well, you'll want to have  a second IP address for FMS (two servers can't bind to port 80 on the  same IP)." that confuses me, as it seems to contradict the first part.

    Please don't misunderstand, I'm not being a snot, I just don't fully understand and I need more elaboration.

    Let's add to the mix...

    I am reviewing my fms.ini file on the server via SSH and it says:

    ADAPTOR.HOSTPORT = XXX.X.X.X:1935

    I don't know what the initial numbers are that are shown as Xs, but shouldn't there be a ,80 after 1935?

    Maybe this is why I can't get rtmp to play?

    Should I get my host to attach FMS to my secondary IP?

    I am so clueless right now...any help will be welcome!

    Thank you!

    Sincerely,

    wordman

    October 13, 2010

    About port bindings, if you're not worried about having FMS listen on port 80, you can use a single IP for both FMS and your HTTP server. If you want to bind FMS to port 80, you need to have a separate IP address for FMS. What I mean by "two servers can't bind to port 80 on the  same IP" is just that... if you have both FMS and an HTTP server trying to bind to port 80 on the same IP, one will succeed, and one will fail.

    In the configuration for the hostport, the xxx.xxx.xxx represents the IP address you want to bind to. The numbers following to colon are the ports to bind to.

    By default (the default configuration) FMS will bind to all IP's on port 1935. If you want to bind to a specific IP, replace the wildcard with the IP to bind to... for example, if you have an IP 10.10.10.10, ad you want to bind to ports 1935 and 80, you'd configure like so:

    ADAPTOR.HOSTPORT = 10.10.10.10:1935,80

    The purpose for binding to port 80 is to help with firewall traversal. In some cases, your users many not be able to connect via port 1935, and some proxies and/or firewalls will prevent RTMP altogether. Assuming you don't specify a port or protocol other than RTMP in your connection string (on the client side), the flashplayer will first try RTMP on port 1935, and if that fails, it will try RTMPT (tunneled RTMP... rtmp wrapped in HTTP headers) over port 80.

    So, to have the widest possible reach, you'll want to bind FMS to ports 1935 and 80, and to do so, you'll want to give FMS it's own IP.

    You might want to read through the configuration guide in the docs.... lots of good information there to help you understand configuration of the server.