How do I even install Discourse?

[Vixi]

I’ve been running nextcloud, vaultwarden, jellyfin etc in docker containers for years, but I cannot for the life of me figure out Dicourse.

The setup script gives me some error about not being able to connect on port 80 and 443. Probably because I’m setting it up on a new server which does not have those ports forwarded as I intend to use nginx proxy manager on my other server to reverse proxy to Discourse.

I’ve tried to write a compose file based on the variables in the files, but docker can’t find a manifest when I attempt to pull discourse/base.

I’ve tried the bitnami container but I end up with no admin account and the command bitnami says to use to setup one returns errors.

I have spent the past few days on this. Can someone please help?

[Lilly]

@Vixi

bitnami container

sounds like a non-standard install.

please note:

Bitnami installations are unsupported

Community support is only provided for installs that use the official instructions: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub If you have installed with Bitnami and are having trouble, then you need to either follow the instructions or get help somewhere else.

[Vixi]

Sounds like an automatic response that completely ignored the problems I am having with the standard install.

[merefield (Robert)]

It was an accurate response, your setup is not standard and therefore not a standard install. Free support is generally targeted at the standard install because it then remains manageable for people to provide it (for free).

If looking for free support for a non-standard install I suggest being a bit nicer to those who provide it …

Anyway have a look at this, might help:

Run other websites on the same machine as Discourse

@pfaffman edited this heavily 2022.02.24. Blame me if it’s broken. 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 …

[Vixi]

As stated in my original post, standard install is the first thing I tried. It returns errors.

[merefield (Robert)]

Because yours isn’t!

[Vixi]

The guide you linked outright says it assumes I have Discourse working. Which I don’t. I’m also not trying to run other websites on the same machine as Discourse, I am trying to run Discourse on a second machine.

[merefield (Robert)]

Yes, but it handles the case where you have NGINX in front of the container … so in a way is a similar situation.

But I am but a lowly app-dev with some sys admin hobby experience. A sys admin guru is what you really need.

If someone doesn’t automatically chime in, consider posting in Marketplace if you have budget.

[Lilly]

What's the proper way to set up Discourse behind a reverse proxy?

if you expose a port/ip, all traffic for that port will be handled. The only issue you need to resolve is IP forwarding. So you need to customize NGINX to allow for the forwarded IP addresses so it does not look like all traffic is coming from 1 IP, there is a post here on meta covering that.

[Vixi]

The problem is I can’t get the discourse-setup script past the port check and none of the launcher commands actually do anything. I had already edited the files mentioned in the guide merefield linked before I even posted here as the error message in discourse-setup reccomended, but I don’t know what to do from there.

[Lilly]

you mentioned bitnami - unfortunately if you are using bitnami it will be difficult to solve without their help.

[Vixi]

I’m asking for help with the official discourse docker.

I cannot get the official discourse docker to run at all
I can get the bitnami one to run and access the site but I haven’t been able to setup an admin account with theirs.

[Lilly]

where in this setup are you having problems exactly?

docs/INSTALL-cloud.md

please post any error messages, backtraces (use code blocks), and any system details that may help.

Are you able to clone the official discourse docker image?

[Vixi]

sudo ./launcher rebuild app got it going. However, after filling in the details to sign up an admin account and go to the next page, I just get this. I haven’t received any confirmation email with either the smtp port set to 587 or 465

[NateDhaliwal]

You should change example.com with your actual domain name. That domain is an example domain on the web, not actually your forum’s own domain.

Have you setup your domain name and DNS yet?

[Vixi]

yeah, changing example.com back to the server ip shows me the correct confirmation email page.

I found a DNS record typo and a mistake I made in the yml file, so email should hopefully work when I wake up.

The output of the sudo ./launcher rebuild app command also gives me some clues on what to tinker with to further customize the setup. Hopefully I’ll have a Discourse setup I’m happy with by the weekend!

[Andrew_Rowe]

@Vixi

The problem is I can’t get the discourse-setup script past the port check

Sorry for butting in and not reading the whole thread but OP’s problem I had myself the first time I tried to setup Discourse. Port 80 and port 443 are not open because the app isn’t using them yet. The trick is to run skip-network-check or some such command (can’t remember and at work) and setup skips the port check and then goes forward with the setup. It is in the standard setup instructions but it is easy to miss

Sorry if someone else already got this

Thanks to Jay below command is

--skip-connection-test

[pfaffman (Jay Pfaffman)]

@Vixi

The setup script gives me some error about not being able to connect on port 80 and 443. Probably because I’m setting it up on a new server which does not have those ports forwarded as I intend to use nginx proxy manager on my other server to reverse proxy to Discourse.

Then you can’t use discourse-setup or you can run it with --skip-connection-test, but you’re on your own to make it work. You also need to comment out the ssl and https templates.

@Vixi

I’ve tried to write a compose file based on the variables in the files, but docker can’t find a manifest when I attempt to pull discourse/base.

That won’t work.

You should first install it on a machine that doesn’t have anything else using ports 80 and 443 to see how it works. If you’re not going to do that then you need to understand how it works before you do anything.

[Vixi]

I fixed the issue with my email server can and other docker apps can use the email address I want to use with discourse, but discourse is still failing to send an email.

[NateDhaliwal]

Perhaps check your email provider? It may be in the list of bounced emails.