zeabur-port-mismatch

Diagnose and resolve port mismatches between services and proxy configurations.

40|9|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/zeabur/zeabur-claude-plugin --skill zeabur-port-mismatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeabur-port-mismatch
Source: https://github.com/zeabur/zeabur-claude-plugin/tree/main/skills/zeabur-port-mismatch
Command: npx skills add https://github.com/zeabur/zeabur-claude-plugin --skill zeabur-port-mismatch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves issues where your service's port configuration doesn't align with what the proxy expects, leading to connection errors like timeouts or refusals.

Core Features & Use Cases

  • Diagnose Port Mismatches: Compares expected proxy ports with actual container-exposed ports.
  • Resolve Connection Errors: Fixes dial tcp timeouts and connection refused errors by aligning service and proxy ports.
  • Handle Headless Services: Provides solutions for services that don't expose HTTP ports, preventing 502 errors.
  • Use Case: When your deployed application shows a dial tcp 10.x.x.x:3000: i/o timeout error, this skill helps you identify and fix the port discrepancy.

Quick Start

Use the zeabur-port-mismatch skill to fix a service that is showing a connection refused error.

Frequently Asked Questions about zeabur-port-mismatch

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

FAQPage Schema
Why does my proxy show a dial tcp timeout or connection refused error?

A dial tcp timeout or connection refused error occurs when your service's container-exposed port does not align with the port expected by the proxy configuration.

How do I fix a port mismatch between my container and proxy?

Fix a port mismatch by comparing the expected proxy ports with the actual container-exposed ports and updating the configuration to align both values.

What is the best way to prevent 502 errors with headless services in a proxy?

Prevent 502 errors with headless services by implementing background HTTP health checks to verify connectivity when the services do not expose standard HTTP ports.

Can I use this to diagnose connection issues for non-HTTP services?

Yes, you can diagnose connection issues for non-HTTP services by implementing background health checks to manage headless services that do not expose HTTP ports.

Does this approach resolve dial tcp i/o timeout errors on specific ports?

Yes, this approach resolves dial tcp i/o timeout errors on specific ports by aligning the container-exposed port with the port configured in the proxy settings.