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/uploads. I can’t find where in site settings of my yml file to fix this.

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 to localhost:8888 (or wherever you’ve got Discourse mapped to).

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 host_yyy lines.

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 bind *:80 default_backend main_apache_sites/html # Define hosts acl host_discourse hdr(host) -i leet.arc.rpi.edu # figure out which one to use use_backend discourse_docker if host_discourse backend main_apache_sites server server1 127.0.0.1:8080 cookie A check backend discourse_docker server server2 127.0.0.1:8888 cookie A check Note, host is not connected to internet, you must be on campus network to connect. All the other (existing) sites are behind Apache, so I don’t think I need more acl lines.

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?)

I’m not understanding the root problem. Why would "the correct URL would be $hostname:8888/uploads – all access to the site should be via HAProxy, as I understand it, so why would the correct URL have the port in it?

I think I’m causing all the confusion here as I’m the one confused. Let me try and clear things up. ##Before Discourse: 3 sites were hosted on a local server, http://leet.arc.rpi.edu. quicklogs, mediawiki, and printers were located at /quicklogs, /wiki, and /printerpicker respectively. There was also an index.html at the root of the server which included links to each of the 3 sites, as well as a few external resourses. ##Discourse Install: Installed Discourse using the 30-minute guide, then followed above linked guide to put alongside existing sites. End goal is for staff to continue using “leet” as their homepage, and linking to each tool. As such, Discourse would exist (somewhere) and would be linked by the index.html. ##Problem: Currently I can only access Discourse by adding :8888 to the url. I am unsure how to access it otherwise.

So just to make sure I am understanding completely, I should do the following: Remove HAProxy entirely. Remove Listen commands from Apache config files. Follow Neil’s guide to put Discourse in a subfolder. Use apache to proxy to Discourse.

A more generalised step 1+2 would be, “revert everything you’ve done according to the “existing apache sites” howto”. But yes, what you’ve described is what needs to be done.

…and it looks like I may have spoken too soon. Unknown if this is related to subfolder install, discourse being on a custom port and proxied, or an actual bug - but when I went to /admin/upgrade and ran an update, the progress bar never filled nor did anything appear in the console below. After waiting 10 minutes, I reloaded the upgrade page and found that it had in fact upgraded. Any thoughts?

I’d have to say that by far the most likely cause of that would be a bug in the upgrade UI not handling subfolders with grace and aplomb. Any of my fellow @team members feel like spinning up a scratch subfolder install and seeing if this sucker’s reproducible?

Non-standard port breaks uploads

Product Support Self-hosting

jomaxro (Joshua Rosenfeld) August 24, 2016, 3:34am 17

Matt, thanks for all your help (and Jay, and Rafael). I was able to successfully get my instance up and running, and have run into no further issues thus far!

Topic		Replies	Views
Set up Discourse on a server with existing Apache sites Sysadmins how-to	16	23485	September 18, 2020
Sorry for another Haproxy/Apache port 80 post but Self-hosting	4	1642	March 22, 2018
Deploying discourse on server already running another rails app Self-hosting	8	3936	February 17, 2016
Can't make Discourse accessible through Apache Self-hosting	7	3297	March 26, 2015
I see Discourse by port number but i couldn't see it to subdomain. (:3001) Self-hosting unsupported-install	7	730	January 6, 2021

Non-standard port breaks uploads

Related topics