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?

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.

[image] Beluk: 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 Discourse requires ports 80 and 443. Non standard ports are not supported.

Hyperlink with port number not working

Product Support

rishabh February 27, 2019, 8:16am 2

You should try doing this:

rails console
SiteSetting.port = 3000
exit

Topic		Replies	Views
Can not visit forum.abc.com again after port change to container/app/yml Self-hosting	3	1218	May 14, 2020
Running on different port than 443: Disable redirect to nonport URL Self-hosting unsupported-install	7	1193	July 18, 2023
Access Discourse on Port Forwarded by Router Self-hosting hosting	8	1519	September 19, 2018
Generate https links in port 80 Self-hosting	20	1471	June 5, 2020
Discourse on different port - links will not honour this Self-hosting	1	786	April 29, 2016

Hyperlink with port number not working

Related topics