Here’s what I did to install a successful installation of Discourse for multiple instances on a dedicated server that uses Nginx and Apache. I decided to create a new topic since my installation seems to be a little unique from what I have seen others having to go through. I am very new to Nginx we…

[image] PopsRocker: Change the first half of the ports to a port that is not being used, I used 85 Actually, ports <1024 are considered “privileged”, using them without assignment is… not technically wrong, but ugly. Also, you should bind Discourse to the local interface: expose: - "127.0.…

That makes complete sense, I made the changes suggested to my server and they work perfectly. I also changed them in the above instructions as well as used the code markdown instead of the quote markdown (thanks for pointing that out) … Pops

@elberet hmmm, something isn’t quite right when changing the ports on the production sites Changing the ports as you suggested on the app.yml file worked great, but after changing the two additional container files with the appropriate changes I get a 502 bad gateway error. I made the changes to …

You can also stop exporting ports entirely by using web.socketed.template.yml: [image] Run other websites on the same machine as Discourse Self-Hosting @pfaffman edited this heavily 2022.02.24. Blame me if it’s broken. If you want to run other websites on the…

I saw that post, but had a difficult time understanding how to implement it in the way my server is set up since Nginx is already installed and running in front of Apache. It had to do with the last step, the path you referenced for sites-enabled an sites-available doesn’t exist and if I just neede…

[image] PopsRocker: This got me through the installation with no errors, but when I went to the url I setup for the forum nothing was showing up. I could connect to the forum using the IP with the port number. Since the forum doesn’t need Apache, I found the conf file that was directing the site…

Sorry, replied too soon and then found my answer above: in app.yml: expose: - "127.0.0.1:8888:80" # fwd host port 80 to container port 8888 (http) - "2222:22" # fwd host port 22 to container port 2222 (ssh) in /etc/nginx-sp/vhosts.d/discourse.d/main.conf (renamed to main.custom.conf as sugges…

I’m still a little confused with this Serverpilot / Discourse setup. When you created your “discourse” app in Serverpilot, what did you put in the apps/discourse/public/ directory? I have my current discourse installation in the /var/discourse directory but am not sure how Serverpilot is suppose to …

You don’t actually have to put anything in the apps/discourse/public/ directory. Instead, you want requests to that Serverpilot app forwarded to your Discourse install living in /var/. This is accomplished via the /var/discourse/containers/app.yml and /etc/nginx-sp/vhosts.d/discourse.d/main.custom.…

Thanks for your help! I was able to get it up and running.

Success - New Multisite Install on Dedicated server using ServerPilot, Nginx and Apache

Support Self-hosting

riking (Kane York) April 30, 2015, 3:04am 5

You can also stop exporting ports entirely by using web.socketed.template.yml:

Topic		Replies	Views
More than one site as different container running on the same do server Self-hosting	3	866	December 24, 2019
One server for 2 Discourse communities? Self-hosting hosting	56	1542	August 27, 2026
Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy Sysadmins how-to , domains	24	4867	August 27, 2026
Multiple app containers for a single Discourse site Self-hosting hosting	5	217	January 19, 2026
Help me setup many websites on one VPS Self-hosting	3	976	May 25, 2020

Success - New Multisite Install on Dedicated server using ServerPilot, Nginx and Apache

Related topics