# Does Wowza streamlock support Subject Alternative Name?

**URL:** <https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003>\
**Category:** Wowza Streaming Engine\
**Created:** [March 14, 2019, 3:57pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003 "2019-03-14T15:57:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sAM\_ElMorabit](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@sAM\_ElMorabit](https://community.wowza.com/u/sAM_ElMorabit)\
**Post date:** [March 14, 2019, 3:57pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003/1 "2019-03-14T15:57:37Z")

</div>

Using Wowza StreamLock Certificate I am getting the following error in chrome **NET::ERR\_CERT\_COMMON\_NAME\_INVALID**

According to google beginning with Chrome 58, the Chrome browser no longer uses the Common Name (CN) field to validate an SSL certificate. Instead, it only uses the Subject Alternative Name field.

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [March 14, 2019, 8:23pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003/2 "2019-03-14T20:23:43Z")

</div>

Tech support is suggesting that this error can be thrown if your StreamLock certificate has expired [@sAM ElMorabit](http://community.wowza.com/community/questions/50934/does-wowza-streamlock-support-subject-alternative.html#). You can check the status here:

[https://www.sslshopper.com/ssl-checker.html](https://www.sslshopper.com/ssl-checker.html)

They tested StreamLock in the latest version of Chrome and had no issue. If your certificate is still valid and that’s not the issue, please submit a support ticket and we’ll diagnose the problem for you.

[https://www.wowza.com/support/open-ticket](https://www.wowza.com/support/open-ticket)

---

<div class="post-metadata">

**Author:** ![Andrew\_Kennedy1](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@Andrew\_Kennedy1](https://community.wowza.com/u/Andrew_Kennedy1)\
**Post date:** [March 14, 2019, 8:24pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003/3 "2019-03-14T20:24:00Z")

</div>

Hi,

The error suggests some other issue as it is saying the common name is invalid.

How have you got your VHost.xml configured and how are you accessing your server, ie. what is the URL you are using ?

Andrew.

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [March 14, 2019, 9:21pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003/4 "2019-03-14T21:21:44Z")

</div>

To answer directly though your question about whether or not Wowza Streamlock supports Subject Alternative Name field, yes it does.

Please see this example:

```auto
 ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
  DNSName: 50c68a6b4a093.streamlock.net
  DNSName: www.50c68a6b4a093.streamlock.net
]

```

---

<div class="post-metadata">

**Author:** ![sAM\_ElMorabit](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@sAM\_ElMorabit](https://community.wowza.com/u/sAM_ElMorabit)\
**Post date:** [March 15, 2019, 1:52pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003/5 "2019-03-15T13:52:13Z")

</div>

The following is the URL I am using :

**_[https://66.77.62.29/CHAN-375/CHAN-375\_1.stream/playlist.m3u8](https://66.77.62.29/CHAN-375/CHAN-375_1.stream/playlist.m3u8)_**

as for VHost.xml:

**_StreamLock_**

**_443 192.168.116.29_**

**_Streaming_**

**_${com.wowza.wms.TuningAuto}_**

**_true 65000 65000 65000 true 100_**

**_cupertinostreaming,smoothstreaming,sanjosestreaming,dvrchunkstreaming,mpegdashstreaming_**

**_com.wowza.wms.http.HTTPCrossdomain \*crossdomain.xml none_**

**_com.wowza.wms.http.HTTPClientAccessPolicy \*clientaccesspolicy.xml none com.wowza.wms.http.HTTPProviderMediaList \*jwplayer.rss|\*jwplayer.smil|\*medialist.smil|\*manifest-rtmp.f4m none_**

**_com.wowza.wms.timedtext.http.HTTPProviderCaptionFile .ttml|.srt|.scc|.vtt none com.wowza.wms.webrtc.http.HTTPWebRTCExchangeSessionInfo_**

**_\*webrtc-session.json none_**

**_com.wowza.wms.http.HTTPServerVersion \* none_**

**_C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.7.5/conf/5bac76fd46024.streamlock.net.jks_**

**_xxxxxxxxx_**

**_JKS_**

**_TLS_**

**_SunX509 TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256,TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256,TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA256,TLS\_ECDH\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256,TLS\_ECDH\_RSA\_WITH\_AES\_128\_CBC\_SHA256,TLS\_DHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256,TLS\_DHE\_DSS\_WITH\_AES\_128\_CBC\_SHA256,TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA,TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA,TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA,TLS\_ECDH\_ECDSA\_WITH\_AES\_128\_CBC\_SHA,TLS\_ECDH\_RSA\_WITH\_AES\_128\_CBC\_SHA,TLS\_DHE\_RSA\_WITH\_AES\_128\_CBC\_SHA,TLS\_DHE\_DSS\_WITH\_AES\_128\_CBC\_SHA,TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256,TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256,TLS\_RSA\_WITH\_AES\_128\_GCM\_SHA256,TLS\_ECDH\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256,TLS\_ECDH\_RSA\_WITH\_AES\_128\_GCM\_SHA256,TLS\_DHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256,TLS\_DHE\_DSS\_WITH\_AES\_128\_GCM\_SHA256,TLS\_ECDHE\_ECDSA\_WITH\_3DES\_EDE\_CBC\_SHA,TLS\_ECDHE\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA,SSL\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA,TLS\_ECDH\_ECDSA\_WITH\_3DES\_EDE\_CBC\_SHA,TLS\_ECDH\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA,SSL\_DHE\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA,SSL\_DHE\_DSS\_WITH\_3DES\_EDE\_CBC\_SHA,TLS\_EMPTY\_RENEGOTIATION\_INFO\_SCSV,TLS\_DH\_anon\_WITH\_AES\_128\_GCM\_SHA256,TLS\_DH\_anon\_WITH\_AES\_128\_CBC\_SHA256,TLS\_ECDH\_anon\_WITH\_AES\_128\_CBC\_SHA,TLS\_DH\_anon\_WITH\_AES\_128\_CBC\_SHA,TLS\_ECDH\_anon\_WITH\_3DES\_EDE\_CBC\_SHA,SSL\_DH\_anon\_WITH\_3DES\_EDE\_CBC\_SHA,SSL\_RSA\_WITH\_DES\_CBC\_SHA,SSL\_DHE\_RSA\_WITH\_DES\_CBC\_SHA,SSL\_DHE\_DSS\_WITH\_DES\_CBC\_SHA,SSL\_DH\_anon\_WITH\_DES\_CBC\_SHA,SSL\_RSA\_EXPORT\_WITH\_DES40\_CBC\_SHA,SSL\_DHE\_RSA\_EXPORT\_WITH\_DES40\_CBC\_SHA,SSL\_DHE\_DSS\_EXPORT\_WITH\_DES40\_CBC\_SHA,SSL\_DH\_anon\_EXPORT\_WITH\_DES40\_CBC\_SHA,TLS\_RSA\_WITH\_NULL\_SHA256,TLS\_ECDHE\_ECDSA\_WITH\_NULL\_SHA,TLS\_ECDHE\_RSA\_WITH\_NULL\_SHA,SSL\_RSA\_WITH\_NULL\_SHA,TLS\_ECDH\_ECDSA\_WITH\_NULL\_SHA,TLS\_ECDH\_RSA\_WITH\_NULL\_SHA,TLS\_ECDH\_anon\_WITH\_NULL\_SHA,SSL\_RSA\_WITH\_NULL\_MD5,TLS\_KRB5\_WITH\_3DES\_EDE\_CBC\_SHA,TLS\_KRB5\_WITH\_3DES\_EDE\_CBC\_MD5,TLS\_KRB5\_WITH\_DES\_CBC\_SHA,TLS\_KRB5\_WITH\_DES\_CBC\_MD5,TLS\_KRB5\_EXPORT\_WITH\_DES\_CBC\_40\_SHA,TLS\_KRB5\_EXPORT\_WITH\_DES\_CBC\_40\_MD5_**

**_SSLv2Hello,SSLv3,TLSv1,TLSv1.1,TLSv1.2_**

---

<div class="post-metadata">

**Author:** ![Andrew\_Kennedy1](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@Andrew\_Kennedy1](https://community.wowza.com/u/Andrew_Kennedy1)\
**Post date:** [March 15, 2019, 2:09pm UTC](https://community.wowza.com/t/does-wowza-streamlock-support-subject-alternative-name/53003/6 "2019-03-15T14:09:14Z")

</div>

Hi,

The problem I suspect is you are using this URL

**_[https://66.77.62.29/CHAN-375/CHAN-375\_1.stream/playlist.m3u8](https://66.77.62.29/CHAN-375/CHAN-375_1.stream/playlist.m3u8)_**

_it should be_

**_https://_\_\_\_\__[5bac76fd46024.streamlock.net](http://5bac76fd46024.streamlock.net)_****_/CHAN-375/CHAN-375\_1.stream/playlist.m3u8_**

_When accessing a SSL connection the CN name, so in the certificate MUST match the URL being accessed, otherwise the certificate is not valid for the connection._

_Please try the following_

**_[https://5bac76fd46024.streamlock.net/serverinfo](https://5bac76fd46024.streamlock.net/serverinfo)_**

**_and_**

**_[https://66.77.62.29/serverinfo](https://66.77.62.29/serverinfo)_**

_The first should show the server version, the second should give you the SSL error you have been experiencing before._

_I assume you also behind a NAT firewall as the IP address configured on the server is_ _192.168.116.29 and your public URLs are 66.77.62.29._

_Andrew._
