I am installing this on the production server, which I already have a website running on port 80. How do I specify a different port to install Discourse? Currently it won’t let me install and says: # ./discourse-setup Port 80 appears to already be in use. If you are trying to run Discourse simultaneously with another web server like Apache or nginx, you will need to bind to a different port See https://meta.discourse.org/t/17247 However the above link says “assumes you already have Discourse working”, but I don’t.

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.

Yes, that does appear to be something of a chicken-and-egg problem… what the discourse-setup script does, more-or-less, is just copy samples/standalone.yml to containers/app.yml and edit a bunch of stuff in response to your answers to a bunch of questions. You can do the same thing yourself – copy the file, edit to suit. It’s how all installs used to be done before @codinghorror decided he wanted to show he could write bash scripts with the best of 'em. :grinning:

what is it that actually isn’t working when using different ports? did it some months ago for a little test install and can’t see any issues .. now would have to do a more serious installation and am not sure if i should bother doing the nginx-proxy-thing or just change the ports as i did with the other.. tia, markus.

[image] markusk: what is it that actually isn’t working when using different ports? did it some months ago for a little test install and can’t see any issues … It breaks some parts, and since isn’t a priority for us (you can just use a reverse-proxy + subdomain or subfolder) we won’t be spending time to add support for this.

well, what are these parts? i still couldn’t uncover any.. and for me at least - on a plesk managed server where it’s a bit harder to see what’s actually happening behind the scenes - this reverse-proxying so far seems over my head.. and from what i found so far most plesk related howtos and threads essentially end up using different ports as well.. :roll_eyes:

[image] markusk: well, what are these parts? i still couldn’t uncover any… That’s mostly unknown, but when you use a port and find out that it didn’t work, you’ll know. And then you can’t get help here, because it’s not supposed to work. Your best bet is to install on a separate server.

Is this still the case in 2020, that Discourse cannot or should not be installed on a port different than 80/443? Or was this problem eventually resolved? Installing nginx seems like like a pretty big deal to deal with such a simple issue! Most software you can simply specify the port to which it needs to bind. And I do see the http/https ports in app.yml.

[image] Stéphane: Is this still the case in 2020 Yes non default port is still an unsupported production configuration.

[image] Stéphane: Or was this problem eventually resolved? It’s a bit of a stretch to refer to this as a problem, there’s very few reasons to run anything on nonstandard ports these days. It’s easy to proxy with nginx/traefik now and free SSL certificates are ubiquitous. Could you maybe elaborate as to why it’s a problem?

Because the K-12 school server where I’m trying to install it limits what software I can install, and to which ports I can bind. And that server already runs apache on 80, 443, and 8080 for other services the school runs. I cannot imagine why in this day and age a linux server software wouldn’t support having a port definition in a configuration file so people can change the port. This is what all the software I can think about does, from way back in the telnet and ftp days up to modern day ssh, apache, etc.

How to specify a different port (not 80) during installation?

Product Support Self-hosting

Falco (Falco) June 8, 2018, 3:51pm 6

It breaks some parts, and since isn’t a priority for us (you can just use a reverse-proxy + subdomain or subfolder) we won’t be spending time to add support for this.

Topic		Replies	Views
I see Discourse by port number but i couldn't see it to subdomain. (:3001) Self-hosting unsupported-install	7	730	January 6, 2021
Port already in use, what to do? Self-hosting	26	20042	March 6, 2020
Port busy and app.yml not found Self-hosting	1	810	November 20, 2020
Install on vps problem? Self-hosting	2	1369	April 19, 2018
Can't get Discourse to work on different ports Self-hosting	2	1685	March 9, 2021

How to specify a different port (not 80) during installation?

Related topics