In my app.yml, make these changes: Only expose port 80: expose: - "80" # fwd host port 80 to container port 80 (http) In the env: section, add the latter 3 new lines: DISCOURSE_HOSTNAME: 'a.com' VIRTUAL_HOST: 'a.com' LETSENCRYPT_HOST: 'a.com' LETSENCRYPT_EMAIL: a@a.com' Then run .…

It looks like you messed up the very sensitive yml file (i.e. used tabs instead of spaces to indent) Try testing it with a linter YAMLlint - The YAML Validator Validate, Verify and Reformat your YAML documents, optimized for Ruby on Rails

In that case it might be something to do with your multisite setup. I just noticed this: Then run ./launer rebuild app that is a “ch” typo, correct? I guess the next question is what guide(s) did you follow?

:grinning: i can visit it use http://ip:port,but when i get 502 with https://ip:port

[help]multisite with letsencrypt-nginx-proxy-companion

Product Support Self-hosting

Yule_Augustine (Yule Augustine) May 23, 2018, 2:47am 3

thanks first,and it shows: Valid YAML

Topic		Replies	Views
Multisite Dockerfile issues Self-hosting	4	1053	May 13, 2021
Nginx / letsencrypt / docker -- Ubuntu 16.04 Self-hosting	5	2873	January 13, 2018
Let's Encrypt and multisite (on 2 containers) Product Support	14	1257	August 20, 2018
Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy Sysadmins how-to , domains	24	5079	August 27, 2026
Discourse Multisite – Nginx (Inside Docker) Only Serving Default Site Product Support	1	129	March 19, 2025

[help]multisite with letsencrypt-nginx-proxy-companion

Related topics