Hello! I’ve setup Discourse servers in a about 5 instances now and all seem to be exhibiting odd behaviour; not sure if it is indeed a Bug or if anyone else has experience same. Steps to Recreate Server setup goes smooth Wizard walk through is fine, all images are uploaded and shown as expected U…

@itsbhanusharma do I comment out 80:80 #http and use @RGJ ’s advise to proxy_pass https?

Why aren’t you following the supported process for multisite here? You’re effectively reinventing a very fragile wheel.

So many links have been provided now, @Stephen -- that I am at a loss to make sense of it all. I thought I was following supported processes. Are the comments above not supported? :pensive:

Yes because you weren’t using force_https, hence the unsupported-install tag above. If you deviate from a supportable track then you won’t receive much assistance. Start here: [이미지] Multisite configuration with Docker Self-Hosting warning While multisite is s…

So, does the standard container only run http? How is what I am trying to do multi-site? I’m not attempting to host multiple domains? I have a single domain. Can you please clarify how that addresses my issue?

What did you mean by: I’ve setup Discourse servers in a about 5 instances now and all seem to be exhibiting odd behaviour; not sure if it is indeed a Bug or if anyone else has experience same.

Independent infrastructures, not in anyway connected to one another. But all with very similar settings as per above.

So why is nginx proxying the host at all? What else is happening on the machines?

We have several VM’s that are not exposed externally, the traffic is routed through the proxy (is exposed externally), to the Discourse VM internally. Similar situation in each of the separate installs. Does that clarify?

Not really, but one way or another this is technical pain you’re just going to have to live with. It’s impossible to comment on whether there’s a better approach when the use case and topology is so ambiguous.

아바타, 사이트 로고 및 인증서 오류

지원 자체 호스팅

itsbhanusharma (Bhanu Sharma) 5월 25, 2020, 6:38오후 55

정확히 말씀드리자면, 제가 제안한 내용은 아닙니다.

저는 로컬 IP에서 포트 80을 노출하고 리버스 프록시에서 SSL을 종료해 달라고만 요청했습니다.

글		댓글	조회수
Mixed SSL since upgrade Self-hosting	13	888	12월 30, 2022
Using a certificate when Discourse is installed behind a reverse proxy Self-hosting unsupported-install	24	5257	5월 17, 2019
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	139628	6월 30, 2026
Fresh install returning 502 Bad Gateway Self-hosting unsupported-install	27	1140	3월 12, 2024
Discourse behind reverse proxy and https Self-hosting	18	7665	3월 13, 2022

아바타, 사이트 로고 및 인증서 오류

Related topics