22 Replies
Anonymous
4 years ago
Nice idea
Anonymous
3 years ago
Multiple ports and also internal urls to connect between services and not have those endpoints exposed.
Status changed to Under Review angelo • almost 3 years ago
Status changed to Planned angelo • over 2 years ago
2 years ago
Posting an update for those interested, this is expected to be included in our upcoming Private Networking sprint.
Anonymous
2 years ago
Is there an ETA on this?
Anonymous
2 years ago
Multiple ports and also internal urls to connect between services and not have those endpoints exposed.
Agustin Banchio: internal url's exist now as part of Railway's Private Networking.
Anonymous
2 years ago
How far away is this?
Anonymous
2 years ago
Some News?
2 years ago
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.
Status changed to In Progress angelo • almost 2 years ago
2 years ago
Still not possible, Still no ETA.
though I'm sure the team would like to hear your usecase, would you mind sharing that?
2 years ago
I'm new to Railway, and have just deployed Soketi via a Docker image. The main Soketi functionality runs on port 6001, and I've mapped that to a public domain.
However, Soketi also exposes usage/metrics information on port 9601, and this port is integral to monitoring.
As a current workaround, surely it must be possible to expose the second port via the internal networking, via a second container?
2 years ago
yes you could for sure expose the metrics via another service that's running a proxy
2 years ago
@brody Are you aware of any templates for that?
2 years ago
there isn't any for this specific use-case, theres is only this template:
https://railway.app/template/7uDSyj
it's not exactly for soketi but it will get you 90% of the way there
2 years ago
☝️ +1
We'd be super keen to get this up and running, and are happy to beta test it!
a year ago
Hello! I would also share my use case. EMQX (https://emqx.io) is an MQTT broker which exposes 5 ports: 2 TCP, 2 Websocket, 1 HTTP (UI). So far, I'm going to expose 1 TCP port and use another L7 proxy service to expose Websockets and HTTP together.
a year ago
Simple use case yet unachievable from the templates you already provide. Using MinIO, ports 9090 and 900 are required (for console and api), however, without multiple ports exposure a straightforward deployment is not feasible. Is there any workaround?
a year ago
unless I'm not understanding something, that template comes with two services, one for the console and one for the s3 API where the files are stored.
a year ago
I would like to share the following use-case:
We are using Railway to host a Weaviate DB, the things is, the new Client V4 now supports GRPC, so it needs to be able to expose 2 ports, one for HTTP and one for the aforementioned GRPC. Without being able to expose 2 ports, we are stuck using V3…
a year ago
I have the exact same problem as above - stuck with a V3 client.
a year ago
Same issue here. We are using Colyseus for a game server and we need to spawn multiple child processes each exposed to the internet for the game to scale:
https://docs.colyseus.io/scalability/#step-3-spawning-multiple-colyseus-processes
a year ago
Upvote the ability to expose multiple ports! TCP + HTTP also. Using complex apps or DinD even expands this need imo.
a year ago
Same issue, I want to host a development server with vscode-server installed, and also running a project on it. I need to connect different domains for two different ports.
a year ago
This feature is now available under the V2 runtime.
When configuring a domain, Railway provides a list of ports that we have detected being exposed by your deployment, and you are able to choose which port you want a domain to point to.
Status changed to Completed phin • about 1 year ago