Results 1 to 5 of 5

Thread: Rtmp encoder cant connect to wowza server

  1. #1
    Join Date
    Apr 2013
    Posts
    29

    Default Rtmp encoder cant connect to wowza server

    I tried from a rtmp encoder (fmle) to connect with wowza server but i receive "Failure to connect to primary server. Please verify that your Server URL and application name are valid and that your Internet connection is working and retry."
    On the machine running FMLE, i opened a browser and enter: http://[wowza-address]:1935 and i see Wowza version and build number.

    Here is the logs

    2014-07-11 13:23:42 EEST comment session INFO 401 106028387 client connectionClosed [106028387] pingtimeout _defaultVHost_ - - 32.363 [any] 1935 - 127.0.0.1 rtmp - unknown 106028387 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:23:42 EEST disconnect session INFO 200 106028387 - _defaultVHost_ - - 32.364 [any] 1935 - 127.0.0.1 rtmp - unknown 106028387 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:26:45 EEST comment session INFO 401 331621930 client connectionClosed [331621930] pingtimeout _defaultVHost_ - - 32.343 [any] 1935 - 127.0.0.1 rtmp - unknown 331621930 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:26:45 EEST disconnect session INFO 200 331621930 - _defaultVHost_ - - 32.343 [any] 1935 - 127.0.0.1 rtmp - unknown 331621930 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:33:31 EEST comment session INFO 401 1431442947 client connectionClosed [1431442947] pingtimeout _defaultVHost_ - - 32.359 [any] 1935 - 127.0.0.1 rtmp - unknown 1431442947 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:33:31 EEST disconnect session INFO 200 1431442947 - _defaultVHost_ - - 32.36 [any] 1935 - 127.0.0.1 rtmp - unknown 1431442947 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:35:44 EEST comment session INFO 401 1412593785 client connectionClosed [1412593785] pingtimeout _defaultVHost_ - - 32.39 [any] 1935 - 127.0.0.1 rtmp - unknown 1412593785 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:35:44 EEST disconnect session INFO 200 1412593785 - _defaultVHost_ - - 32.391 [any] 1935 - 127.0.0.1 rtmp - unknown 1412593785 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:37:02 EEST comment session INFO 401 1628337964 client connectionClosed [1628337964] pingtimeout _defaultVHost_ - - 32.372 [any] 1935 - 127.0.0.1 rtmp - unknown 1628337964 1537 3091 - - - - - - - - - - - - - - -
    2014-07-11 13:37:02 EEST disconnect session INFO 200 1628337964 - _defaultVHost_ - - 32.373 [any] 1935 - 127.0.0.1 rtmp - unknown 1628337964 1537 3091 - - - - - - - - - - - - - - -

    Then i used an other FMLE machine and i can connect with the same wowza server without problems. (same ip/app name).
    But why i cant connect with the first encoder (i use the same version of FMLE ,same OS,same wowza server and application)

    Any suggestions about the issue ?
    Last edited by elhal82; 07-11-2014 at 03:39 AM.

  2. #2

    Default

    Can you try using the real IP address in FMLE rather than 127.0.0.1? It may be that one FMLE instance is on the same box as Wowza so 127.0.0.1 (localhost) will work, but if you use 127.0.0.1 in FMLE to connect to Wowza on a different machine then that IP address won't work. You would need to enter the publicly visible IP address of the box.


    -Paul

  3. #3
    Join Date
    Apr 2013
    Posts
    29

    Default

    I use the public visible ip [rtmp://xxx.xxx.xxx.xxx/appname]
    I also used the [rtmp://xxx.xxx.xxx.xxx:1935/appname]
    The logs which i include is from those ips i never used the localhost.
    I tried to connect from the same machine to the other two wowza media servers which i own and i didnt had any problems.
    Also when i use an other FMLE machine from the same network area i cant connect to the wowza server 1

  4. #4

    Default

    Quote Originally Posted by elhal82 View Post
    Also when i use an other FMLE machine from the same network area i cant connect to the wowza server 1
    OK so on the other machine running FMLE which is on the same network as the Wowza server. Can you verify that you have a live application defined in Wowza with the same name as you entered in FMLE?

    -Paul

  5. #5
    Join Date
    Apr 2013
    Posts
    29

    Default

    FMLE1 and FMLE2 are on the same network area and on different network with WMSs
    Everything is the same the only thing that i change is the FMLE machine (live application same name)
    WMS1 and WMS2 are on different networks each other.

Similar Threads

  1. My encoder can't connect to my EC2 instance of Wowza
    By jHouseman in forum Wowza Streaming Engine in the Cloud
    Replies: 8
    Last Post: 10-01-2014, 02:23 PM

Posting Permissions

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