Skip to main content
A
Anonymous
April 21, 2011
Question

Problems with the latest windows installer?

  • April 21, 2011
  • 1 reply
  • 590 views

FMS *sigh* FML

I am trying to get live streaming running on my windows 7 machine (as full admin; permissions shouldn't be an issue)

- Windows install

- No serial/Development server version

- Yes Appache

- Admin, password...
- Default, default, default...ect, GO.

Out of box, nothing worked - localhost just laughed at me with a blank ("could not connect") page and the FMS admin page was no better "Login attempt to the server below failed...etc".  Then I found that [root]/Apache2.2/conf/httpd.conf came straight from the installer like this

# Please see httpd.conf.orig for the configuration of a default

# (non-FMS) installation of apache.


Listen 8134

# If you plan to run FMS as root on linux, you _must_ specify a

# valid user, with access to the FMS installation direction, or


First off - Isn't that supposed to be set to 80?  Also, httpd.conf had no definition for ServerRoot - I am no apache expert (that cannot be overstated) but everytime i've used it, i've needed to define this.

Anyway, I figured I had nothing to lose and so armed with essentially my mom's working knowledge of Apache's .conf schema, I went in and changed "Listen 80" and added a definition for ServerRoot, reset and...tada...finally, localhost would resolve to that FMS startup page.  But that doesn't mean much because I get a timeout/failure on the rtmp demo (sure the http demo works but who cares; ignf about http).  But that makes sense because the FMS admin page STILL can't connect to localhost (or localhost:1111 for that matter) so there was no server instance to connect to anyway...[Jason slumps; a broken man].


Anyway - anyone have any insight?  Same problems += soultion?

    This topic has been closed for replies.

    1 reply

    Nikhil_Kalyan
    Nikhil_Kalyan
    Participating Frequently
    April 22, 2011

    Hi,

    Thank you for trying FMS.

    Though you mentioned you have the admin access on your windows 7 machine, I still doubt the admin privileges are the cause of the problem for you. Let's take your issues one by one.

    After the FMS installation, the installer gives options to start the service automatically (few check boxes to select). But on Windows 7, that wont work straight away even though you are logged in as admin. What you need to do is to open a command prompt (with run as administrator). So, your command prompt is actually elevated with admin stuff. Now try to start the fms services as below :

    c:\> net start fms

    c:\> net start fmsadmin

    Once you get the successful messages, try to make connections, it should work.

    Next, the apache that comes along with FMS runs/listens on 8134 itself. Port 80 is taken over by the FMS processes (to be exact, the FMSEdge process) which will redirect all HTTP traffic to Apache on 8134 and all the RTMP traffic to itself (to be exact, to FMSCore process) and hence you can keep the 8134 intact.

    Once your services start correctly, there wont be any port conflict/problems.

    Please try and let us know if that helps.

    Thank you !

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices