render-networking

Configures private networking, internal DNS, and service discovery between Render services.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-networking-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-networking
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-networking
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-networking-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Connecting services on Render's private network requires understanding internal hostnames, region and workspace scoping, port rules, and per-resource connectivity limits, and misconfigurations cause hard-to-diagnose connection failures. ## Core Features & Use Cases - Private Network Setup: Explains internal hostnames, internal URLs, and the Connect > Internal dashboard values needed for service-to-service traffic. - Service Discovery: Covers the [hostname]-discovery DNS pattern and RENDER_DISCOVERY_SERVICE for custom load balancing across scaled instances. - Troubleshooting Guidance: Diagnoses DNS failures, reserved port conflicts (10000, 18012, 18013, 19099), free-tier inbound limits, cross-region/workspace issues, and environment isolation. - Use Case: A public web gateway needs to call three private backend services; use this Skill to wire internal hostnames and ports correctly, then debug why a free-tier web service cannot receive inbound private traffic. ## Quick Start Ask how to connect a Render web service to a private Postgres database over the internal network and troubleshoot any connection errors.

Frequently Asked Questions about render-networking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect two Render services over the private network?▼

Use the internal hostname and port from the target service's Connect > Internal dashboard tab, formatted as http://[internal-hostname]:[port]/path. Both services must be in the same region and same workspace for private DNS to resolve.

How does service discovery work for scaled Render services?▼

Render exposes a [hostname]-discovery DNS name that resolves to all instance IPs of a multi-instance service. Combine it with the RENDER_DISCOVERY_SERVICE environment variable to implement custom load balancing or per-instance health checks in application code.

Can Render free-tier web services receive private network traffic?▼

No. Free-tier web services can send outbound private traffic but cannot receive inbound private connections. Upgrade the target service or route traffic through a public endpoint with authentication instead.

Why does private DNS resolution fail between my Render services?▼

Private DNS only works when both services share the same region and workspace, and the target service is running. Also verify you use the system resolver, include an explicit http:// or https:// scheme, and check environment isolation settings on Professional workspaces.

Which ports are reserved on Render services?▼

Ports 10000, 18012, 18013, and 19099 are reserved and must not be used for application listeners. Each service supports a maximum of 75 open ports, and on multi-port web services only the PORT variable's port receives public HTTP traffic.

Can background workers accept inbound connections on Render?▼

No. Background workers, cron jobs, and workflow runs have no internal hostname and cannot receive inbound private traffic. They can only initiate outbound connections, such as to a Postgres or Key Value internal URL.