Following this guide I setup Discourse alongside multiple existing sites on my server. All the previous sites (as well as Discourse) are able to run, and seem to work fine, but images are broken in Discourse. The images are uploaded to $hostname/uploads, but the correct URL would be $hostname:8888…

OK, what you need then is not the subdomain install you’re kinda-sorta putting together now, but a subfolder install . Then, it’d probably be best just to throw out haproxy altogether and configure Apache to proxy <Location /forum> to localhost:8888 (or wherever you’ve got Discourse mapped to).

[afbeelding] User avatars are not displaying Self-hosting Discourse doesn’t support running on a non standard port, so choose 80 or 443. (ps: choose 443 with free ssl)

OK, so if that howto is not proper practice, do you know how to run Discourse alongside existing Apache sites?

I don’t think that how-to is by Discourse staff. You could ask in that topic and maybe that would trigger response by the how-to author.

From my read of that guide, it uses HAProxy in front of Apache, so Discourse listen on port 80 in the end.

Then I am obviously doing something wrong…simply loading the hostname puts me at my sites index.html, I have no way of getting to Discourse without a specific port. I must be missing something here…

That’s my read too. Discourse is exposed on some other port on the Host, but the proxy needs to map x.example.com to the Discourse instance. @jomaxro , can you add another domain (like community.example.com ) to your config and tell the proxy to proxy requests for community.example.com to localhost:8…

The concept makes sense, but in practice I am lost. Which config am I adding to, apache or haproxy? Also, I don’t have control of the domain, I have xyz.abc.123.edu , and that’s it.

It’s in the HAProxy, I believe. These lines are the magic: acl host_discourse hdr(host) -i my_discourse_site.com # figure out which one to use use_backend discourse_docker if host_discourse If you have lots of sites, you’ll need to add more acl lines and more use xx if hos…

Here’s my current HAProxy: timeout queue 1m timeout connect 10s timeout client 1m timeout server 1m timeout http-keep-alive 10s timeout check 10s maxconn 3000 frontend http-in …

I’d be stumped too. :slight_smile: Oh. Maybe you need to make sure that Apache isn’t doing something to enforce the port mapping? Are you sure that HAProxy and not Apache is what’s answering the door? (Maybe shutdown apache, restart HAPRoxy and then start apache?)

Non-standard port breaks uploads

Ondersteuning Installatie

elijah (Eli the Bearded) 22 augustus 2016 om 19:31 2

Topic		Antwoorden	Weergaven
Set up Discourse on a server with existing Apache sites Sysadmins how-to	16	22753	18 september 2020
Sorry for another Haproxy/Apache port 80 post but Self-hosting	4	1564	22 maart 2018
Deploying discourse on server already running another rails app Self-hosting	8	3845	17 februari 2016
Can't make Discourse accessible through Apache Self-hosting	7	3223	26 maart 2015
I see Discourse by port number but i couldn't see it to subdomain. (:3001) Self-hosting unsupported-install	7	651	6 januari 2021

Non-standard port breaks uploads

Gerelateerde topics