I recently was setting up a Node.js and found that it used a non-standard port but that port was still proxied by the shared load balancer. I found this information on that feature at https://docs.jelastic.com/container-ports#ports-auto-redirect
During a node creation, the platform detects the ports which are listened on the TCP level. The commonly used for standard services (e.g. SSH, mail, databases, etc.) are automatically filtered. The first among the remaining ports becomes the container entry point so that all incoming requests are forwarded to it.
This process is performed on each container launch, so the corresponding application becomes available over the embedded Shared Load Balancer just after being deployed, without any manual intervention required.
However, in case you need to disable or adjust this functionality (e.g. if it exposes application admin panel), you can manually change the auto-redirect settings during the container creation. For that, switch to the Variables section, add the dedicated JELASTIC_EXPOSE parameter and set its value based on your needs
I see you have port 30000 exposed there so it should be working I would think:
I’m not sure you’ve got the app running yet though since I tried setting an Endpoint for 30000 and nothing was showing nor did loading the site under :30000 either so I would first make sure you’ve confirmed the app is up and running and ideally the platform should proxy it automatically.