Wirecast -4018 error when initiating broadcast - no error in FMLE

Wowza Streaming Engine
1

  • Adobe FMLE works using same account and credentials. This is an existing working system. Again, FMLE can authenticate with the very same account. Wirecast used to work. We are not sure exactly at what upgrade of Wowza it stopped working (it was sometime in the last couple months).

  • Using latest version of wms-plugin-security.jar . Using Wowza server version 2.1.1 . Wirecast 3.5.8 (win). Also removed/installed Wirecast again. All firewalls off.

  • Wirecast cannot broadcast if application is configured to use RTMP authentication via module “ModuleRTMPAuthenticate”. The error "Cannot connect to the RTMP/Flash server at the given IP address. Verify the server is reachable at the given address. [-4018]

  • Have tried Wirecast and FMLE 3 user agent options in Wirecast

  • Can be re-produced from multiple locations . Again FMLE works.

  • Application.xml is setup correctly. The following module entry is the last entry in the module list:

ModuleRTMPAuthenticate

ModuleRTMPAuthenticate

com.wowza.wms.plugin.security.ModuleRTMPAuthenticate

Access log for failed Wirecast connection attempt:

2010-11-06 13:15:32 PDT connect-pending session INFO 100 127.0.0.1 - defaultVHost live definst 0.0030 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live FMLE/3.0 (compatible; FMSc/1.0) 499184080 3356 3073 - - - - - - - - - - - - - rtmp://localhost/live authmod=adobe&user=live

2010-11-06 13:15:32 PDT connect session INFO 401 127.0.0.1 - defaultVHost live definst 0.0040 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live FMLE/3.0 (compatible; FMSc/1.0) 499184080 3356 3073 - - - - - - - - - - - - - rtmp://localhost/live authmod=adobe&user=live

2010-11-06 13:15:32 PDT disconnect session INFO 200 499184080 - defaultVHost live definst 0.0060 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live FMLE/3.0 (compatible; FMSc/1.0) 499184080 3372 3422 - - - - - - - - - - - - - rtmp://localhost/live authmod=adobe&user=live

Access log entries when FMLE connects (working) :

2010-11-06 13:15:33 PDT connect-pending session INFO 100 127.0.0.1 - defaultVHost live definst 0.0030 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== FMLE/3.0 (compatible; FMSc/1.0) 1721949869 3564 3073 - - - - - - - - - - - - - rtmp://localhost/live authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ==

2010-11-06 13:15:33 PDT connect session INFO 200 127.0.0.1 - defaultVHost live definst 0.0060 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== FMLE/3.0 (compatible; FMSc/1.0) 1721949869 3564 3073 - - - - - - - - - - - - - rtmp://localhost/live authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ==

2010-11-06 13:15:34 PDT create stream INFO 200 - - defaultVHost live definst 0.011 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== FMLE/3.0 (compatible; FMSc/1.0) 1721949869 3715 3411 1 0 0 0 - - - - - - rtmp://localhost/live rtmp://localhost/live - rtmp://localhost/live authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ==

2010-11-06 13:15:34 PDT publish stream INFO 200 broadcast1 - defaultVHost live definst 0.014 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== FMLE/3.0 (compatible; FMSc/1.0) 1721949869 3810 3452 1 0 0 0 broadcast1 videoKeyframeFrequency=5&totalDatarate=128 - - - - rtmp://localhost/live/broadcast1?videoKeyframeFrequency=5&totalDatarate=128 rtmp://localhost/live/broadcast1 videoKeyframeFrequency=5&totalDatarate=128 rtmp://localhost/live authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ==

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/definst/broadcast1]: chunkDurationTarget: 10000 - - - 246.828 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/definst/broadcast1]: chunkDurationTolerance: 500 - - - 246.829 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/definst/broadcast1]: audioGroupCount: 3 - - - 246.829 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/definst/broadcast1]: playlistChunkCount:3 - - - 246.829 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: cupertinostreamingpacketizer:broadcast1 - - - 246.83 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - CupertinoPacketHandler.startStream[live/definst/broadcast1] - - - 246.831 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.handlePacket: Video codec: H264 - - - 246.832 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.handlePacket: Video info[live/definst/broadcast1]: {H264CodecConfigInfo: profile: “Baseline”, level: 3.0, frameSize: 320x240, aspect: 1/1} - - - 246.835 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: smoothstreamingpacketizer:broadcast1 - - - 246.838 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerSmoothStreaming.startStream[live/definst/broadcast1] - - - 246.839 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:35 PDT comment server INFO 200 - LiveStreamPacketizerCupertino.handlePacket: Audio codec: MP3 - - - 246.959 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:40 PDT comment server INFO 200 - LiveStreamPacketizerSmoothStreaming.flushPendingAudio: Bitrate[live/definst/broadcast1]: 47737 - - - 252.312 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:43 PDT unpublish stream INFO 200 broadcast1 - defaultVHost live definst 8.728 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== FMLE/3.0 (compatible; FMSc/1.0) 1721949869 88459 3612 1 0 84858 0 broadcast1 videoKeyframeFrequency=5&totalDatarate=128 - - - - rtmp://localhost/live/broadcast1?videoKeyframeFrequency=5&totalDatarate=128 rtmp://localhost/live/broadcast1 videoKeyframeFrequency=5&totalDatarate=128 rtmp://localhost/live authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ==

2010-11-06 13:15:43 PDT destroy stream INFO 200 broadcast1 - defaultVHost live definst 8.73 [any] 1935 rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== 127.0.0.1 rtmp rtmp://localhost/live?authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ== FMLE/3.0 (compatible; FMSc/1.0) 1721949869 88505 3762 1 0 84858 0 broadcast1 videoKeyframeFrequency=5&totalDatarate=128 - - - - rtmp://localhost/live/broadcast1?videoKeyframeFrequency=5&totalDatarate=128 rtmp://localhost/live/broadcast1 videoKeyframeFrequency=5&totalDatarate=128 rtmp://localhost/live authmod=adobe&user=live&challenge=iAQAAA==&response=O9PDgpVdubKZjjrnNC3+pw==&opaque=6wm0uQ==

2010-11-06 13:15:55 PDT comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[live/definst/broadcast1]: Destroy live stream packetizer: cupertinostreamingpacketizer - - - 266.473 - - - - - - - - - - - - - - - - - - - - - - - - -

2010-11-06 13:15:55 PDT comment server INFO 200 - MediaStreamMap.removeLiveStreamPacketizer[live/definst/broadcast1]: Destroy live stream packetizer: smoothstreamingpacketizer - - - 266.473 - - - - - - - - - - - - - - - - - - - - - - - - -

We need to get Wirecast RTMP authentication working again. What can possibly be wrong?

2

Try re-downloading the MediaSecurity Addon

https://www.wowza.com/docs/media-security-overview

Copy /lib/wms-plugin-security.jar file over the one in Wowza /lib folder, then restart Wowza.

Richard

3

Bumped into the same problem:

http://forum.telestream.net/forum/messageview.aspx?catid=45&threadid=6939&STARTPAGE=1

Any updates on this?

4

In my test I was able to get 4018 error by “trying to connect to Wowza when it is not running, or by trying to connect to an application that does not exist.”

Ok, I suppose that would be normal behaviour.

I get this error randomly with a valid address/application when hitting the broadcast button.

Could you try to start/stop broadcast several times to an application that requires authentication?

In my case this just randomly succeeds/fails without changing any settings.

The debug logs from Wowza in the Wirecast forum post do not indicate any problems. btw, debug logs have too much info for most situations, and actually make it more difficult to figure out what is happening. In a few cases they are necessary.

I understand, but in this case it might be useful, as the INFO logs almost outputs anything.

A failed session starts with

DEBUG server comment - queryStr: authmod=adobe&user=a

While a successfull session:

DEBUG server comment - queryStr: authmod=adobe&user=a&challenge=dGcAAA==&response=KJ5m5CIJKQxPZwqM25u7qg==&opaque=MWBqvA==

(cfr. http://forum.telestream.net/forum/messageview.aspx?catid=45&threadid=6939&STARTPAGE=1 )

5

Sounds like you are stress testing Wirecast and Wowza. If you are getting this error when you “start/stop broadcast several times to an application that requires authentication”, then don’t do that.

Richard

Not stress testing, just normal use. I just noticed it was random because sometimes it is not working the first time.

When you have multiple (bitrate) streams configured in the broadcast settings, the problem gets more anoying, because both can fail.

Sometimes we need to stop/start up to 5 times until both streams are published.

6

I don’t know whether Wirecast or Wowza is causing the problem. Posted it first in Wirecast forum, and they suggested to contact Wowza as well, as you can read in the Wirecast forum.

I see a clear difference between the successful and failed logs, but you might know better how to interpret this:

DEBUG server comment - queryStr: authmod=adobe&user=a

vs

DEBUG server comment - queryStr: authmod=adobe&user=a&challenge=dGcAAA==&response=KJ5m5CIJKQxPZwqM25u7qg==&opaque=MWBqvA==

To replicate it:

Clean Wowza 2.2.3 install, and added 2 security (2.0) jars in the lib folder

Create a “live” application with ModuleRTMPAuthenticate module, and insert a user-pwd in publish.password

Use Wirecast 4.0.1 with these credentials set, and try to stop/start broadcast a few times

7

MediaSecurity_2.0.zip contains:

wms-plugin-security.jar

wms-plugin-security-encryption.jar

8

We are still experiencing the same problem as well.

Makes no difference where you enter the credentials.

A difference with dptekco : sometimes the authentication does succeed. (all described in posts above)

side note: I have the impression the success rate depends on location of the broadcaster (latency?). Today we had to turn the auth. off because the broadcaster needed that many attempts it with would be to much of a risk to use (what if broadcaster needed a restart during the event).

9

In the Wirecast Broadcast Settings dialog, click button labeled “Set Credentials…”. Add username and password here. Click OK, then save. Then you can publish from Wirecast with ModuleRTMPAuthenticate.

Richard

10

I am able to generate a 4018 error code in Wirecast by trying to connect to Wowza when it is not running, or by trying to connect to an application that does not exist.

Can you zip up conf, logs and screen shots of Wirecast settings and send to support@wowza.com

Richard

11

In my test I was able to get 4018 error by “trying to connect to Wowza when it is not running, or by trying to connect to an application that does not exist.”

The debug logs from Wowza in the Wirecast forum post do not indicate any problems. btw, debug logs have too much info for most situations, and actually make it more difficult to figure out what is happening. In a few cases they are necessary.

Richard

12

Sounds like you are stress testing Wirecast and Wowza. If you are getting this error when you “start/stop broadcast several times to an application that requires authentication”, then don’t do that.

Richard

13

I’m not sure. I don’t see a problem in the logs you posted in the Wirecast forum. The error is coming from an encoder, not Wowza. If you can find a definitive correlation in the Wowza logs and can tell us how to replicate it, we can look at it.

Richard

14

Two security jars? I know of one.

Richard

15

I could never replicate a problem. If you are expecting a login dialog to pop-up like FMLE, you don’t get that.

Open Broadcast Settings dialog and click Set Credentials button to enter username and password

Richard

16

I tried it again and setting username and password that way didn’t work. However when I published and got a fail message, there was a button labeled “edit”, which I clicked and it opened the same credentials dialog. I set my username and password there, and it worked. So it is more like FMLE actually.

This is Wirecast 4.

Richard

17

Zip up and send the conf and logs folders to support@wowza.com

Do a few tests first to generate logging

Tell us which application is configured for security and that you have been testing.

Include a link that I can try to publish to with Wirecast.

Include a link to this thread.

Richard

18

One thought, does /conf/publish.password file have non-text word processor formatting?

@bubbles01, can you send support@wowza.com a rtmp url to secured Wowza application, along with username and password, so I can try to connect and play from Wirecast and FMLE.

And do a couple of tests and zip up conf and logs folders and send those. It would help a lot if you started with a empty access log, and just had testing related logging in the file you send.

Tell us what version of Wirecast and Wowza you are using.

Please include a link to this thread.

Richard

19

Try changing User Agent to “FMLE/3.0” in the Broadcast settings dialog. That worked for me.

Richard

20

Do you have ModuleRTMPAuthenticate setup on the application you are publishing to? Wirecast does not popup box for username/password, you have to open Set Credentials dialog to enter.

Richard