Failed to connect to server - custom RTMP

[marlostanfield]

Hi there,

I am using a custom RTMP server to broadcast live to an application that I developed.

I am using Wowza and AWS

All was working ok until recently. The changes I made was to move my DNS from godaddy to AWS

here are the log files

https://obsproject.com/logs/5LBTHJxCSTVZkyHB

any help would be greatly appreciated.

 

[Harold]

The server isn't running on the IP address or the port isn't opened.

 

[marlostanfield]

The server isn't running on the IP address or the port isn't opened.

Thanks for the reply Harold.

The server is up and running on that IP

Im currently doing a port scan to see if port 1935 is open

AWS support says it is open though

 

[marlostanfield]

$ nmap -Pn -p 1935 54.202.198.121 Starting Nmap 6.40 ( http://nmap.org ) at 2020-06-16 09:04 UTC Nmap scan report for ec2-54-202-198-121.us-west-2.compute.amazonaws.com (54.202.198.121) Host is up (0.079s latency). PORT STATE SERVICE 1935/tcp closed rtmpNmap done: 1 IP address (1 host up) scanned in 0.14 seconds ----- Please note, in the output above, the STATE of the port is 'closed' which means that the port is accessible but no application is listening on it. If the port was inaccessible or blocked on OS level, it would have shown the state as 'filtered'. Please refer https://nmap.org/book/man-port-scanning-basics.html

Thus, I would like to suggest you to please verify if the application/service associated with port 1935 is running or not. If not, please start it and run the netstat command again to check. You could also connect with the application vendor or the system admin for further assistance pertaining to the application.

This is the response from AWS support, any ideas?

 

[Harold]

you've checked the server side with "netstat -lnop | grep :1935"?

 

[marlostanfield]

I ran $ sudo netstat -tulpn | grep 1935

but it returned nothing

When logging as a ec2-user I get the attached error.

running your command with sudo it returns nothing as well.

thanks for all your help Harold

 

[Harold]

then the server isn't listening on 1935

 

[marlostanfield]

then the server isn't listening on 1935

Thanks Harold.

So is this something I need to change on Wowza or AWS?

 

[R1CH]

Your Wowza server configuration is likely the issue, there's no issue on AWS side if the port is reachable but closed.

 

[marlostanfield]

Your Wowza server configuration is likely the issue, there's no issue on AWS side if the port is reachable but closed.

thanks R1CH!

you are bang on the money, my wowza licence expired! epic fail!

thanks for all the help Harold and R1CH!