Hi. I have an app that uses separate port to listen for websocket messages. Is it possible with Galaxy to allow connections on specific port?
Bump on this! Has anyone followed up?
The answer is in the Galaxy Guide about the container environment:
Galaxy runs your app containers in a firewalled network environment. Only one port is exposed for external connections. Galaxy tells your app what port to listen on via the
$PORTenvironment variable, which contains a number such as 3000.
Galaxy forwards HTTP connections (port 80) on your app’s configured domains to the port exposed for external connections. HTTPS connections (port 443) are also forwarded to this port if you’ve configured encryption. You cannot serve connections on any other ports.
If you need different behavior, you may want to e-mail Galaxy Support to see if they have any suggestions!