I have seen a couple of tutorials that explain how to do this but in different ways which does not help me. Is there a way to make a apache virtual host config for Discourse so that a specific domain redirects to the software just like adding other websites and respective domains? Thank you.

So I fixed the problem. Someone mentioned the favicon showing in http which is why it gave the error. I uploaded something else and deleted it, now the site is fully https :slight_smile:

Yes. Those tutorials explain how. Or, if you mean can you run discourse without docker and having apache as a reverse proxy, the answer is no. For $5/month you an avoid that pain.

Thanks for the reply. I am running it off a VPS. I have Apache installed and I am not too experienced with websites. I am looking at this, Run other websites on the same machine as Discourse But with that it seems like I have to use Nginx because of the config files, but my question is, can I do…

Yeah I was looking at that too. He covered it for CentOS and not Ubuntu, some parts are unclear to me

[이미지] koltl: I have Apache installed and I am not too experienced with websites. If you aren’t familiar with this (and don’t want to become), I really recommend ditching Apache and running only Discourse in the VPS. If you need to run more stuff, get a VPS for Apache stuff and another for Dis…

So I switched over to Nginx and everything is working. I believe SSL is setup properly but on chrome, it gives me the message “Your connection to this site is not fully secure”. Force HTTPs is on

The SSL is setup with the nginx service inside the container. If the container is exposed to the internet and you access it directly from the browser (default discourse installation), you will have SSL. But if you put a reverse proxy in front of it (be it Apache, Nginx, or some 3rd party service, l…

So to have security between browser and reverse proxy, I need to configure SSL in the nginx configuration file? Thanks

This is my config here, what else do I need to add? server { listen 80; listen [::]:80; server_name a1rp.xyz; # ← change this return 301 https://$host$request_uri; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name a1rp.xyz; # ← change this ssl on; ssl_certificate …

Make sure to: Comment out all ssl templates in the templates (in app.yml) . If you are using letsencrypt you will have two: # - "templates/web.ssl.template.yml" # - "templates/web.letsencrypt.ssl.template.yml" Add a socket template: - "templates/web.socketed.template.yml" Comment out all e…

Wanting to run Discourse alongside apache

지원 자체 호스팅

pfaffman (Jay Pfaffman) 8월 7, 2019, 2:28오전 4

Have a look at Set up Discourse on a server with existing Apache sites

글		댓글	조회수
Apache w/ SSL + Discourse: Next steps? Self-hosting	10	1900	7월 18, 2020
Discourse not loading with Apache and proxy redirect Self-hosting	7	2557	7월 15, 2020
I want to install using a reverse proxy for Apache Self-hosting	13	4741	8월 8, 2021
Install discourse together with Apache websites Self-hosting	4	1876	12월 28, 2020
Setting up Discourse on a VPS with other sites Self-hosting	12	4629	4월 23, 2017

Wanting to run Discourse alongside apache

Related topics