Skip to main content
A
Anonymous
December 5, 2008
Question

Virtual Host Problem

  • December 5, 2008
  • 1 reply
  • 521 views
Hello - I'm new to FMS. I've got the dev version installed on a box, and we've built a test SWF and server application. I want to use this box as our dev, test, and staging environments, so I created virtual hosts for each of them. I then setup the application in both the default host, and the "dev" virtual host.

I am unable to connect to the application (using fmscheck.exe OR our test application), but I can connect to the default host. The application loads fine in either host, I just can't connect to it.

So, why would I be able to connect to "myFMS1", but not say "dev.fms1.mydomain.com"? I have, of course, made sure that DNS entries point dev.fms1.mydomain.com to the myFMS1 box. I also updated the hosts file on myFMS1 so that it knows that dev.fms1.mydomain.com points to itself.

FWIW, I get the generic:

NetConnection.Connect.Failed

error.
    This topic has been closed for replies.

    1 reply

    J
    Jake2
    Participating Frequently
    December 5, 2008
    There's no inherent firewall policies in place that would inhibit the use of the 1111 or 1935 ports on that machine is there?
    A
    Anonymous
    December 5, 2008
    No there isn't.... Its all the same box, I just can only connect to one (the default) host... its very strange.

    I did some a little bit of luck with fmscheck.exe, and I use

    ?_fcs_vhost=dev.streaming.connectionsacademy.com

    in the query parameter, but I would much prefer to be able to just use dev.streaming.connectionsacademy.com as the server name. From the documentation I've read, that should work.
    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    December 5, 2008
    You want to make sure that the DNS entries that you use to get dev.fms1.mydomain.com don't map to another DNS entry but instead directly to IP. FMS only knows which VHost to launch by the string that the connection arrives with, hence if you have

    myFMS1 127.0.0.1
    dev.fms1.mydomain.com myFMS1

    It could pick up the name twice and end up still appearing as myFMS1 when the connection arrives and then being directed to the default. Check in your access logs. If you enable all the fields in Logger.xml then you should get the connection string that your connections are arriving with, if they don't string match your vhost that's why.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices