Unable to Connect to Wowza Streaming Engine Manager on the browser

system · March 29, 2014, 11:38pm

Hello,

I hope I can get an urgent help… I actually just completed the installation of the Wowza Streaming Engine (Linux OS) and I am unable to connect to the manager via the browser. I really do not know where the fault might be because when I start the Wowza Streaming Engine, it does not give any error but this is the message I received when I start the manager:

root@livewaymedia # sudo ./startmgr

.sh

Sat, 29 Mar 2014 22:30:43 478 GMT, BootStrap Info: Home Directory=/usr/local/Wow

zaStreamingEngine-4.0.3/manager/lib

Sat, 29 Mar 2014 22:30:43 540 GMT, BootStrap Info: Main-Class=net.winstone.Winst

one

2014-03-29 17:30:43,862 [main] INFO net.winstone.boot.BootStrap - stage 1/3: L

oading arguments…

2014-03-29 17:30:43,866 [main] INFO net.winstone.boot.BootStrap - stage 2/3: L

oading WebApplication configuration…

2014-03-29 17:30:43,866 [main] INFO net.winstone.boot.BootStrap - stage 3/3: c

ompute JSP classpath…

2014-03-29 17:30:44,004 [main] INFO net.winstone.core.HostConfiguration - Begi

nning extraction from war file

2014-03-29 17:30:44,097 [main] INFO net.winstone.core.WebXmlParser - Found and

enabled the local Servlet 2.5 XSD replacement

2014-03-29 17:30:45,429 [main] WARN net.winstone.core.WebXmlParser - XML Error

(Line 2): Document is invalid: no grammar found.

2014-03-29 17:30:45,430 [main] WARN net.winstone.core.WebXmlParser - XML Error

(Line 2): Document root element “web-app”, must match DOCTYPE root “null”.

2014-03-29 17:30:45,811 [main] INFO net.winstone.core.WebAppConfiguration - Ac

cess logging disabled - no logger class defined

Configure logging: file:///usr/local/WowzaStreamingEngine/manager/conf/log4j.pro

perties

INFO com.wowza.wms.logging.Log4jStartupListener OS Name: Linux:

INFO com.wowza.wms.logging.Log4jStartupListener OS Version: 2.6.32-431.5.1.el6

.x86_64:

INFO com.wowza.wms.logging.Log4jStartupListener OS Architecture: amd64:

INFO com.wowza.wms.logging.Log4jStartupListener Java Name: Java HotSpot™ 64

-Bit Server VM:

INFO com.wowza.wms.logging.Log4jStartupListener Java Vendor: Oracle Corporatio

n:

INFO com.wowza.wms.logging.Log4jStartupListener Java Version: 1.7.0_51:

INFO com.wowza.wms.logging.Log4jStartupListener Java VM Version: 24.51-b03:

INFO com.wowza.wms.logging.Log4jStartupListener Java Spec Version: 1.7:

INFO com.wowza.wms.logging.Log4jStartupListener Java Home: /usr/java/jdk1.7.0_

51/jre:

INFO com.wowza.wms.logging.Log4jStartupListener Java Max Heap Size: 7129MB:

INFO com.wowza.wms.logging.Log4jStartupListener Java Architecture: 64:

INFO com.wowza.wms.logging.Log4jStartupListener Java Locale[user.language]: en

:

INFO com.wowza.wms.logging.Log4jStartupListener Java Locale[user.country]: US:

INFO com.wowza.wms.logging.Log4jStartupListener Java Locale[file.encoding]: UT

F-8:

INFO com.wowza.wms.logging.Log4jStartupListener Java Timezone[user.timezone]:

US/Central:

INFO com.wowza.wms.logging.Log4jStartupListener Java Args[0]: -Dcom.wowza.wms.

ConfigURL="":

INFO com.wowza.wms.logging.Log4jStartupListener Java Args[1]: -Dcom.wowza.wms.

ConfigHome=/usr/local/WowzaStreamingEngine/manager:

INFO com.wowza.wms.logging.Log4jStartupListener Java Args[2]: -Djava.io.tmpdir

=/usr/local/WowzaStreamingEngine/manager/temp:

INFO com.wowza.wms.logging.Log4jStartupListener Java Args[3]: -Dlog4j.configur

ation=file:///usr/local/WowzaStreamingEngine/manager/conf/winstone.properties:

INFO com.wowza.wms.logging.Log4jStartupListener Java Args[4]: -Djava.net.prefe

rIPv4Stack=true:

2014-03-29 17:30:46,228 [main] INFO net.winstone.core.WebAppConfiguration - we

bapp Initializing Spring root WebApplicationContext

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:file:/usr/local/WowzaStreamingEngine-4.0.3/manager/

lib/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/usr/local/WowzaStreamingEngine-4.0.3/manager/

temp/WEB-INF/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.clas

s]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

INFO org.hibernate.validator.util.Version Hibernate Validator null

INFO com.wowza.wms.server.ManagerConfiguration Loading configuration from /usr

/local/WowzaStreamingEngine/manager/conf/Manager.xml:

INFO com.wowza.wms.server.ManagerConfiguration Loading configuration from /usr

/local/WowzaStreamingEngine/manager/conf/Manager.xml:

INFO com.wowza.wms.webapp.RequestLoggingFilter RequestLoggingFilter disabled,

no HTTP requests will be logged:

2014-03-29 17:30:52,063 [main] INFO net.winstone.core.WebAppConfiguration - we

bapp Initializing Spring FrameworkServlet ‘wowzaapp’

Mar 29, 2014 5:30:53 PM org.apache.jasper.EmbeddedServletOptions

WARNING: Warning: Invalid value for the initParam fork. Will use the default val

ue of “true”

2014-03-29 17:30:53,559 [main] INFO net.winstone.core.HostConfiguration - Depl

oy web application: prefix webroot [/usr/local/WowzaStreamingEn

gine/manager/temp]

2014-03-29 17:30:53,571 [main] INFO net.winstone.core.listener.HttpListener -

HTTP Listener started: port=8088

2014-03-29 17:30:53,578 [LauncherControlThread[ControlPort=-1]]] INFO net.winst

one.Server - Winstone Servlet Engine v1.0.5 running: controlPort=disabled

Sat, 29 Mar 2014 22:30:53 578 GMT, BootStrap Info: Exit

Then once I try connecting via a browser, (http://myserver-ip:8088/enginemanager) it gives me a page cannot be displayed error.

Please, what do I do to correct this?

Thanks.

sal_jefferson · March 30, 2014, 6:15am

Hi there, are you using a Wowza 3.x license with a Wowza 4 install?

The two licenses are not compatible between versions so a 3.x license will not work on 4.x

Salvadore

Philip_Neabueze · March 30, 2014, 11:36pm

Hi Salvadore,

Thanks for the reply. But I am using the license key sent to us at the launch of the new streaming engine 4. Here is an excerpt of the mail with a license info:

Hello Solomon,

Weâ€™re excited to announce the new Wowza Streaming Engine, version 4 of our

award-winning Wowza Media Server software.

As a current customer, your subscription includes free upgrades. Hereâ€™s

your new Wowza Streaming Engine key, so you can get started right away!

ENGM4-XXXXX-XxxxX-xXxxx-xXXxx-XXXXX

Download the Wowza Streaming Engine™ Installer from

https://www.wowza.com/pricing/installer. Please refer to the Wowza Streaming

Engine Software User’s Guide for additional license key installation

instructions found at

https://www.wowza.com/docs/user-guides.

Wowza Streaming Engine 4 combines the powerful Wowza Media Server software

you currently use with several new, powerful elements:

New Wowza Streaming Engine Manager, a browser-based admin panel that allows

users to conveniently set up, manage, monitor, and measure video and audio

streams using a computer, tablet, or phone browser

Support for MPEG-DASH
Performance acceleration

To learn more about Wowza Streaming Engine, visit the overview page:

https://www.wowza.com/products/streaming-engine

Happy streaming,

The Wowza Team

Philip_Neabueze · March 31, 2014, 1:02pm

Thanks. Sent it.

Philip_Neabueze · April 1, 2014, 9:54am

Thanks Matt, its solved. I set iptables to off as you instructed and I am able to connect now.

Jason_Hilton · April 17, 2015, 12:45pm

Hi,

For more information on iptables please see the site below

The Beginner’s Guide to iptables, the Linux Firewall

Jason

sal_jefferson · November 4, 2015, 9:06am

It sounds like you may need to forward TCP port 1935 (in your router) to the computer running Wowza. Or on your network you need to map port 1935 to the server running Wowza.

A simple test would be to connect to the server remotely(outside of your network)

If you enter [wowza-ip]:1935 in a browser remotely, it should display Wowza version and build numbers. If not port forwarding is in order.

And use a public IP in the player instead of localhost. If you don’t know what it is, you can see it here: http://www.dnsstuff.com

This is a helpful resource:

http://portforward.com/

Regards,

Salvadore

Matt_Young · March 30, 2014, 8:29pm

Please zip up a copy of your conf/, logs, and manager/logs directories and send it to support@wowza.com along with a reference to this thread for further review.

Matt_Young · April 1, 2014, 8:37am

Great, I’m glad you got it working. Thanks for the update.

Alain_Vandebosch · April 16, 2015, 5:10pm

Hi,

i have the same problem.

iptables in witch file can i find this option.

Thanhs

Dinesh_Chebrolu · November 3, 2015, 6:22pm

Hi,

i am new to this wowza Engine.

i am trying to connect WOWZA Streaming engine from another network, i checked the 8088 port using port fwd tester it says closed, don’t know why it is not opening in netgear router, to access wowza remotely do i have to open 8088 port on my router? Can anyone help how to access WOWZA from remote.

These are the ports i tried to opened in my router 1935,8088 & 8086 but with fwd tester it says closed

http://192.168.1.6:8088/enginemanger/home.htm this links work fine on my local network.

192.168.1.6:1935 with this link i can see edition information

Thanks in Advance

D

Topic		Replies	Views
Streaming Engine won't start up Wowza Streaming Engine	7	5548	March 26, 2015
Upgraded from 4.0.1 to 4.0.4 stream engine mgr wont resolve Wowza Streaming Engine	3	2399	July 24, 2014
This webpage is not available Wowza Streaming Engine Manager Wowza Streaming Engine	3	2340	December 24, 2014
Wowza Media Streaming Engine hangs when accessing Logs Wowza Streaming Engine	1	1937	August 26, 2015
Unable to connect to Engine Manager Wowza Streaming Engine server-administration	11	7813	March 24, 2015

Unable to Connect to Wowza Streaming Engine Manager on the browser

Related topics