# Found character that cannot start any token while scanning for the next token at line 86 column 1 -e LANG=en\_US.UTF-8

**URL:** <https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795>\
**Category:** Self-hosting\
**Created:** [7월 5, 2015, 12:51오후 UTC](https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795 "2015-07-05T12:51:00Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [7월 7, 2015, 4:51오후 UTC](https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795/6 "2015-07-07T16:51:37Z")

</div>

Oh yeah, that means you screwed up your YML file. Use an online YAML validator like [http://yamllint.com](http://yamllint.com) .

---

_[View the full topic](https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795)._