Discourse on different port - links will not honour this

We run discourse on a different / “hidden” port (not 80 / not 443), and while everything is fine, notification mails will not include this port in the links they contain.

I cannot find any place where I could configure a different “end user port”, only the site name can be set.

Help appreciated!

Kind regards, Tom

Public ports other than default are not supported. Behind the scenes you can proxy as needed.

1 Like