# Launcher always exits with "ERROR: Config name must not contain upper case characters, spaces or special characters."

**URL:** <https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642>\
**Category:** Self-hosting\
**Created:** [September 2, 2016, 6:50pm UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642 "2016-09-02T18:50:48Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![elijah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elijah/32/104055_2.png) [@elijah](https://meta.discourse.org/u/elijah)\
**Post date:** [May 10, 2017, 11:30pm UTC](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642/8 "2017-05-10T23:30:36Z")

</div>

Did you also `export LANG=en_US.utf8` before running it? The current shell could have it’s own independent idea of locale.

As a separate matter, the test could be rewritten to be less locale sensitive:

```plaintext
#!/bin/bash
re='[^abcdefghijklmnopqrstuvwxyz0123456789_.-]'
if [[$1 =~ $re]];
  then
      echo "ERROR: Config name must not contain upper case characters, spaces or special characters. Correct config name and rerun $0."
fi

```

But maybe people wanted `[configname]` to work…

---

_[View the full topic](https://meta.discourse.org/t/launcher-always-exits-with-error-config-name-must-not-contain-upper-case-characters-spaces-or-special-characters/49642)._