Hey guys,
Maybe this one was answered and dealt with but I can’t find it here. Therefore, posted mine one, hoping someone could elaborate what is going on:
(unknown): did not find expected key while parsing a block mapping at line 40 column 3 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
Thanks,
is this a fresh install or you’re using an old yml to build a container?
it is a fresh install and done it several times but this is the first time I have this error 
Can you share your redacted app.yml?
which part of it??? from top to bottom??
Yes, the entire file and redact any sensitive information.
## this is the all-in-one, standalone Discourse Docker container template
2 ##
3 ## After making changes to this file, you MUST rebuild
4 ## /var/discourse/launcher rebuild app
5 ##
6 ## BE *VERY* CAREFUL WHEN EDITING!
7 ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNM>
8 ## visit http://www.yamllint.com/ to validate this file as needed
9
10 templates:
11 - "templates/postgres.template.yml"
12 - "templates/redis.template.yml"
13 - "templates/web.template.yml"
14 - "templates/web.ratelimited.template.yml"
15 ## Uncomment these two lines if you wish to add Lets Encrypt (https)
16 #- "templates/web.ssl.template.yml"
17 #- "templates/web.letsencrypt.ssl.template.yml"
18
19 ## which TCP/IP ports should this container expose?
20 ## If you want Discourse to share a port with another webserver like Apache>
21 ## see https://meta.discourse.org/t/17247 for details
22 expose:
23 - "8080:80" # http
24 #- "443:443" # https
25
26 params:
27 db_default_text_search_config: "pg_catalog.english"
28
29 ## Set db_shared_buffers to a max of 25% of the total memory.
30 ## will be set automatically by bootstrap based on detected RAM, or you can override
31 #db_shared_buffers: "256MB"
32
33 ## can improve sorting performance, but adds memory usage per-connection
34 #db_work_mem: "40MB"
35
36 ## Which Git revision should this container use? (default: tests-passed)
37 #version: tests-passed
38
39 env:
40 LC_ALL: en_US.UTF-8
41 LANG: en_US.UTF-8
42 LANGUAGE: en_US.UTF-8
43 # DISCOURSE_DEFAULT_LOCALE: en
44
45 ## How many concurrent web requests are supported? Depends on memory and CPU cores.
46 ## will be set automatically by bootstrap based on detected CPUs, or you can override
47 #UNICORN_WORKERS: 3
48
49 ## TODO: The domain name this Discourse instance will respond to
50 ## Required. Discourse will not work with a bare IP number.
51 DISCOURSE_HOSTNAME: 'community.MYWESITE.com'
52
53 ## Uncomment if you want the container to be started with the same
54 ## hostname (-h option) as specified above (default "$hostname-$config")
55 #DOCKER_USE_HOSTNAME: true
56
57 ## TODO: List of comma delimited emails that will be made admin and developer
58 ## on initial signup example 'user1@example.com,user2@example.com'
59 DISCOURSE_DEVELOPER_EMAILS: 'MYEMAIL@gmail.com'
60
61 ## TODO: The SMTP mail server used to validate new accounts and send notifications
62 # SMTP ADDRESS, username, and password are required
63 # WARNING the char '#' in SMTP password can cause problems!
64 DISCOURSE_SMTP_ADDRESS: XXXXXXXXXXXXX.COM
65 #DISCOURSE_SMTP_PORT: 587
66 DISCOURSE_SMTP_USER_NAME: SMTP_Injection
67 DISCOURSE_SMTP_PASSWORD: XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
68 #DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true)
69 #DISCOURSE_SMTP_DOMAIN: discourse.example.com # (required by some providers)
70 DISCOURSE_NOTIFICATION_EMAIL: MYEMAIL@gmail.com # (address to send notifications from)
71
72 ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
73 #LETSENCRYPT_ACCOUNT_EMAIL: me@example.com
74
75 ## The http or https CDN address for this Discourse instance (configured to pull)
76 ## see https://meta.discourse.org/t/14857 for details
77 #DISCOURSE_CDN_URL: https://discourse-cdn.example.com
78
79 ## The maxmind geolocation IP address key for IP address lookup
80 ## see https://meta.discourse.org/t/-/137387/23 for details
81 #DISCOURSE_MAXMIND_LICENSE_KEY: 1234567890123456
82
83 ## The Docker container is stateless; all data is stored in /shared
84 volumes:
85 - volume:
86 host: /var/discourse/shared/standalone
87 guest: /shared
88 - volume:
89 host: /var/discourse/shared/standalone/log/var-log
90 guest: /var/log
91
92 ## Plugins go here
93 ## see https://meta.discourse.org/t/19157 for details
94 hooks:
95 after_code:
96 - exec:
97 cd: $home/plugins
98 cmd:
99 - git clone https://github.com/discourse/docker_manager.git
100
101 ## Any custom commands to run after building
102 run:
103 - exec: echo "Beginning of custom commands"
104 ## If you want to set the 'From' email address for your first registration, uncomment and change:
105 ## After getting the first signup email, re-comment the line. It only needs to run once.
106 #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
107 - exec: echo "End of custom commands"
Remove the space here
This fixed the error and app went all the way but with another error not launching the discourse!
I scrolled up to see what was there as it said but had nothing mentioned except port 6379 is not opened and this:
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-property-in-object since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-property-in-object", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-private-property-in-object.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
I’m not sure this is significant but I’ll fresh re-install discourse first and my other control panel to host my other pages 
I’ve promised someone here to report if things went right when installing discourse and other sites on same server and been trying hard to get it right but it isn’t happening yet 
It looks as though you’re trying to publish on a different port. Are you trying to put Discourse behind a reverse proxy?
I would revert the expose statement for now and try accessing over 80 first if so.
If you’re just trying to install discourse on something other than 80/443 for direct access please note that this won’t work and isn’t supported.
Affirmative Stephen, I was doing that but I decided to install discourse first and play with other stuff next…!
I’m almost there with the fresh installation as I type 
I should reduce caffeine intake 
K, I did the right thing and installed a fresh one to start my day with it but I can’t get anywhere;
If checked forum.mywebsite.com I get blank page nothing is displaying at all except discourse icon on the left top corner displaying.
If I use https with it I get error Secure Connection Failed instead of actual homepage
I checked all DNS, A, TXT, CNAMES …! All good to go as a matter of fact I’ve installed it and and got the admin register page but had to activate through SSH console and it went well but nothing shown after that step!!!
Anyone for helping this lost person 
Are you installing with let’s encrypt enabled?
If so how many times have you tried to install against this hostname between this installation and the last one?
Not that I know off. But domain and its sub were on cloudflare SSL and these gadgets …!
I paused it just a few minutes ago and checked the site here and there you were saying this to me 
I’m giving it one more shot to see how things are later on!
Thanks Stephen, you’re a life saver as usual 
BTW. For all times sake, I had this warning whenever installed discourse and will happen again in the future unless I know how to deal with it:
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-property-in-object since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-property-in-object", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-private-property-in-object.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
All the best 
I have the same issue
You can bypass it. If you know what it means, then you know how to deal with it if there is some needs. We all others… just another warning that needs no action.