Won't Run on Different Port

Product Support Self-hosting

AI-generated summary

Won’t Run on Different Port

User Jackz encountered an issue with running Discourse on a different port (8080) alongside an existing Apache server on port 80 and 443. Despite modifying the app.yml file and attempting different configurations, Jackz was unable to access Discourse and received a “connection refused” error.

Codinghorror suggested that running Discourse on a different port is not supported and recommended using a proxy instead. Jackz confirmed the issue but mentioned success with running Discourse on a VM.

Pfaffman provided the solution: exposing 8080:80 and setting up an Apache reverse proxy to direct forum traffic to port 8080. Jackz successfully implemented this solution, resolving the issue.

1

Hello. I’m trying to install discourse on my server.
I have an apache server currently running on port 80 and 443 at /var/www
I want to install discourse to run at port 8080 for HTTP (I don’t care for https at the moment)

I have set the app.yml file to be:
8080:81 and I’ve tried 8080:8080.

I have the hostname set to 0.0.0.0, and I’m tried to access it from the computer’s LAN ip, and from itself. It just says connection refused. Server is currently running. It seems like its running but not displaying anything or such?

I’m stumped at this point so I’m looking for some help.

2

I don’t think we support running on a different port, you will need to proxy requests instead. There are howto topics on it here.

3

I thought there was a way to run on different ports. I’ve been reading multiple howto topics, but none of say instructions how to directly do it with apache. I did throe get discourse running on a VM so it seems it is working.

4

I think what you want to do is to expose 8080:80 and then have Apache reverse-proxy forum.yourdomain.com to port 8080.

5

Thank you! I didn’t understand how to set it up. I got it working now.