Wowza Community

IDENT request failed with error: Security error accessing url

Hi There,

I’m in need of help. I’m having a problem which I believe to be centered around flash. I have 17 Wowza Servers on AWS EC2 and they are running fine… . All are wowza ready instances. I’ve recently moved 8 servers into a data center building them up as Wowza Transcoder/Origin Servers, Loadbalancer and Edge Servers… They are running on Linux CentosOS 6.2 with the firewall disabled and SELinux disabled. Java is installed and must be working…

I’ve got the first transcoder/origin up and running and pulling a stream. I have the stream playing on my IOS device no problem. When trying to play the stream using the Akamai Support player (http://support.akamai.com/flash/index.html), I keep getting the following Error: “IDENT request failed with error: Security error accessing url”

Research seems to show that it is some sort of crossdomain issue. In /usr/local/WowzaMediaServer/conf directory is the crossdomain.xml file that is installed with Wowza…

If I have a transcoder/origin server on AWS EC2 pull the stream and use the akamai test player to watch the stream, it works just fine. This new transcoder pulls the stream just fine and I can watch it on an IOS device… but I keep getting this error when trying to watch it using the akamai player. ?? I’m baffled. Seems like something simple…

I started up the server in standalone mode so that I could watch things. Following is the console output… Maybe this will help.

Thank you,

Tim

[Transcoder01:/usr/local/WowzaMediaServer/bin]#./startup.sh

Configure logging: file:///usr/local/WowzaMediaServer/conf/log4j.properties

INFO server server-start Wowza Media Server 3 Monthly Edition 3.1.2 build1624 -

INFO server comment - Server License Key: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

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: 24

INFO server comment - Hardware Physical Memory: 15429MB/15921MB

INFO server comment - Hardware Swap Space: 18111MB/18111MB

INFO server comment - Max File Descriptor Count: 20000

INFO server comment - Open File Descriptor Count: 52

INFO server comment - OS Name: Linux

INFO server comment - OS Version: 2.6.32-220.el6.x86_64

INFO server comment - OS Architecture: amd64

INFO server comment - Java Name: Java HotSpot™ 64-Bit Server VM

INFO server comment - Java Vendor: Oracle Corporation

INFO server comment - Java Version: 1.7.0_05

INFO server comment - Java VM Version: 23.1-b03

INFO server comment - Java Spec Version: 1.7

INFO server comment - Java Home: /usr/local/java/jdk1.7.0_05/jre

INFO server comment - Java Max Heap Size: 10666MB

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[file.encoding]: UTF-8

INFO server comment - Java Timezone[user.timezone]: GMT

INFO server comment - Java Args[0]: -Xmx12000M

INFO server comment - Java Args[1]: -Djava.net.preferIPv4Stack=true

INFO server comment - Java Args[2]: -Dcom.sun.management.jmxremote=true

INFO server comment - Java Args[3]: -Dcom.wowza.wms.runmode=standalone

INFO server comment - Java Args[4]: -Dcom.wowza.wms.native.base=linux

INFO server comment - Java Args[5]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer

INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigURL=

INFO server comment - Java Args[7]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer

INFO server comment - Server runmode: standalone

INFO server comment - Server native.platform: linux

INFO server comment - Server threads[h/t]: 10/10

INFO server comment - JMX java.rmi.server.hostname: 123.123.123.123

INFO server comment - JMX bind attempt service:jmx:rmi://123.123.123.123:8084/jndi/rmi://123.123.123.123:8085/jmxrmi

INFO server comment - JMX password file: /usr/local/WowzaMediaServer/conf/jmxremote.password

INFO server comment - JMX access file: /usr/local/WowzaMediaServer/conf/jmxremote.access

INFO server comment - JMX bind successful

INFO server comment - CMDInterface now listening: [any]:8083

INFO vhost vhost-start defaultVHost -

INFO server comment - defaultVHost threads[h/t]:480/320 home:/usr/local/WowzaMediaServer

INFO vhost comment defaultVHost Bind attempt ([any]:1935:24)

INFO vhost comment defaultVHost Bind successful ([any]:1935)

INFO vhost comment defaultVHost Bind attempt ([any]:8086:1)

INFO vhost comment defaultVHost Bind successful ([any]:8086)

INFO server comment - ModuleStreamNameAlias.onAppStart: aliasMapFileStream: /usr/local/WowzaMediaServer/conf/aliasmap.stream.txt

INFO server comment - ModuleStreamNameAlias.onAppStart: aliasMapFilePlay: /usr/local/WowzaMediaServer/conf/aliasmap.play.txt

INFO application app-start definst transratelive/definst

INFO server comment - StreamNameAliasFile.load: size:0:1 hash:true matchAll:true

INFO server comment - ModuleStreamNameAlias.nameToAlias[play]: streamName:exp-us-wsc alias:{pattern: “*” alias:"${Stream.Name}" wildcardMatches:{[0]: “exp-us-wsc”}} result:exp-us-wsc

I figured out the problem.

By default on an AWS EC2 wowza instance, the SocketConfiguration in the VHost.xml file includes ports 1935,80,443 and 554. When building up and installing Wowza yourself, only port 1935 is listed here… I added the additional ports and all is good with the Akamai player.

See below!

Tim

24

*

1935,80,443,554

true

24000

65000

true

100

cupertinostreaming,smoothstreaming,sanjosestreaming,dvrchunkstreaming

com.wowza.wms.http.HTTPCrossdomain

*crossdomain.xml

none

com.wowza.wms.http.HTTPClientAccessPolicy

*clientaccesspolicy.xml

none

com.wowza.wms.http.HTTPProviderMediaList

*jwplayer.rss|*medialist.smil|*manifest-rtmp.f4m

none

com.wowza.wms.http.HTTPServerVersion

*

none