Skip to main content
A
Anonymous
October 18, 2010
Question

startVHost() does not work on new vhosts

  • October 18, 2010
  • 1 reply
  • 553 views

Hi,

I'm using FMS 4.0 64 bit

The way I create new VHost on default adapter:

1. Create new directory named for example foo.host.com and copy Application.xml and Vhost.xml from _defaultVHost_ dir.

2. Execute startVHost command through http admin interface or Restart Vhost in admin console.


New Vhost still does not work untill I Restart the Server (which is not acceptable).

I had no problems with startVHost or restartVHost on new vhosts on FMS 2 - I did not have to restart the whole server to make new vhost work.

Any help ?

thanks

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    October 18, 2010

    Here is what edge.log says when I try to access the application on NEW vhost after I start or restart vhost (rtmp://new.vhost.com/app):

    Connection rejected by server. Reason : [ Server.Reject ] : (_defaultRoot_, _defaultVHost_) : Application (app) is not defined.

    Does that mean that server still does not "see" this new vhost ?

    Btw, getVhosts returns vhosts including new vhost.

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    October 18, 2010

    This is a known issue that is being worked now in FMS.  For now your workaround as you found is restarting FMS to load the new virtual host.


    Asa

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