I have set up a server and when I stream to localhost or 192.168.1.11 (My servers IP) the live streams work great. When I go to use the public IP that i get from http://ipchicken.com/ it does not work.
I have opened the 1935 port on my router and have also tested it here:http://www.canyouseeme.org/
and it says 1935 is open. But when I try to stream to it, it does not work.
Any help please. Thanks
Ensure that Wowza is listening and your router is forwarded correctly by typing in your browser URL bar: “http://[public-ip-address]:1935”
You should see the Wowza version number displayed. If not, then it is likely your router is not forwarded to the correct IP/port of your Wowza server.
Wowza responds when I use localhost or my normal IP but when i use the public IP it does not work.
I have port forwarded that port (1935).
I have tried turning off all firewalls but nothing… I’m stuck.
Have you tried to access other services from the wan, eg www
I am having the same issue and port forwarding is working since I can see the Wowza version.
When I am using ffmpeg as live encoder pointing to local ip address it is working correctly, whereas using a public ip address ffmpeg instance finishes after the RTP timeout of 90 seconds. Actually I can see the name of the incoming stream in the wowza manager, but I cannot watch it…
Any idea how to configure Wowza for using ffmpeg as live enconder pointing to a public ip address?
Hi all,
I’ve solved the problem using Flash Media Encoder but I have not been able to solve it yet with ffmpeg… Hence the problem is not related with Wowza.
Thank you for sharing that update with the community.
Hi Raul -
This does sound like a routing issue, not something specific to Wowza Streaming Engine. If you’re able to publish to the public IP from outside your LAN, then it’s likely you’ll need to configure routing specific to your workflow. Depending on your equipment, you might be able to use NAT On A Stick or other configurations to create a path to your public IP.
Best regards,
Andrew
Hi Andrew,
I also think the problem is related with my network configuration. I will try some tests using iptables to reroute my requests to the correct local ip address.
Thanks.