Restrict TCP proxy to specific IP addresses
danguetta
PROOP

a month ago

Hi there! I'm currently evaluating whether I can move all my services from render to railway.

One absolutely key feature render provides is the ability to expose databases to the public internet only from certain IP addresses - this extra layer of safety is crucial for me, to ensure I can still access the database locally without exposing it to the world with only a flimsy password as protection.

I realize that one way to achieve this on render is to expose the private network via a tailscale node. I tried this, and it wasn't fit for purpose. The connection was extremely slow (around 10 seconds to connect), it timed out consistently during a pg_restore, and didn't work in the dbeaver GUI for some reason. The TCP proxy works great, but is open to the world.

Does railway have any plan to offer such a service in the future? I really hope so, because I love everything else I've seen about railway so far!

Thanks!

$20 Bounty

2 Replies

Railway
BOT

a month ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway about 1 month ago


morilor1
FREE

a month ago

این تاپیک برای مشارکت عمومی علامت‌گذاری شده است، زیرا حاوی هیچ اطلاعات حساس یا شخصی نیست. هرگونه فعالیت بیشتر در این تاپیک برای همه قابل مشاهده خواهد بود


darseen
HOBBYTop 5% Contributor

a month ago

Inbound IP rules are not available on railway currently. But you can deploy an Nginx service infront of your db, expose it via TCP, and manage the allow-list manually in the Nginx config as a workaround.


Loading...