SSL certificate name invalid

[Murangaza_hans]

Hello again, i have a developper license. I am getting this error after having installed a StreamLock certificate.

About the MediaCp, is there any free offer for development. This is the error in the console: WebSocket connection to ‘wss://192.168.56.1:8880/webrtc-session.json’ failed: Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID

[Rose_Power-Wowza_Com]

That error can be triggered when you don’t have the correct port configured. Check that you have port 443 configured properly:

Sometimes people have this WebRTC HTTP Provider in HostPort 1935 and it should only be in HostPort 443 ( Make sure it’s the 2nd to last entry just above HTTPServerVersion:

<HTTPProvider>
 <BaseClass>com.wowza.wms.webrtc.http.HTTPWebRTCExchangeSessionInfo</BaseClass>
      <RequestFilters>*webrtc-session.json</RequestFilters>
      <AuthenticationMethod>none</AuthenticationMethod>
        </HTTPProvider>

You will need to uncomment HostPort 443 as that will be needed for SSL streaming for WebRTC.

Save and restart your Wowza Server for changes to take effect.

[Murangaza_hans]

I have tried but now i getting an error: WebSocket connection to ‘wss://XXXXXXXX41e28.streamlock.net/webrtc-session.json’ failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED. Is there any solution?

[Amara_Graham]

I’ve found this issue when I did not configure my certificate. Have you followed these steps in the Configuring Wowza Streaming Engine to use your StreamLock certificate? https://www.wowza.com/docs/how-to-get-ssl-certificates-from-the-streamlock-service

[Rose_Power-Wowza_Com]

At this point, we need a support ticket from you to view your complete configuration. There are too many variables involved in a WebRTC workflow and we can’t debug in the forums without full access to your files.

You can submit one here and our WebRTC engineers will walk you through the setup after they find the error.

[Murangaza_hans]

i dont know where The xml configuration file is located.

[Amara_Graham]

Using a streamlock certificate, your SDP url should look like the following - wss://{certificate_name}.streamlock.net/webrtc-session.json where you replace {certificate_name} with your streamlock certificate name (typically a series of numbers and letters).

[Rose_Power-Wowza_Com]

I have edited your streamlock certificate to include X’s. You were sharing your private SSL information that is supposed to be kept private to protect your content.

[Murangaza_hans]

Okay now i have modified to port 443. And again an error: WebSocket connection to ‘wss://5ebba1af41e28.streamlock.net/webrtc-session.json’ failed: Error during WebSocket handshake: Unexpected response code: 200