Release-Kadenz
CLI- und Docs-Release-Notes werden laufend aktualisiert, inkl. versionsspezifischer Kompatibilitatshinweise.
Release Notes ansehenAnswer-first summary
Empfohlene Reihenfolge: CLI installieren, authentifizieren, ersten Tunnel starten und danach MCP/Webhooks/Referrals je Use Case. Fur den Alltag nutze CLI Flags und Troubleshooting.
Schnellbefehl
instatunnel auth login -e you@example.com && instatunnel 3000 --subdomain docs-demoHaufige Fehler und schnelle Fixes
Nutze diese Referenzen fur Kompatibilitat, Zuverlassigkeit und Sicherheitslage.
CLI- und Docs-Release-Notes werden laufend aktualisiert, inkl. versionsspezifischer Kompatibilitatshinweise.
Release Notes ansehenPrufe Policy-Enforcement, Auth-Layer und operative Schutzmechanismen im Security Whitepaper.
Security Whitepaper offnenTroubleshooting-Guides decken haufige Fehler, Recovery-Schritte und CLI-Baselines ab.
Troubleshooting-Guides lesenCreate memorable, consistent URLs for your tunnels with custom subdomains. Perfect for demos, development, and sharing.
Sign in with an InstaTunnel account to choose a subdomain, including on the Free plan. Anonymous tunnels use random names only. First-party and security-sensitive names such as api, login, and support cannot be claimed.
Instead of random URLs like abc123.instatunnel.my, get memorable URLs like myapp.instatunnel.my
When no subdomain is specified, InstaTunnel automatically generates a unique 6-character subdomain.
Use consistent naming patterns for organized development workflows.
Available names are first-come-first-served for signed-in users. Reserved names are unavailable even when not in use. Try a different name or use a random subdomain.
🎯 Best Practice: Use descriptive subdomains for demos and consistent subdomains for development environments. For quick testing, random subdomains work perfectly.
Plane ansehen und dann gefuhrt starten.
Fur MCP-Endpunkte auf Pro/Business nutze: instatunnel 8787 --mcp.