Getting Error while running WOWZA streaming server and WEBRTC [ via firefox ] - websocket

I'm using latest wowza streaming engine and while trying to send stream via webrtc, I get the following error.
I've followed the instructions on the official wowza docs and double checked them.
wsConnection.onerror: {"isTrusted":true} webrtc.js:260:1
stopPublisher webrtc.js:314:2
wsConnection.onclose webrtc.js:255:3
Firefox can't establish a connection to the server at ws://172.16.14.237:1935/webrtc-session.json.
Please let me know how to resolve this or what's causing this so I can move ahead with my project.
Any help will be much appreciated.

It doesn't appear that you have set up an SSL Host Port in your VHost file. You need to follow the steps shown in this part of the article
https://www.wowza.com/docs/how-to-use-webrtc-with-wowza-streaming-engine#install
It also appears that your StreamLock certificate is invalid
https://www.sslshopper.com/ssl-checker.html#hostname=https://<YOUR-STREAMLOCK-ID>.streamlock.net
So please ensure that you download the the following keystore file (.jks) from your Wowza Portal: <YOUR-STREAMLOCK-ID>.streamlock.net
Place that keystore file in your Wowza /conf directory
Create an HTTPS/StreamLock Host Port for port 443 using this keystore,
https://www.wowza.com/docs/how-to-get-ssl-certificates-from-the-streamlock-service#config4-0
Confirm that the Host Port is responding on port 443 by entering the following in a browser (it should return the Wowza version number)
https://<YOUR-STREAMLOCK-ID>.streamlock.net
and when publishing as WebRTC use the proper wss URL (don't specify port 1935). For example if using our example publisher
https://www.wowza.com/_private/webrtc/4.7.4/publish/
then the SDP URL would be wss://<YOUR-STREAMLOCK-ID>.streamlock.net/webrtc-session.json

Related

External IP + SSL

how can i use the external ip of my centos7 instance with https, like for example https://external_ip to open an application like https://external_ip:Port/my_application
Generate a self-sign certificate using openssl.
Check this out here:
https://stackoverflow.com/a/10176685/9662626
Open a https port on your webserver. Set the certificate in the config (I can't be specific here because I don't know about your operating system and your choice of web server). Finally setup a reverse proxy to proxy the web server port to your app port.

Unable to bind locally created project on default ports - moovweb sdk

I am trying to create a new project locally in the moovweb developer dashboard using moovweb windows sdk. But the newly created project fails to start with below error:
listen tcp 0.0.0.0:443: bind: An attempt was made to access a socket in a way
forbidden by its access permissions.
Perhaps there's something already listening on port 443?
and same error for port 80.
Of course, there are other applications running on these two ports. So how do I change the default port that moovweb binds any local project to?
I looked their documentation, but couldn't find any relevant information regarding this (or may b I didn't look hard enough).
I am using moovweb sdk v6.3.10
If you are unable to temporary shutdown the applications that are using ports 80 and 443, then you should start the moovweb server using the -p and -ssl-port settings in order to start your server using a different port.
For more information you can type:
moov help server
into your terminal

Wowza Server Configuration On Amazon EC2 Server

I am struggling to configure the Wowza Media Server on Amazon Server.
Success: - I have Successfully Installed Wowza Server on Amazon and Streaming is working with the Internal Private IP. Now, I have changed the Port from Default 1935 to Port 80. Now Binding with port 80 with Internal Private IP is working Fine i.e. 10.8..:80 this works fine.
Problem: - Now, When I configure port 80 instead of my private 10.8.. to my Public IP 54.76..
binding fails and i got error Bind Failed and Could not assign port. I have tried all the solution posted on stack overflow and also reinstalled the application several times.
Solution Tried : -
1) Restarting the Amazon and Wowza Server.
2) To verify firewall, I have installed IIS server and hosted dummy application it works with both private and public IP on port 80.
3) Installed Correct Java Version i.e. 1.8
4) Stopped the IIS server and Running Wowza Server.
Help is appreciated. Thanks in Advance.
Ensure you modify the security group settings and that all the appropriate ports are defined there. I would also test playback with the aws url they provide to ensure it isn't an odd routing issue. Lastly, you can review the quick-start guide for this process to ensure all basis are covered.
Lastly there are a ton of pre-built AMI's just for this purpose as well.

polygraph for https via proxy server

Can anyone help me setup web polygraph for testing an HTTPS servers via proxy servers in middle
linux machine:192.168.21.7
proxy server :192.168.21.9
https server : 192.168.21.11
This link contains the needed information:
http://www.web-polygraph.org/docs/userman/simple.html
Basically polygraph has couple files which are bundled with it and use for testing.
The manual I gave you give example that uses polysrv but on different distributions you will probably have different names for the tool(on ubuntu it's polygraph-server and polygraph-client)
You need to set the listening service ip+port outgoing "robot" ip and then start it using command line.
For https setup we will configure our pg file on server and client with SslWrap module.
Details of same can be found in http://www.web-polygraph.org/docs/reference/models/ssl.html

Red5 Problem with connecting from remote client

So I have this issue. The issue is I am unable to connect to my red5 server from a remote client. I also have not found any tutorials on how to install red5 so that remote clients can connect to it. However, here is what I have done...
Inside My MXML Flex File I try to connect to the computers IP that the server is running on(My Server is running from within Eclipse). The line for connecting looks like this netConnection.connect(rtmp://192.168.2.12/myApp, true);
All that happens is after a lot of minutes go by, I just get NetConnection.Connect.Failed and there is no log being output by Eclipse. Almost like it never even registers the connection that the remote client is trying to make.
The other interesting thing is that I am ABLE to connect to my Red5 Server using a different computer within my local home network just fine. But only when it is remote I am unable to connect.
I have changed my Red5-web.properties file and added this...
webapp.contextPath=/myApp
webapp.virtualHosts=*, 127.0.0.1, localhost, 192.168.2.14, 174.122.104.3
The 174 one is my website where the Flex Swf Resides on.
I think maybe somehow my computer is not setup or configured to allow these remote connections and is rejecting them or something, I'm not quite sure why a remote client can't connect. Does anyone have any idas?
Your help is greatly appreciated.
You may uninstall the red5 and reinstall it.
When it ask you the server ip address type your server's LAN adress (192.168.2.* or 10.0.0.* whatever). This solved my problem.
In my opinion, if you have at least one domain name that you own, the best way for you to go is to set up an Apache Http Server to your server machine, and create subdomains for both red5, rtmp and rtmpt. Make the Apache handle your incoming requests, and decide their correct routing there.
In case you don't own a domain, or the previous way is too time-taking to set up and get it work, you should just make sure that the ip address you're trying to connect to is not an internal IP.
In your example above you are trying to connect from the client to a 192.168... address. If you try to connect to it from within your LAN, it works, since that ip there is registered to your machine.
But when you take your notebook to your neighbor, and using his internet connection to access your site and connect to red5, the client (flex application) will also try to connect to that 192.168..., and your neighbor's router has no idea about your LAN, probably it doesn't have such an internal IP address either, but SURELY cannot connect to your server.
So instead of using 192.168... in your connection string, you should try using your external IP address (the 174... one):
netConnection.connect("rtmp://174.122.104.3/myApp", true);
This will work always, as far as you have a static IP address.
Also make sure, that your red5 server is accessible over the 80 port, or if it's not, specify the correct port number there.
For that you can do following thing...
These steps I took and it's solved my problem...
1.During the installation, you must have given ip 127.0.0.1 (localhost) and port :5080
2.firstly open the port (5080 and 1935) on firewall.
Visit http://windows.microsoft.com/en-in/windows/open-port-windows-firewall#1TC=windows-7
3.Now to go red5->conf->red5.properties and open this file in notepad++. (or any other editor)
4.repalce http.host and rtmp.host ip with your ip address (ipv4)
5.start the red5 service.
6.Now check http://yourip:5080
It will start working, and you can access it from other system also (in the same network Obviously )

Resources