pinggy-tunnel

Expose local services to the public internet via Pinggy SSH reverse tunnels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expose a local service to the public internet without installing extra daemons, enabling quick demos, webhook testing, and remote access via Pinggy's SSH reverse tunnels.

Core Features & Use Cases

  • Expose local development servers and webhook endpoints through ephemeral public URLs.
  • No daemon installation required; uses your existing SSH client and standard ports.
  • Supports HTTP/HTTPS exposure, TLS gates, and basic access control patterns for safe sharing.

Quick Start

Start a local service on port 8000 and run a Pinggy tunnel to publish 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 local development server to the public internet?

You can expose a local development server to the public internet by creating an SSH reverse tunnel using Pinggy. This generates an ephemeral public URL that routes external traffic directly to your local service without requiring any daemon installations.

What is the best way to test webhooks locally without deploying my application?

Testing webhooks locally is best achieved by establishing an SSH reverse tunnel via Pinggy. This provides a public URL that third-party services can send webhook requests to, securely forwarding the payload to your local listening service.

Do I need to install a daemon to create a public URL for my local port?

No, you do not need to install a daemon to create a public URL for your local port. Pinggy tunnels operate using your existing SSH client, requiring only that an SSH client is available on your system PATH and a local service is listening on 127.0.0.1.

Can I use SSH port forwarding to share an HTTP demo with basic access control?

Yes, you can use SSH port forwarding with Pinggy to share HTTP demos while applying basic or token-based access controls. Providing an optional Pinggy_TOKEN enables Pro features, and the tunnel supports HTTP/HTTPS exposure alongside TLS gates for safe sharing.

Does Pinggy SSH tunnel support HTTPS exposure for local services?

Yes, Pinggy SSH tunnels support both HTTP and HTTPS exposure for local services. By forwarding your local port through an SSH reverse tunnel, you receive a public URL equipped with TLS gates to ensure secure sharing of your development environment.