# Starting a second Discourse forum on the same VPS
**URL:** https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160
**Category:** Self-hosting
**Created:** [July 31, 2017, 11:29am UTC](https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160 "2017-07-31T11:29:57Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@\_vincent](https://meta.discourse.org/u/_vincent)
#### Post date: [July 31, 2017, 11:29am UTC](https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160/1 "2017-07-31T11:29:57Z")
Hi,
I would like to host a second forum on an OVH VPS. Main standalone discourse instance runs on the domain root ([https://zbeul.org](https://zbeul.org)) and I want the new one to be ran on [https://mao.zbeul.org](https://mao.zbeul.org).
I figured the best solution would be 2 standalone instances with nginx proxy\_pass in front.
I thoroughly read the following threads:
- [https://meta.discourse.org/t/advanced-troubleshooting-with-docker/15927](https://meta.discourse.org/t/advanced-troubleshooting-with-docker/15927)
- [Multisite configuration with Docker - #42](https://meta.discourse.org/t/multisite-configuration-with-docker/14084/42)
- [Run other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247)
- [Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/setting-up-let-s-encrypt-with-multiple-domains/56685)
I just nuked my config files, removed the front nginx and reverted to my previous app.yml for the sake of a fresh start.
Has anyone tried this kind of installation?
If we come to a solution I’ll be happy to put up a wiki page for this specific case.
Thanks!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [July 31, 2017, 11:33am UTC](https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160/2 "2017-07-31T11:33:26Z")
Your plan should work. Or both instances on non standard ports. I recommend using caddyserver as the front door. That’ll give you https in both sites with no extra configuration.
---
### Author:  [@\_vincent](https://meta.discourse.org/u/_vincent)
#### Post date: [July 31, 2017, 11:39am UTC](https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160/3 "2017-07-31T11:39:33Z")
According to this answer (which might be outdated) it appears like running Discourse on a non-standard port is not the prettiest way:
> [@How to specify a different port (not 80) during installation?](https://meta.discourse.org/t/how-to-specify-a-different-port-not-80-during-installation/47859/3):
>
> Just bear in mind that running on a different port that 80 and 443 isn’t really supported, and there will be some things broken. If you really need to reuse the server you can set nginx in front to proxy request between discourse and he other site. There’s an #howto for that.
But anyway, why not.
Thanks a lot for your answer and for bringing up Caddy, I never heard of it. Anyone interested, DO wrote a howto:
> **[How To Host a Website with Caddy on Ubuntu 16.04 | DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-host-a-website-with-caddy-on-ubuntu-16-04)**
>
> Caddy is a web server that was created with ease of use in mind. It’s become a common choice for developers who want to quickly r…
**Edit :** in addition, it seems like Ubuntu 16.04 users have to enable systemd-networkd service first.
```
sudo systemctl enable systemd-networkd
sudo systemctl start systemd-networkd
```
In this case @pfaffman, should I disable ssl and letsencrypt in app.yml?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [July 31, 2017, 12:11pm UTC](https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160/4 "2017-07-31T12:11:11Z")
> [@\_vincent](#):
>
> should I disable ssl and letsencrypt in app.yml?
Yes.
Also, if you want to save some resources, you can use this, it’s just a bit more work than 2 standalones, but uses half the resources: [Multisite configuration with Docker](https://meta.discourse.org/t/multisite-configuration-with-docker/14084)
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [August 1, 2017, 5:29pm UTC](https://meta.discourse.org/t/starting-a-second-discourse-forum-on-the-same-vps/67160/5 "2017-08-01T17:29:59Z")
> [@\_vincent](#):
>
> According to this answer (which might be outdated) it appears like running Discourse on a non-standard port is not the prettiest way:
That’s for running on a nonstandard port for the external interface - what you type in the web browser - not for internal routing.
I’d still recommend the use of unix sockets for the [Caddy || nginx] → Discourse.nginx connection **if** you’re doing 2 containers.
If you can figure out how to do multisite, of course, that’ll get you just one container and everything is fine.