When i define the hyperlink http://forum:3000/releases and click on it it will forward to http://forum/releases. How can i change that the port number 3000 is not filtered?
AI-generated summary
The discussion revolves around a hyperlink issue where http://forum:3000/releases is being rewritten to http://forum/releases, stripping the port number. Beluk explains the setup: the forum runs on a standard port, while a separate web server on port 3000 hosts binaries. rishabh suggests setting the port via SiteSetting.port = 3000, but Beluk clarifies this is not feasible as the port should not be changed. pfaffman proposes using a reverse proxy or a CNAME for releases, but Beluk notes he lacks network admin access. Stephen asks for more setup details, and pfaffman confirms that Discourse does not support non-standard ports, making the issue fundamental to the platform’s design.
You should try doing this:
rails console
SiteSetting.port = 3000
exit
I think i missed to mention: The forum is running well on normal port. I don’t want to change it.
I run a different webserver on same machine with port 3000 to store binaries. It is just the link which is not forwarding…
It’s not the answer you want, but I’d set up a reverse proxy and give the other server another host name. Actually, you might just add a CNAME releases. That might fix it.
Thank for sharing your solution. This would be a great workaround, unfortunately i’m not the network administrator.
Can you give us more information on how you’ve got this set up? Is there a reverse proxy in front of Discourse?
You could point any domain name that you have control ov to the server without the network administrator. Failing that, you could implore the network administrator to get their job.
Good luck with that.
Discourse requires ports 80 and 443. Non standard ports are not supported.