# 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:** [5 Julho , 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:** 1

<div class="post-metadata">

**Author:** ![kkershaw](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kkershaw/32/115025_2.png) [@kkershaw](https://meta.discourse.org/u/kkershaw)\
**Post date:** [5 Julho , 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/1 "2015-07-05T12:51:00Z")

</div>

For some reason it appears my discourse/docker instance crashed and trying to start the app with `launcher start app` results in:

```
starting up existing container
+ /usr/bin/docker start app
app

```

but then visiting the site I have a completely blank screen

Then trying a `launcher rebuild app` results in the following error message:

```
Ensuring discourse docker is up to date
Fetching origin
Discourse Docker is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 10 app
app
(<unknown>): found character that cannot start any token while scanning for the next token at line 86 column 1 -e LANG=en_US.UTF-8
YAML syntax error. Please check your /var/discourse/containers/*.yml config files.

```

I’ve looked at my `app.yaml` and I’m not sure what is wrong?

The lines at that part of the config are:

```
env:
  LANG: en_US.UTF-8
  ## TODO: How many concurrent web requests are supported?
  ## With 2GB we recommend 3-4 workers, with 1GB only 2
  UNICORN_WORKERS: 2
  ##

```

Any troubleshooting ideas greatly appreciated as our site is completely offline now ☹

**edit**  
I’ve also run full apt-get updates/dist-upgrade etc and updated all packages to latest. Actually the service did finally manage to start, but I’m still unable to rebuild the app due to the above error.

---

_[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)._