vers-networking

Configure public URLs, TCP port routing, and TLS termination for Vers VMs.

2|4|Updated Feb 5, 2026

Search Tags:#networking #ssh #vm #tls #public url #vers #port routing

Ready to run

npx skills add https://github.com/hdresearch/pi-vers --skill vers-networking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vers-networking
Source: https://github.com/hdresearch/pi-vers/tree/main/skills/vers-networking
Command: npx skills add https://github.com/hdresearch/pi-vers --skill vers-networking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of making services running on Vers Virtual Machines accessible to the internet, handling complex networking configurations like public URLs, port routing, and TLS termination.

Core Features & Use Cases

Public URL Access: Every VM gets a unique public URL to serve traffic on any port.
TLS Termination: The Vers proxy handles TLS, so your services don't need to.
IPv6 Binding: Services must bind to IPv6 (::) to be reachable.
Cross-VM SSH: Securely SSH into other VMs through the TLS proxy without complex setup.
Use Case: Deploy a web application on a Vers VM and expose it to the public via its unique URL, complete with automatic HTTPS.

Quick Start

Use the vers-networking skill to expose your service running on port 3000 on VM ID 'your-vm-id'.

Frequently Asked Questions about vers-networking

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

FAQPage Schema

How do I expose a local service running on a Vers VM to a public URL?▼

Expose local services on Vers VMs by using the vers-networking skill to configure a unique public URL and route TCP traffic to your specified port. The Vers proxy handles TLS termination, providing secure HTTPS access automatically.

Does my service need to bind to a specific IP address for public URL access on Vers?▼

Yes, services must bind to IPv6 (`::`) to be reachable through the Vers public URL. Binding to IPv6 ensures the Vers proxy can correctly route external TCP traffic to your application's port.

How does TLS termination work for applications deployed on Vers VMs?▼

TLS termination for Vers VM applications is handled by the Vers proxy, so your services do not need to manage SSL certificates. The proxy intercepts HTTPS traffic and forwards it securely to your application port.

Can I SSH into another Vers VM through the public URL proxy?▼

Yes, you can securely SSH into other Vers VMs through the TLS proxy. The vers-networking skill manages cross-VM SSH connections through public endpoints without requiring complex manual network configuration.

What is the best way to route TCP traffic to a specific port on a Vers VM?▼

The best way to route TCP traffic to a specific port on a Vers VM is using the vers-networking skill. It configures port routing and assigns a unique public URL to serve traffic for your application.

Why is my service not accessible externally after configuring public URL routing on Vers?▼

If your service is not accessible externally after configuring public URL routing, verify it is binding to the IPv6 address (`::`). Services that only bind to IPv4 will not be reachable through the Vers proxy.