Allow connecting to non-HTTP services from outside Render | Feature Requests

112

Allow connecting to non-HTTP services from outside Render

planned

Jason Barbee

I can connect to any non-HTTP port from within my private network, but I'd like to expose non-HTTP ports outside Render as well.

This is useful for connecting to debugger ports, and to host public apps that don't use HTTP (e.g. Git, VPN, DNS and email).

September 3, 2019

Steve Frost

Need this to connect to MongoDB remotely and also to be able to run Payload CMS on Render.

Martin Seigneuret

We all need this feature asap, what is the point to disallow it 😭😭

Swift Admin

+1 we need this to be able to connect to pgbouncer from an external app

Marcelino Borges

Common Render!
We need this!
I'm trying to send a message to my RabbitMQ web service from another API and I just can't do it!
What the goal of making it easy to use rabbitmq and not allowing external requests to 'amqp://...' ?

Kevin Haggerty

Important! Trying to deploy a cube.js application stack and it's got an SQL api that it exposes over the default postgres port of 5432. Can't connect and now I know why!

John Slemmer

I think this is also important for doing any sort of IOT applications. Ideally you would have an open port to an MQTT server (or something). Anyway, this would be an awesome feature.

Sumit Kumar

Important for Redis too

Aman Gupta

I would like to host a DNS service similar to xip.io using CoreDNS (TCP/UDP 53)

Sylvain Kerkour

+1 for SSH (self hosted git) and inbound SMTP

Michael Schade

+1, this is important for us for setting up Tailscale or a similar VPN solution for data security. Would love to see some form of support (whether the generic underlying change or first-class VPN)

→