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.