pinggy-tunnel

Expose local network services via SSH-based reverse tunneling.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/zangjeicy/Hermes --skill pinggy-tunnel-zangjeicy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinggy-tunnel
Source: https://github.com/zangjeicy/Hermes/tree/main/optional-skills/devops/pinggy-tunnel
Command: npx skills add https://github.com/zangjeicy/Hermes --skill pinggy-tunnel-zangjeicy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of making local development servers, webhooks, or internal tools accessible to the public internet without complex network configuration or permanent daemon installations.

Core Features & Use Cases

  • Zero-Install Tunneling: Leverages existing SSH clients to create secure reverse tunnels on the fly.
  • Access Control: Supports built-in security features like Basic Auth, bearer tokens, and IP whitelisting to protect exposed services.
  • Use Case: Quickly share a local web dashboard with a remote teammate or receive real-time webhook callbacks from services like Stripe or GitHub directly to your local machine.

Quick Start

Use the pinggy-tunnel skill to expose the local service running on port 8000 to a public URL.

Frequently Asked Questions about pinggy-tunnel

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

FAQPage Schema
How do I expose a localhost development server to the internet?

You can expose a localhost development server to the internet using SSH-based reverse tunneling, which creates a temporary public URL that routes external traffic directly to your local service port.

What is the best way to receive webhooks from Stripe or GitHub on my local machine?

The best way to receive webhooks from Stripe or GitHub on your local machine is by establishing a secure reverse tunnel, allowing remote webhook endpoints to reach your local API instances for real-time testing.

Can I secure a public tunnel to my local service?

Yes, you can secure a public tunnel to your local service using built-in access controls like Basic Auth, bearer tokens, and IP whitelisting to protect the exposed endpoint from unauthorized access.

Do I need to install a permanent daemon to create an SSH reverse tunnel?

No, you do not need a permanent daemon to create an SSH reverse tunnel; the process leverages your existing SSH client to establish secure, temporary public connectivity on the fly without complex configurations.

What are the requirements to expose local network services to the public internet?

To expose local network services to the public internet, you need a functional SSH client and an active local service port to establish the secure reverse tunnel connection for remote access.