Acceder a Discourse en puerto reenviado por el router

Tengo Discourse ejecutándose en un servidor Ubuntu dentro de mi red.
Para poder acceder a la instalación desde fuera de mi red, necesito reenviar puertos en mi router.
¿Alguien ha logrado esto con éxito y puede ayudar con dónde configurar esto correctamente en la configuración?

Básicamente, desde fuera de mi red necesito acceder a miinstalacion.com:9050, lo cual debe reenviarse al puerto 80.

Cualquier ayuda o orientación será muy apreciada.

Check https://ngrok.com/

Thanks for that

I already have a static “hostname” which I use.
On my router I have set a port eg. “9050” to point to port 80 on my webserver
But im looking for a setting somewhere in the backend of Discourse where i can add the port :9050 at the end of the domain name for site wide access

Whenever discourse sends and email the link is mydomain.com and not mydomain.com:9050 which means i cannot access it from outside of my network.

You can map discourse to any port in your yml file

There should be lines

80:80 
443:443

Change those to:

9050:80
#443:443

And is there a way in the BackEnd to specify the URL must always end with :9050

That is exactly what it would do.
Or if You want more control, You can run discourse behind a reverse proxy and set up nginx so that it serves discourse on 9050

Thank you
Waiting for everything to rebuild after editing so i can test

Right. Discourse will not work on a non standard port.

You need to have whatever is doing the reverse proxy to send requests for discourse.example.com to the internal server.

Thank you to all for the advise etc…
I have decided it seems to be the smarter option to use the DEV Version which allows you to use Port 3000 out the “Box” and I think this is a better option for me for now

Thanks Again to all…