pinggy-tunnel

Expose local services publicly via Pinggy SSH reverse tunnels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expose a local service to the public internet using Pinggy SSH reverse tunnels, with no daemon installation required; you simply run your SSH client and receive a public URL.

Core Features & Use Cases

  • No daemon to install; expose local services via a public Pinggy URL.
  • Supports HTTP/HTTPS via Pinggy, with optional security gates (basic auth, bearer tokens), CORS, and TLS.
  • Use cases include exposing dev servers, webhook receivers, MCP endpoints, and demos to remote collaborators.

Quick Start

Start your local service and run a Pinggy tunnel to expose it publicly.

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 dev server to the public internet without installing a daemon?

You can expose a local service to the public internet using Pinggy SSH reverse tunnels, which require no daemon installation. By running a minimal tunnel command with your existing SSH client, you receive a public URL to access your local development server remotely.

Can I secure an SSH tunnel with basic auth or bearer tokens for webhook receivers?

Yes, you can secure an SSH tunnel using optional security gates like basic auth and bearer tokens. This ensures that exposed webhook receivers and MCP endpoints require proper authentication before being accessed over the public internet.

Do I need a Pinggy token to get a persistent public URL for my local service?

Pro features such as persistent public URLs require a Pinggy token. Without a token, you can still expose local services via a Pinggy relay at a.pinggy.io:443, but the generated public URLs will be temporary and subject to URL expiry.

What is the best way to share a local application demo with remote collaborators?

The best way to share a local application demo is by using an SSH reverse tunnel. It provides an instant public HTTPS URL linked to your local service, allowing remote collaborators to view the demo without any complex network configuration.

Does the Pinggy tunneling service support TLS and CORS for HTTP endpoints?

Yes, the Pinggy tunneling service supports HTTP/HTTPS with TLS and CORS. This allows your local service to handle cross-origin requests securely when exposed via the public URL.

What are the limitations of using a daemon-free SSH tunnel for local services?

Limitations of a daemon-free SSH tunnel include reliance on an active SSH client connection to maintain the public URL, and the potential expiration of the URL without a pro token, which disrupts long-running local service endpoints.