render-web-services

Configure Render web services including port binding, health checks, domains, and deploy lifecycle.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/greenmartialarts/EventCore --skill render-web-services-greenmartialarts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-web-services
Source: https://github.com/greenmartialarts/EventCore/tree/main/.junie/skills/render-web-services
Command: npx skills add https://github.com/greenmartialarts/EventCore --skill render-web-services-greenmartialarts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying and operating web services on Render involves many platform-specific behaviors—PORT binding, TLS termination at the edge, health check gating, custom domain DNS, and zero-downtime deploy rules—that cause failed deploys and misconfigurations when misunderstood. ## Core Features & Use Cases - Port and TLS Configuration: Explains binding to 0.0.0.0 on the PORT variable, reserved ports, multi-port private listeners, and edge TLS termination. - Health Checks and Deploy Lifecycle: Covers healthCheckPath requirements, pre-deploy commands for migrations, zero-downtime swaps, drain behavior with maxShutdownDelaySeconds, and rollbacks. - Domains, Disks, and Auto-Deploy: Details CNAME/apex/wildcard DNS setup, persistent disk constraints (single instance, no zero-downtime), autoDeployTrigger modes, and PR previews. - Use Case: A deploy succeeds in the Render Dashboard but never takes traffic—use this Skill to diagnose that the health check path returns 404 or the app binds to 127.0.0.1 instead of 0.0.0.0. ## Quick Start Ask the assistant to configure a Render web service with a health check endpoint and a custom domain, or to troubleshoot why a deploy is not going live.

Frequently Asked Questions about render-web-services

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

FAQPage Schema
How do I configure a health check for a Render web service?

Set healthCheckPath in your Blueprint or the Health Check Path field in the Dashboard to a dedicated route like /health. Render sends HTTP GET requests and requires a 2xx or 3xx response; failures block the deploy from going live.

Why is my Render deploy not going live after a successful build?

The most common causes are a health check returning 4xx/5xx, the app binding to 127.0.0.1 instead of 0.0.0.0, or listening on the wrong port instead of the PORT environment variable. Verify the health path is served by the same process handling production traffic.

How do I add a custom domain to a Render web service?

Create a CNAME record pointing your hostname to [service-name].onrender.com, then add the domain in Dashboard Settings under Custom Domains. Render automatically provisions and renews TLS certificates after DNS verification.

Does Render support zero-downtime deploys with persistent disks?

No. Attaching a persistent disk limits the service to a single instance and disables zero-downtime deploys. Disk sizes can be increased but not decreased, and disks are not mounted during the build phase.

Can I run database migrations before a Render deploy goes live?

Yes, use the preDeployCommand, which runs in the new image before traffic switches. If the command exits non-zero, the deploy is canceled and the previous revision keeps serving traffic.

What port should my app listen on for Render web services?

Listen on 0.0.0.0 using the PORT environment variable, which Render sets for you (often defaulting to 10000). Avoid reserved ports 18012, 18013, and 19099, and note that only the PORT-aligned port receives public traffic.