9 months ago
I asked about exposing multiple TCP ports over here and was informed that's not currently supported.
My use case is running ejabberd, which requires multiple ports for XMPP traffic.
To be clear, this is different from the "Expose Multiple Ports" feature request, which unfortunately appears to have been coopted for the custom domains feature.
I am curious though what happened to this work that angelo mentioned in the same thread:
Those who have been waiting for multiple years fear not- we have begun the work in revamping our proxies that will allow you to listen on multiple ports. (Esp. those who like to host a websocket server or write Elixir.)
No timeline, but we are hands on keyboard.
0 Threads mention this feature
2 Replies
9 months ago
Hello,
I cannot speak to the feature request you have proposed, but I can answer your question - Angelo may not have mentioned either HTTPS or TCP in his message, but he was referring to HTTPS, Cooper's root message was also written with HTTPS in mind, and that has indeed been delivered - https://docs.railway.com/guides/public-networking#target-ports - I know this doesn't help with your feature request, I'm just answering your question directly.
6 months ago
Another service I can't run here to add to the tally: https://tangled.sh. 22 and 80.