The user dlukefinch encountered a YAML syntax error related to control characters at line 1 column 1 while setting up a Discourse instance. After trying to resolve it by rerunning ./discourse-setup, the issue persisted. The community suggested checking for special characters in passwords and using tools like yamllint.com to validate the YAML. The user eventually resolved the issue by carefully re-entering all configuration details. jks noted that invisible byte-order marks (BOM) from GUI editors can cause such errors, which are detectable with tools like hexdump -C.
(<unknown>): control characters are not allowed at line 1 column 1 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
My password does not have any special characters. I just accidentally included some-don’t ask!
Ok, so in that guide you’re told to use: ./discourse-setup which autogenerates the yml file for you. The quickest solution is to re-run it and provide all the correct details.
The YML syntax is sometimes a sticking problem for the unfamiliar, the setup tool will bypass your needing to decipher it.
Ok, it is sorted now. Started afresh this morning and entered everything REALLY carefully. Process running and expected now. Must have entered something really minute.
I see you solved this already, but in my experience weird control characters at the beginning of a file usually result from editing in some GUI editor that likes to add the byte-order mark to text files. They could be invisible, but when you run some tool like hexdump -C on them, you see the extra bytes: