Wowza Community

WebRTC SDP (WebSocket connection failed)

Hello,

I setup WebRTC configuration following this post https://www.wowza.com/docs/how-to-use-webrtc-with-wowza-streaming-engine, i already created streamlock certificate along with password and update configuration accordingly.

when i try to publish stream by running wowza webrtc addong. it throw error

WebSocket connection failed: wss://5ab***25b9d.streamlock.net/webrtc-session.json

Where 5ab***25b9d.streamlock.net is my cert filename.

Now not sure how to create webrtc-session.json file i adjust wss url by guess. can you help me creating SDP url or what is the correct format for creating SDP URL.

Need help to setup webrtc properly.

Note: i am using wowza configured in AWS Cloud.

Hello,

Your problem is the same me, after fixing in [install-dir]/conf/VHost.xml and everything is working. You should re-check the port 443 configuration with the streamlock certificate for wowza. Following this link : https://www.wowza.com/docs/how-to-get-ssl-certificates-from-the-streamlock-service

The same issue : https://www.wowza.com/community/questions/8006/problems-with-webrtc.html

Regards,

Quang

Hello @Muhammad Irfan

If the linked article does not work, please send the below for further review by a support ticket:

Click this link to open a support ticket and send the below folders for review:

[install-dir]/conf

[install-dir]/logs

[install-dir]/htdocs

If you are not sure how to get this information please see the following tutorial.

https://www.wowza.com/docs/how-to-create-a-compressed-zip-file-in-windows-os-x-and-linux

Regards,

JasonT

I was having this issue too, and it turned out to be an issue with my firewall on Windows 10.

It turned out that that relevant ports on my server (which is just my laptop) weren’t open. Conceptually, 5ab***25b9d.streamlock.net just redirects to your server’s public IP address. You may want to verify that the relevant ports are open.

I noticed something was up when I could navigate to

localhost:8088/enginemanager, and

192.168.xxx.xxx:8088/enginemanager , (my internal IP) but could NOT get to

98.26.xx x.xxx:8088/enginemanager (my external IP)

I thought the only issue would be port-forwarding, and I set my router to forward port 8088 to my server. It still didn’t work.

I followed the instructions at http://ctl.jhsph.edu/help/index.cfm/go/faq.display/faqID/105/ (which are for Windows 7, but worked on Windows 10) to open some ports associated with Wowza: 1935, 8088, and 443. This allowed me to access the enginemanager through my external IP, and for my WebSocket to finally connect.

Hope that helps!

Hello I have same websocket connection failed but I am running my web server on http is that issue.

Hi - having a similar issue, except on Mac. How can I check the that relevant ports are open?

SSL/TLS encryption is required for WebRTC, please use HTTPS.