4 months ago
Hi,
I have a NATS server up and running and it's configured to listen on the default port 4222.
It is also configured to accept leaf node connections on port 7422.
I can create a TCP proxy for port 7422 and my leaf nodes hosted in other Railawy projects or on-prem successfully connect. However, is there a way to also create a second TCP proxy for port 4222?
That would allow me to connect to the NATS server from my local machine for troubleshooting etc.
Thanks,
Mike
5 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 TCP Proxy for PostgreSQL not accepting connections - Connection timeout
🧵 TCP Server Not Receiving Connections Despite Proper Configuration
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
Oh... I could install the nats CLI on the NATS server and SSH into it as per docs: https://docs.railway.com/guides/cli#usage
4 months ago
Yep, that works as expected. I'll keep the ticket open as I'm curious to hear if the Railway team has plans for multiple TCP proxies per service.
4 months ago
Hello,
We don't have plans for it, but we would like to support multiple TCP proxies and even UDP at some point. But yeah, no immediate plans for it.
Best,
Brody
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
Thanks Brody. Luckily I can get by with a single port exposed thanks to the SSH approach 
Status changed to Awaiting Railway Response Railway • 4 months ago
Status changed to Solved mikenikles • 4 months ago
