Wowza setup on server working on intranet but not over internet

Wowza Streaming Engine
1

We’re testing streaming services at a new server, I configured a test with wowza and it works locally in the server and with any computer in the intranet even using the public IP but it won’t work using a computer outside of the network over the internet. Port 1935 is open and I’m stuck as to what could it be, any ideas?

2

Forgot to say that we’re using JWPlayer7 for this test

3

Hello,

What error are you getting with JW Player? Have you set up port forwarding from the router Public IP address to the Wowza Server’s Private IP address?

By default, Wowza Streaming Engine uses the following ports for streaming:

TCP 1935: RTMP (all variants), RTSP, Microsoft Smooth Streaming, Apple HTTP Live Streaming (HLS), WOWZ™

UDP 6970-9999: RTP UDP Streaming

TCP 8084-8085: JMX/JConsole monitoring and administration

TCP 8086: HTTP administration

You (or a network administrator) must access your network firewall to open and forward these ports to your server that is hosting Wowza. This is not a process I am able to support, however, this website, www.portforward.com, provides all sorts of instructions for various routers.

Regards,

JasonT

4

Hello,

Good to hear your stream is working now!

Regards,

JasonT

5

Hello,

What error are you getting with JW Player? Have you set up port forwarding from the router Public IP address to the Wowza Server’s Private IP address?

By default, Wowza Streaming Engine uses the following ports for streaming:

TCP 1935: RTMP (all variants), RTSP, Microsoft Smooth Streaming, Apple HTTP Live Streaming (HLS), WOWZ™

UDP 6970-9999: RTP UDP Streaming

TCP 8084-8085: JMX/JConsole monitoring and administration

TCP 8086: HTTP administration

You (or a network administrator) must access your network firewall to open and forward these ports to your server that is hosting Wowza. This is not a process I am able to support, however, this website, www.portforward.com, provides all sorts of instructions for various routers.

Regards,

JasonT

Thanks Jason, we finally figured out what the issue was. We were pointing to the videos on the server using its intranet IP and not its public IP.