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…

This has a whole bunch of implications beyond what you’ve just written that I’ll have to investigate–we could have started there. :wink: Immediate questions: In app.yml change default listening port to 8080? What about SSL 443? Leave 443? Remove the redirect on 80 from Nginx server block? Does #3 …

[이미지] markcichy: In app.yml change default listening port to 8080? That’s your preference, I wrote it as an example. You can also choose to expose 80. [이미지] markcichy: What about SSL 443? Leave 443? There is no benefit or sense in enabling ssl on a local network [이미지] markcichy: R…

Okay. Thanks for comments. Here is my Nginx server block, FYI: server { # ssl listen 443 ssl http2; listen [::]:443 ssl http2; server_name discourse.mobiusnode.io; location / { #http trafic proxy_pass http://192.168.86.108; proxy_set_header X-Real-IP …

The behaviour I am experience is under those conditions above. Beginning of app.yml looks like this: ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CARE…

You are connecting to port 80 on the second nginx, so it thinks you’re connecting to http and not https. Try to find the X-Forwarded-Proto in the inner nginx and change proxy_set_header X-Forwarded-Proto $thescheme; to proxy_set_header X-Forwarded-Proto https; or forward your traffic to https pro…

[이미지] markcichy: - "80:80" # http - "443:443" # https This part needs to be changed

What does the log/production.log (in the running docker) say when you try to log in with failure (hence with force_https=true) ?

@RGJ – I like your solution! Do I force-https with the last suggestion? RE proxy_pass https. EDIT: I get a 502 if all I do is use proxy_pass https://192.168.86.108 EDIT2: I concealed 80 on Discourse via app.yml and it was still broke–I just re-read your post, does the Discourse container possess i…

@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.

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

지원 자체 호스팅

itsbhanusharma (Bhanu Sharma) 5월 25, 2020, 3:02오후 40

이 부분은 변경해야 합니다

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

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

Related topics