a year ago
I want to run ejabberd, but per this post, it looks like I'll not be able to? It needs 5222, 5280, etc. but the service's network settings allow me to proxy exactly one custom domain to HTTP and exactly one TCP port.
Overall, I've hit more snags with Railway than I'd hoped for. My experience so far is that hosting anything but the simplest of services requires some extra creativity or just isn't suitable for this platform. That said, setting up an app with an API with a database...worked really well, minimal surprises.
For the kinds of workloads I want to run, I need more feature parity with e.g. Docker Compose, AWS ECS, and the like. Aside from the ports issue, I also needed multiple volumes, GitLab, and more infrastructure as code.
2 Replies
a year ago
Heya, unfortunately we don't support exposing multiple TCP ports at this time.
You can expose multiple ports as different domains on HTTP.
Feel free to open a feedback threads requesting this feature 
Status changed to Awaiting User Response Railway • 12 months ago
a year ago
Thanks! Unfortunately, proxying HTTP is not sufficient.
I logged a request over here.
Status changed to Awaiting Railway Response Railway • 12 months ago
Status changed to Solved mossymaker • 12 months ago