pinggy-tunnel

Expose localhost services publicly via SSH reverse tunnels through Pinggy.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill pinggy-tunnel-signmanal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinggy-tunnel
Source: https://github.com/Signmanal/VIGIL/tree/main/optional-skills/devops/pinggy-tunnel
Command: npx skills add https://github.com/Signmanal/VIGIL --skill pinggy-tunnel-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need to install dedicated tunneling software or configure complex network rules to share local services, development servers, or webhook endpoints with external parties for temporary testing and collaboration.

Core Features & Use Cases

  • Zero-install tunneling: Uses the host's stock SSH client to connect to Pinggy's servers, no additional binaries or daemons required.
  • Multiple tunnel types: Supports HTTP/HTTPS, TCP, and TLS tunnels for dev servers, databases, MCP endpoints, and LLM inference services.
  • Access control options: Includes built-in support for HTTP Basic auth, bearer token gates, IP whitelisting, CORS, and HTTPS redirects to secure shared endpoints.
  • Use case example: A developer can quickly expose their local Ollama LLM endpoint to a remote teammate for testing without deploying it to a public cloud server.

Quick Start

Use the pinggy-tunnel skill to generate a public HTTPS URL for your local service running on port 8000 so you can share it with external webhook providers or teammates for one-off testing.

Frequently Asked Questions about pinggy-tunnel

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

FAQPage Schema
How do I expose my localhost dev server to the public internet?

You can expose localhost dev servers to the public internet by establishing SSH reverse tunnels through Pinggy, generating temporary public HTTPS URLs for external testing and collaboration without installing dedicated tunneling software.

Can I test webhooks locally without deploying my application?

Yes, you can test webhooks locally without deployment by creating a public tunnel endpoint for your local webhook receiver using an SSH client, allowing external providers to reach your local service directly.

Do I need to install any additional software to create an SSH tunnel?

No additional software installation is required to create an SSH tunnel; the skill uses the stock SSH client available on your host PATH to connect to Pinggy servers and establish the public tunnel.

What is the best way to share a local LLM inference endpoint with a remote teammate?

The best way to share a local LLM inference endpoint is to use a zero-install SSH tunnel to expose the local service port publicly, enabling remote access for testing without cloud deployment.

Does zero-install tunneling support access control and CORS for shared endpoints?

Zero-install tunneling supports access control and CORS for shared endpoints, offering HTTP Basic auth, bearer token gates, IP whitelisting, and HTTPS redirects to secure your publicly exposed local services.

When should I not use SSH reverse tunnels for exposing local services?

You should not use SSH reverse tunnels for permanent production hosting or long-term traffic, as this approach is designed for temporary public sharing, one-off testing, and remote collaboration workflows.