# Failed to parse SessionDescription. a=fingerprint:sha-256

**URL:** <https://community.wowza.com/t/failed-to-parse-sessiondescription-a-fingerprint-sha-256/50867>\
**Category:** Wowza Streaming Engine\
**Tags:** webrtc\
**Created:** [March 6, 2018, 11:39am UTC](https://community.wowza.com/t/failed-to-parse-sessiondescription-a-fingerprint-sha-256/50867 "2018-03-06T11:39:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakob\_Tidestrom](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@Jakob\_Tidestrom](https://community.wowza.com/u/Jakob_Tidestrom)\
**Post date:** [March 6, 2018, 11:39am UTC](https://community.wowza.com/t/failed-to-parse-sessiondescription-a-fingerprint-sha-256/50867/1 "2018-03-06T11:39:36Z")

</div>

Hello,

I followed this [tutorial](https://www.wowza.com/docs/how-to-use-webrtc-with-wowza-streaming-engine) to attempt to set up WebRTC. However, it (play/index.html) is not able to establish a connection with the server. It seems to send an offer but when it tries to parse the response, I get the following error:

```auto
DOMException: Failed to parse SessionDescription. a=fingerprint:sha-256 Failed to create fingerprint from the digest.

```

I have a second server that was set up, by me, the same way as this one. While it is able to establish a connection properly, it has other issues that make it almost completely unusable.

However, I was able to use it to cross-reference the SDPs and found this difference:

```auto
a=fingerprint:sha-256 8F:00:DA:B8:A2:4C:7F:26:21:B2:2B:A9:F0:B8:E1:4D:9E:5F:DB:20:B7:9C:C4:C5:5E:A1:C2:E0:AA:93:FE:9E\r\n (Works)

```

```auto
a=fingerprint:sha-256 \r\n (Doesn't work)

```

[this thread](http://community.wowza.com/community/questions/41791/webrtc-websockets-issue.html) appears to have had the same issue but a self-signed certificate doesn’t seem to work (the same way, at least). I just get a “can’t find server IP” (DNS\_PROBE\_FINISHED\_BAD\_CONFIG) error using that.

---

<div class="post-metadata">

**Author:** ![Jakob\_Tidestrom](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@Jakob\_Tidestrom](https://community.wowza.com/u/Jakob_Tidestrom)\
**Post date:** [March 14, 2018, 11:29am UTC](https://community.wowza.com/t/failed-to-parse-sessiondescription-a-fingerprint-sha-256/50867/2 "2018-03-14T11:29:57Z")

</div>

With the help of support I was able to solve this particular problem so I wanted to answer here, in case someone has similar problems and stumbles upon this in the future.

In VHost.xml I had accidentally placed the “webrtcKeyStorePath” and “webrtcKeyStorePassword” properties in the under / instead of 3 rows below that. I also removed the 3 out of the 4 properties under / in Application.xml, leaving only the “rtpForceH264Constraint” property.