pinggy-tunnel

Expose local services to the internet via Pinggy SSH tunnels.

150|25|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Devsoul2026/Hermes-One-Click --skill pinggy-tunnel-devsoul2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinggy-tunnel
Source: https://github.com/Devsoul2026/Hermes-One-Click/tree/main/hermes-agent/optional-skills/devops/pinggy-tunnel
Command: npx skills add https://github.com/Devsoul2026/Hermes-One-Click --skill pinggy-tunnel-devsoul2026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expose local services to the internet without installing extra daemons or complex config, enabling rapid testing and demos.

Core Features & Use Cases

  • SSH reverse tunneling to expose 127.0.0.1:<port> as a public URL.
  • Flexible access control with Bearer tokens, Basic auth, or CORS.
  • Works for webhooks, demos, and remote testing across Linux, macOS, and Windows.

Quick Start

Run a single SSH command that forwards a local port to Pinggy and returns 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 dev server to the internet for webhooks?

You can expose a local dev server by establishing an SSH reverse tunnel via Pinggy, which links your local 127.0.0.1 port to a public URL without requiring extra daemons or complex configurations.

Can I add authentication to an SSH reverse tunnel?

Yes, you can secure an SSH reverse tunnel by applying access controls like Bearer tokens, Basic auth, or CORS headers directly through your Pinggy tunnel configuration.

Does Pinggy tunneling work on Windows and macOS?

Yes, Pinggy tunneling works across Linux, macOS, and Windows, allowing you to use standard SSH commands to expose local services regardless of your operating system.

What is the best way to test local services remotely without installing daemons?

The best way to test local services remotely without installing daemons is using an SSH reverse tunnel like Pinggy, which generates a public URL linked to your local endpoint for quick demos and remote testing.

Do I need extra config files to create a public URL for my local endpoint?

No, you do not need extra config files to create a public URL. You can run a single SSH command to forward a local port to Pinggy and immediately receive a public URL.