Results 1 to 5 of 5

Thread: new server not serving off-server

  1. #1
    Join Date
    Sep 2012
    Posts
    17

    Default new server not serving off-server

    Hi,

    I have a newly-installed wowza and daily license on what will be our production machine. Wowza starts and runs, and passes the tests:
    • http://serverIP:1935/ displays wowza version
    • vod example plays video
    • jwplayer in webpage plays example vod video

    But the jwplayer test run from another system fails to connect saying

    server not found: rtmpt://serverIP:80/vod
    The JW Player code
    JW Player streamer example <br />
    <div id='mediaplayer'>Loading the Player ...</div>
    <script >
      jwplayer("mediaplayer").setup({
        width: 320,
        height: 180,
        players: [{ 
          config: {
            'provider': 'rtmp',
            'streamer': 'rtmp://serverIP/vod/',
    	    'file': 'mp4:sample.mp4'
          },
          type: 'flash', 
          src: '/Streams/jwplayer/player.swf' 
        }],
        plugins: {
          '/Streams/jwplayer/livestream.js': {}
        },
        controlbar: 'bottom'
      });
    </script>
    Packet monitoring shows the request is coming from the client machine, but the Wowza server seems to simply ignore it. Also, a live stream connection from FME is similarly ignored.

    The license is daily. The client is not on the same domain as the server. Could this be the issue?

    Joe

  2. #2
    Join Date
    Sep 2011
    Posts
    1,934

    Default

    Hi
    Have you opened port 80 in the VHost.xml?
    It can be found here:
    [Wowza-install]/conf/Vhost.xml

    Change :
    <Port>1935</Port>

    To:
    <Port>1935,80</Port>

    Jason

  3. #3
    Join Date
    Sep 2012
    Posts
    17

    Default

    I changed VHost.xml to match your note. There is no difference in the behavior.

    The Wowza server is running on a VMWare virtual machine on our 172 (internal) sublan. The client machine is a physical desktop running on our 192(internal) sublan.

    In a packet monitor, the line
    http://serverIP:1935
    shows the client's request being received by the server.
    Also in a packet monitor, attempting to connect with the JWPlayer (previous post) shows the client's request being received.

    But in neither case does the Wowza server respond, neither in its output window, nor in packets transmitted.

    This is the output of the Wowza server. There is no response after startup is complete.
    Configure logging: file:///C:/Program Files (x86)/Wowza Media Systems/Wowza Media Server 3.1.2/conf/log4j.properties
    INFO server server-start Wowza Media Server 3 Daily Edition 3.1.2 build1624 -
    INFO server comment - Server License Key: SVRD3-XXXXX-XXXXX-XXXXX-XXXXX-CyhH8
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Transcoder Streams Available: Unlimited
    INFO server comment - Transcoder Watermark: No
    INFO server comment - nDVR Available: Yes
    INFO server comment - DRM Available: Yes
    INFO server comment - Hardware Available Processors: 1
    INFO server comment - Hardware Physical Memory: 3059MB/4095MB
    INFO server comment - Hardware Swap Space: 7075MB/8189MB
    INFO server comment - Max File Descriptor Count: Unlimited
    INFO server comment - OS Name: Windows Server 2008 R2
    INFO server comment - OS Version: 6.1
    INFO server comment - OS Architecture: amd64
    INFO server comment - OS CPU: amd64
    INFO server comment - Java Name: Java HotSpot(TM) 64-Bit Server VM
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.7.0_07
    INFO server comment - Java VM Version: 23.3-b01
    INFO server comment - Java Spec Version: 1.7
    INFO server comment - Java Home: C:\Program Files\Java\jdk1.7.0_07\jre
    INFO server comment - Java Max Heap Size: 2900MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Locale[user.language]: en
    INFO server comment - Java Locale[user.country]: US
    INFO server comment - Java Locale[user.variant]:
    INFO server comment - Java Locale[file.encoding]: Cp1252
    INFO server comment - Java Timezone[user.timezone]: America/Chicago
    INFO server comment - Java Args[0]: -Xmx3000M
    INFO server comment - Java Args[1]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[2]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[3]: -Dcom.wowza.wms.native.base=win
    INFO server comment - Java Args[4]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: win
    INFO server comment - Server threads[h/t]: 10/10
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:C:/Program Files (x86)/Wowza Media Systems/Wowza Media Server 3.1.2
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:80:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:80)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - Wowza Media Server is started!
    This is a new installation; it has never worked. It has to be something basic.

    Thanks,
    Joe

  4. #4
    Join Date
    Sep 2012
    Posts
    17

    Default

    I got it, the windows firewall was blocking it on the server.

    Joe

  5. #5
    Join Date
    Sep 2011
    Posts
    1,934

    Default

    Hi
    That's good, thanks for the update.

    Jason

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •