Authentication with Wirecast 4.3.1 and Wowza 3.6.2

Wowza Streaming Engine
1

I have not, after many hours of searching through posts, and numerous attempts, been able to make the user/password authentication work. I have created a “live” application directory and it’s appropriate conf directory. It all works fine as an open server.

When I remove the * from the directive in the appropriate Application.xml file, Wirecast duly demands to be authenticated. but ignores the credentials configured in Wirecast.

When I add the ModuleRMTPAuthenticate directive, as instructed in "How to enable username/password … (11-08-2012) Wirecast responds with a -4018 error. Although Wowza seems to modify its behaviour without having to be restarted when the xml file is saved, I have tried it by restarting the server as well. I am using the /conf/publish.password file, and have no need for a per-application configuration.

I have tried both basic and digest auth. I seem to get two kinds of error reported from wire cast, -4020 Cannot publish the stream. or -4018, after a short delay. Both seem to indicate a problem with the authentication. However some instances, just after adding the directive, seem not to be able to even connect to the application, however other applications seem just fine.

Oh, yes, I have also tried the various user agent settings in Wirecast.

As it currently appears, I seem to have no option but to run a completely open streaming server… Any help would be most appreciated.

Cheers

Glen

2

Hi Glen,

Have you tested your Wowza RTMP authentication using a different RTMP encoder? It would be helpful to narrow this to a Wirecast configuration or a problem specific to Wowza, if possible.

I think the next best step from a support standpoint is to take a look at your configuration and log files. Please send an email to support@wowza.com and include a copy of your [install-dir]/conf and /logs folders as a .zip file (or other archive) so we can take a closer look at your configuration and server activity. Provide a brief description of this problem and a reference to this post too.

Thank you,

-Tim

3

Glen,

You should not remove the asterisk from StreamWriteAccess. This will prevent Wirecast from being able to publish. Replace the asterisk and restart

Richard

4

Hi - I am having a similar problem. I am running 3.6.2. I set up module RTMPAuthenticate with a per app passwd file. Upon encoder publish the wowza log shows that we get to onStreamCreate and creates the stream then it just sits there. It seems like the encoder never returns the auth challenge… 15 secs later the stream is destroyed. i have tried from a Haivision Makito and from a Teradek Cube. I get no errors just a silent retry…

2013-09-30 14:46:22 CEST comment server INFO 200 - ModuleRTMPAuthenticate.onAppStart: SecureToken is off - - - 19.337 - - - –

2013-09-30 14:46:22 CEST comment server INFO 200 - ModuleRTMPAuthenticate.onAppStart: Authorization password file: /wowza/live_vhost/conf/live/publish.password -19.338 - - - - - - - - - - - - - - - - - - - - - - - –

2013-09-30 14:46:22 CEST app-start application INFO 200 CH1 live/CH1 - - - 19.354 - - - - - - –

2013-09-30 14:46:22 CEST connect-pending session INFO 100 77.59.142.9 - live_vhost live CH1 0.192 10.0.0.22 1935 rtmp://server.tld/live/CH77.59.142.9 rtmp - LNX 10,0,32,18 1117692220 3235 3073 - - - - - - - - - - - - -rtmp://server.tld/live/CH1 -

2013-09-30 14:46:22 CEST connect session INFO 200 77.59.142.9 - live_vhost live CH1 0.193 10.0.0.22 1935 rtmp://server.tld/live/CH1 77.59.142.9 rtmp - LNX 10,0,32,18 1117692220 3235 3073 - - - - - - - - - - - - - rtmp://server.tld/live/CH1 -

2013-09-30 14:46:23 CEST comment server INFO 200 - onStreamCreate[com.wowza.wms.stream.live.MediaStreamLive@78ca3ba1]: clientId:1117692220 - - - 20.063 - - - - - - - - - - - - - - - - - - - - - - - –

2013-09-30 14:46:23 CEST create stream INFO 200 - - live_vhost live CH1 0.012 10.0.0.22 1935 rtmp://server.tld/live/CH1 77.59.142.9 rtmp - LNX 10,0,32,18 1117692220 3268 3413 1 0 0 0 - - - - - - rtmp://server.tld/live/CH1 rtmp://server.tld/live/CH1 - rtmp://server.tld/live/CH1 -

2013-09-30 14:46:39 CEST comment server INFO 200 - onStreamDestroy[com.wowza.wms.stream.live.MediaStreamLive@78ca3ba1]: clientId:1117692220 - - -36.63 - - - - - - - - - - - - - - - - - - - - - - - –

2013-09-30 14:46:39 CEST comment server INFO 200 - removeClientListener: 1 - - - 36.632 - - - - - - - –

2013-09-30 14:46:39 CEST destroy stream INFO 200 - - live_vhost live CH1 16.585 10.0.0.22 1935 rtmp://server.tld/live/CH1 77.59.142.9 rtmp - LNX 10,0,32,18 1117692220 3465 3898 1 0 0 0 - - - - - - rtmp://server.tld/live/CH1 rtmp://server.tld/live/CH1 - rtmp://server.tld/live/CH1 -

2013-09-30 14:46:39 CEST comment server INFO 200 - onStreamCreate[com.wowza.wms.stream.live.MediaStreamLive@40634bec]: clientId:1117692220 live_vhost live CH1 36.639 - - - - - - - - - - - - - - - - - - - - - - –

2013-09-30 14:46:39 CEST create stream INFO 200 - - live_vhost live CH1 0.002 10.0.0.22 1935 rtmp://server.tld/live/CH1 77.59.142.9 rtmp - LNX 10,0,32,18 1117692220 3465 3898 1 0 0 0 - - - - - - rtmp://server.tld/live/CH1 rtmp://server.tld/live/CH1 - rtmp://server.tld/live/CH1

5

Customer being helped in ticket #68244. -Tim

6

Hi Tim

I tried the FMLE and it did not work either. Log:

Wed Jul 24 2013 17:31:10 : Selected video input device: Blackmagic NTSC/PAL - 8 Bit

Wed Jul 24 2013 17:31:19 : Primary - Connected to FMS/3,5,7,7009

Wed Jul 24 2013 17:31:24 : Primary - Network Command: onFCPublish

Wed Jul 24 2013 17:31:24 : Primary - Stream[evensong] Status: Success

Wed Jul 24 2013 17:31:24 : Primary - Stream[evensong] Status: NetStream.Record.NoAccess

I’ll zip things up tomorrow for you…

Glen

7

This has been sitting in limbo for some time now, but I did receive an acknowledgement from Telestream support that the problem lay with WireCast. They indicated that this problem would be addressed in the next update of WireCast, which, to the best of my knowledge has not yet occurred. The result is that I am still operating on an open connection (once I open the door when I need to use the link). Pedro, what encoder are you using?

Cheers

Glen

8

I have the Wowza Version 3.6.2 running in Windows 2012 server and I’m having the same issue. I tried to configure the ModuleRTMPAuthenticate as instruction at https://www.wowza.com/docs/how-to-enable-username-password-authentication-for-rtmp-and-rtsp-publishing. But not works. If I try to use In FMS URL field rtmp://[ip-address]:1935/point the encoder is connecting directly without request login/password. If I try use rtmp://[ip-address]/point, the same.

Bellow I show what I informed in files:

  1. Application.xml from /conf:

flvplayback

FLVPlayback

com.wowza.wms.module.ModuleFLVPlayback

ModuleRTMPAuthenticate

ModuleRTMPAuthenticate

com.wowza.wms.security.ModuleRTMPAuthenticate

  1. Application.xml from /conf/point/:

maxApplicationConnections

2000

Integer

rtmpEncoderAuthenticateFile

${com.wowza.wms.context.VHostConfigHome}/conf/${com.wowza.wms.context.Application}/publish.password

After done it, I restarted the wowza, but not works.

Someone can help me to solve this issue? I done the same in an early version, like 3.1 and worked fine. But in this last version not is working.

I wait any reply to solve this issue.

Thanks

Pedro

9

In my case, I’m using Adobe Media Encoder 3.2. What can be done to solve it?

I wait reply

Thanks

Pedro

This has been sitting in limbo for some time now, but I did receive an acknowledgement from Telestream support that the problem lay with WireCast. They indicated that this problem would be addressed in the next update of WireCast, which, to the best of my knowledge has not yet occurred. The result is that I am still operating on an open connection (once I open the door when I need to use the link). Pedro, what encoder are you using?

Cheers

Glen