Baffled - Trying to get Wowza to listen on Port 1935
OK, after a fresh uninstall/reinstall (including redownloading 1.7.2 rpm package) I cannot get Wowza to listen on Port 1935. I have started Wowza as a Standalone and as a service. Here is my latest access log:
I ran the following Linux command to check to see if the port is open:
This shows that the port is open for RTMP i.e.
1935/tcp open rtmp
However when going to the browser http://myserverip:1935 it comes up
"can't establish a connection to the server at myserverip:1935"
This is the second time I've uninstalled and reinstalled. I've checked the forums, the documentation and still can't figure out what's going on.
Any help would be greatly appreciated! Thanks in advance.
#Version: 1.0 #Start-Date: 2009-08-25 10:36:48 CDT #Software: Wowza Media Server Pro 1.7.2 build12107 #Date: 2009-08-25 #Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment INFO server server-start 2009-08-25 10:36:48 - - - - - 0.326 - - - - - - Wowza Media Server Pro Unlimited 1.7.2 build12107 - INFO server comment 2009-08-25 10:36:48 - - - - - 0.328 - - - - - - - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-YKUUA INFO server comment 2009-08-25 10:36:48 - - - - - 0.328 - - - - - - - Maximum connections: Unlimited INFO server comment 2009-08-25 10:36:48 - - - - - 0.331 - - - - - - - Hardware Available Processors: 2 INFO server comment 2009-08-25 10:36:48 - - - - - 0.332 - - - - - - - Hardware Physical Memory: 1599MB/4054MB INFO server comment 2009-08-25 10:36:48 - - - - - 0.332 - - - - - - - Hardware Swap Space: 1992MB/1992MB INFO server comment 2009-08-25 10:36:48 - - - - - 0.333 - - - - - - - Max File Descriptor Count: 1024 INFO server comment 2009-08-25 10:36:48 - - - - - 0.333 - - - - - - - Open File Descriptor Count: 31 INFO server comment 2009-08-25 10:36:48 - - - - - 0.334 - - - - - - - OS Name: Linux INFO server comment 2009-08-25 10:36:48 - - - - - 0.334 - - - - - - - OS Version: 2.6.18-128.2.1.el5PAE INFO server comment 2009-08-25 10:36:48 - - - - - 0.334 - - - - - - - OS Architecture: i386 INFO server comment 2009-08-25 10:36:48 - - - - - 0.335 - - - - - - - Java Name: Java HotSpot(TM) Server VM INFO server comment 2009-08-25 10:36:48 - - - - - 0.335 - - - - - - - Java Vendor: Sun Microsystems Inc. INFO server comment 2009-08-25 10:36:48 - - - - - 0.336 - - - - - - - Java Version: 1.6.0_15 INFO server comment 2009-08-25 10:36:48 - - - - - 0.336 - - - - - - - Java VM Version: 14.1-b02 INFO server comment 2009-08-25 10:36:48 - - - - - 0.336 - - - - - - - Java Spec Version: 1.6 INFO server comment 2009-08-25 10:36:48 - - - - - 0.337 - - - - - - - Java Home: /opt/jdk1.6.0_15/jre INFO server comment 2009-08-25 10:36:48 - - - - - 0.337 - - - - - - - Java Max Heap Size: 739MB INFO server comment 2009-08-25 10:36:48 - - - - - 0.337 - - - - - - - Java Architecture: 32 INFO server comment 2009-08-25 10:36:48 - - - - - 0.36 - - - - - - - CMDInterface now listening: [any]:8083 INFO server comment 2009-08-25 10:36:48 - - - - - 0.41 - - - - - - - vhost home directory: /usr/local/WowzaMediaServerPro INFO vhost vhost-start 2009-08-25 10:36:49 - - - - - 0.897 - - - - - - _defaultVHost_ - INFO vhost comment 2009-08-25 10:36:49 - - - - - 0.997 - - - - - - _defaultVHost_ RTMP/RTMPT bind attempt ([any]:1935) INFO vhost comment 2009-08-25 10:36:49 - - - - - 0.998 - - - - - - _defaultVHost_ Bind successful ([any]:1935)
I ran the following Linux command to check to see if the port is open:
nmap -sT O localhost
This shows that the port is open for RTMP i.e.
1935/tcp open rtmp
However when going to the browser http://myserverip:1935 it comes up
"can't establish a connection to the server at myserverip:1935"
This is the second time I've uninstalled and reinstalled. I've checked the forums, the documentation and still can't figure out what's going on.
Any help would be greatly appreciated! Thanks in advance.
Are you sure there are no firewalls in the way?
Do a netstat -lp you should see a binding *:1935 owned by a java process. If that's the case, then it's listening and there's something network related in the way. (local firewall, external firewall, ipchains, etc).
For example here's what my output looks like on my Wowza 2 demo box:
Do a netstat -lp you should see a binding *:1935 owned by a java process. If that's the case, then it's listening and there's something network related in the way. (local firewall, external firewall, ipchains, etc).
For example here's what my output looks like on my Wowza 2 demo box:
wowza1:/usr/local/WowzaMediaServer/logs# netstat -lp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:1935 *:* LISTEN 7030/java
tcp 0 0 *:8083 *:* LISTEN 7030/java
tcp 0 0 *:ssh *:* LISTEN 2340/sshd
tcp 0 0 *:https *:* LISTEN 7030/java
tcp 0 0 *:36220 *:* LISTEN 7030/java
--CHris
Thanks for the post. I'm not getting port 1935 showing open with your instructions. I just realized that running the nmap -sT O localhost command shows the port open on localhost only. I've put in a ticket to the dedicated server hosting company to open up the port in the firewall.
I'm assuming that's the issue. Strange that it was closed though as I had wowza up and running for a couple of months before it stopped working.
If they don't get it resolved is there a specific command I can use to open the port myself?
I'm running RedHat Centos 5. Thanks.
I'm assuming that's the issue. Strange that it was closed though as I had wowza up and running for a couple of months before it stopped working.
If they don't get it resolved is there a specific command I can use to open the port myself?
I'm running RedHat Centos 5. Thanks.
It could be closed under iptables. The command to open port 1935 is:
It could also be closed on an external firewall that you probably do not have access to.
Charlie
iptables -I INPUT -p tcp --destination-port 1935 -j ACCEPT
It could also be closed on an external firewall that you probably do not have access to.
Charlie
Thanks, Charlie. I had them open the port for incoming and outgoing on the firewalls and all is well now. I am still baffled as to how it was closed after working fine but at least it's working now. Thanks again!
