Skip to main content
Inspiring
May 24, 2009
Question

Documentation for FMS with IIS?

  • May 24, 2009
  • 1 reply
  • 4071 views

I have installed FMS without Apache, since I already have IIS running on my server.  I have noticed that Apache seems to be the default web server to use with FMS; hence the abundance of documentation and notes Adobe has provided.  However, I can't find any documentation on how to configure FMS with IIS.  Is there any(documentation) from Adobe or anywhere else?

I would like to be able to run both video clips (RTMP and HTTP) from the Samples section of Flash Media Server 3.5/webroot/index.html.

Thanks.

    This topic has been closed for replies.

    1 reply

    May 27, 2009

    You can have FMS forward HTTP requests to any application listening on whatever port you define. See the following settings in conf/fms.ini:

    VOD_DIR

    SERVER.HTTP_ENABLED

    HTTP_PROXY.HOST

    If  you have FMS and IIS running on the same box, and you still want to bind IIS to port 80, I suggest that you give FMS it's own IP address so it will still be able to bind to port 80 (for RTMP users that can't connect on 1935)

    injpixAuthor
    Inspiring
    May 27, 2009

    Jay, thanks your reply!

    Below are the variables and values that I have in conf/fms.ini

    VOD_DIR = C:\Program Files\Adobe\Flash Media Server 3.5\applications\vod\media

    SERVER.HTTP_ENABLED = true

    HTTPPROXY.HOST = 23.28.193.9:80

    I'm able to ping 23.28.193.9, however I can't successfully pull-up anything in a browser from it.  I have tried the following:

    //sample.html is a page I created in the media directory

    http://23.28.193.9/applications/vod/media/sample.html

    http://23.28.193.9/webroot/index.html

    http://23.28.193.9/index.html

    And I did restart FMS.

    FYI, I am using VirtualPC; so my server and client OS are all on one CPU

    May 29, 2009

    Is IIS bound to the same IP address as FMS? If so, that's your problem. If both FMS and IIS are configured to listen on 23.28.193.9, then only one of them will successfully bind to port 80. Sounds to me like FMS started first, so it wins.

    Try giving FMS its own IP address, then restart IIS.