Using Multiple Websites with Nginx + Discourse

[Zarken]

I’ve managed to set up Nginx to use Discourse as its main site… however i’m having trouble adding addition sites with a prefix, for example addons.domain.com

I’ve followed multiple tutorials online and all of them cause the site to not be reached? (my Discourse site is still reachable) how could i fix this?

Alternatively is there a way i could host a HTML site within the Discourse files? for example domain.com/othersite? when i’ve tried to do this in the past it just links to my discourse site with a page not found error.

Thanks!

[fefrei (Felix Freiberger)]

Follow these instructions to set up an instance of Nginx on the host:

Run other websites on the same machine as Discourse

If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container. NOTE: This is for advanced admins This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working. You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will need to copy and edit samples/standalone.yml with your favorite tex…

Once this is complete, you can configure this Nginx instance to also serve any other domain you want, either directly or by proxying to another server

[Zarken]

Hey, thats what i used for making Discourse work with it..

I was unsure whether i’d do that again for another address? if i do would i just use virtually the same code and change the filename from “discourse.conf” to “blahblah.conf”?

Thanks for the response!

[fefrei (Felix Freiberger)]

What do you want to run on the second domain? If it’s Discourse, you’ll have to install a second instance (or use multisite), and have a second, similar configuration file. If it’s something different, the configuration will be different, of course

[Zarken]

Yeah its something different. Just something i’ve coded myself.

Which is where i’m having problems… i’ve tried multiple guides to try and add a 2nd site using a prefix like “addons.” but it doesn’t work (Site cannot be reached)?

Here’s an example tutorial that i’ve used: How To Add New Site Into Your Nginx-based Ubuntu Server - ServerMom

[fefrei (Felix Freiberger)]

What domain are you trying to add?

[Zarken]

Currently have Discourse on gidentity .net (had to space the link because of post requirements for new users)

I want to use the custom stuff on either addons.gidentity.net or gidentity.net/addons/ (dont think the 2nd one is possible because of Discourse)

[pfaffman (Jay Pfaffman)]

If you followed the guide linked above, you just need to configure another site in the Nginx on the server (nothing to do with Discourse).

Google something like “configuring multiple sites in nginx”.

[fefrei (Felix Freiberger)]

What’s currently missing is DNS for addons.gidentity.net. You should set up an A record for this domain that points to 185.38.148.133

[Zarken]

That must be it! Will try that now, thanks.

[Zarken]

@fefrei

What’s currently missing is DNS for addons.gidentity.net. You should set up an A record for this domain that points to 185.38.148.133

That fixed the problem.
Little unrelated… but would i have to update my letsencrypt to allow for the prefix?

[pfaffman (Jay Pfaffman)]

You’ll need to install Let’s Encrypt in the Nginx on the computer (not the Discourse container).

[fefrei (Felix Freiberger)]

You can find some hints on how to do that as part of the following tutorial (but you’ll need to skip some unrelated parts):

Add an offline page to display when Discourse is rebuilding or starting up

This guide is intended for advanced users, who are already using nginx outside the docker container. By following this guide you make your setup more complicated and will lose some speed benefits like HTTP2 if you’re not running Ubuntu 16.04 or later. Proceed with caution! When Discourse is rebuilding or starting up, your users will usually either see an error message from their browser… [image] …or a not-so-nice 502 error message from Nginx: [image] If you’re a perfectionist …

[Zarken]

Thought I had this sorted but apparently not.
Going to the url addons.gidentity.net no longer displays an error however it automatically forwards to gidentity. net (remove space after . - posting requirements) what could be the cause of this?

EDIT - my DNS records = https://puu.sh/zVErv/93ed69a2ac.png

[fefrei (Felix Freiberger)]

Such a redirect probably means that your configuration isn’t appplying and the wrong one is used.

• Did you link your new file to show up in the sites-enabled-folder?
• Did you remember to reload Nginx after that? Did that succeed or show an error?

If these steps don’t help, can you post your configuration files here so we can have a look? (They shouldn’t contain sensitive information, but please double-check.)