# Cant publish stream (JSON error)

**URL:** <https://community.wowza.com/t/cant-publish-stream-json-error/41827>\
**Category:** Wowza Developer Dojo\
**Tags:** wowza-streaming-server-java-api\
**Created:** [January 22, 2014, 2:46pm UTC](https://community.wowza.com/t/cant-publish-stream-json-error/41827 "2014-01-22T14:46:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonas\_Ramonas](https://avatars.discourse-cdn.com/v4/letter/j/e9bcb4/32.png) [@Jonas\_Ramonas](https://community.wowza.com/u/Jonas_Ramonas)\
**Post date:** [January 22, 2014, 2:46pm UTC](https://community.wowza.com/t/cant-publish-stream-json-error/41827/1 "2014-01-22T14:46:52Z")

</div>

Hello,

I face issue when trying to publish stream (fresh install). Getting such error:

ERROR server comment -

RTPSessionDescriptionDataProviderBasic.getSessionDescriptionData JSON

detected but there is an error in the JSON

com.fasterxml.jackson.core.JsonParseException: Unexpected character (’’

(code 92)): was expecting either valid name character (for unquoted name)

or double-quote (for quoted) to start field name

at [Source: java.io.StringReader@5075c744; line: 1, column: 3]

{\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf320{\fonttbl\f0\fswiss\fcharset0

Helvetica;}{\colortbl;\red255\green255\blue255;}\margl1440\margr1440\vieww9000\viewh8400\viewkind0\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\ql\qnatural\pardirnatural\f0\fs24

\cf0

rtsp://_ **:** _@_ **.** _.\*\*\*.100:554/cam/realmonitor?channel=1&subtype=0}

CAn someone tell me where should I look for trouble?

---

<div class="post-metadata">

**Author:** ![Roger\_Littin1](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Roger\_Littin1](https://community.wowza.com/u/Roger_Littin1)\
**Post date:** [January 23, 2014, 6:56am UTC](https://community.wowza.com/t/cant-publish-stream-json-error/41827/2 "2014-01-23T06:56:02Z")

</div>

It looks like your text editor has save the stream file as formatted text instead of plain text.

Make sure you use a text editor that saves the file in plain text (utf8) mode.

TextEdit on the Mac defaults to a rich text format. You need to manually select plain text by choosing Format / Make Plain Text from the menu and then ensuring that you save it in a UTF-8 format from the Save dialog.

Roger.

---

<div class="post-metadata">

**Author:** ![Jonas\_Ramonas](https://avatars.discourse-cdn.com/v4/letter/j/e9bcb4/32.png) [@Jonas\_Ramonas](https://community.wowza.com/u/Jonas_Ramonas)\
**Post date:** [January 22, 2014, 2:50pm UTC](https://community.wowza.com/t/cant-publish-stream-json-error/41827/3 "2014-01-22T14:50:29Z")

</div>

OS: MAC OS x

---

<div class="post-metadata">

**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\
**Post date:** [January 22, 2014, 12:18pm UTC](https://community.wowza.com/t/cant-publish-stream-json-error/41827/4 "2014-01-22T12:18:46Z")

</div>

Are you using a .stream file like this:

[How to specify per-stream settings in .stream files](https://www.wowza.com/docs/how-to-specify-per-stream-settings-in-stream-files)

If so and the file is malformed you would get a json error.

Can you show the contents of the .stream file?

Salvadore

---

<div class="post-metadata">

**Author:** ![Jonas\_Ramonas](https://avatars.discourse-cdn.com/v4/letter/j/e9bcb4/32.png) [@Jonas\_Ramonas](https://community.wowza.com/u/Jonas_Ramonas)\
**Post date:** [January 22, 2014, 7:32pm UTC](https://community.wowza.com/t/cant-publish-stream-json-error/41827/5 "2014-01-22T19:32:31Z")

</div>

> It looks like your text editor has save the stream file as formatted text instead of plain text.
> 
> Make sure you use a text editor that saves the file in plain text (utf8) mode.
> 
> TextEdit on the Mac defaults to a rich text format. You need to manually select plain text by choosing Format / Make Plain Text from the menu and then ensuring that you save it in a UTF-8 format from the Save dialog.
> 
> Roger.

That was the reason.

Thanks a lot, issue resolved