Cadencia de releases
Las notas de release de CLI y docs se actualizan continuamente, con notas de compatibilidad por version.
Ver release notesAnswer-first summary
Sigue este orden: instalar CLI, autenticar, ejecutar primer tunel y luego MCP/webhooks/referrals segun tu caso. Usa CLI Flags y Troubleshooting para operacion diaria.
Comando rapido
instatunnel auth login -e you@example.com && instatunnel 3000 --subdomain docs-demoErrores comunes y solucion rapida
Usa estas referencias para evaluar compatibilidad, confiabilidad y seguridad.
Las notas de release de CLI y docs se actualizan continuamente, con notas de compatibilidad por version.
Ver release notesRevisa enforcement de politicas, capas de auth y salvaguardas operativas en el security whitepaper.
Abrir security whitepaperLas guias de troubleshooting cubren fallos comunes, recuperacion y compatibilidad base de CLI.
Leer troubleshooting guidesUse a domain you control with an InstaTunnel tunnel. Custom domains are available on Pro and Business plans and must be verified through DNS before traffic can be routed.
Use a subdomain when possible
We recommend a hostname such as app.example.com or hooks.example.com. A normal root domain such as example.com cannot use a CNAME with many DNS providers; it requires ALIAS, ANAME, or CNAME flattening support.
Open the dashboard, create a tunnel, and enter the hostname you own in the Custom Domain field. The dashboard then shows a unique TXT value for that tunnel.
Copy the exact record name and value from the dashboard. For app.example.com, the record name will look like _instatunnel-verification.app.example.com and the value starts with itv_.
Do not reuse a TXT value from another tunnel. The value is unique to the pending setup request.
DNS provider forms differ: for app.example.com, the Name field may be app instead of the complete hostname. With Cloudflare, set this record to DNS-only while the domain is connected. Do not point it at the VPS IP address.
Return to the dashboard and select Verify Domain. The TXT record must be visible in public DNS first. If the check reports that the record was not found, wait a few minutes and retry.
InstaTunnel does not route the hostname or start SSL setup before this verification succeeds.
After verification, SSL setup begins automatically. Keep the CNAME in place and allow a few minutes for DNS and certificate setup before testing HTTPS.
We require a matching DNS TXT record before associating a custom domain with a tunnel. Domains and subdomains under instatunnel.my or instatunnel.com cannot be used as custom domains.
Confirm that the record name is not duplicated by your DNS provider, the value matches exactly, and the record has propagated publicly. Some providers append your domain automatically when you enter a relative host name.
Use a subdomain such as app.example.com, or use your DNS provider's ALIAS, ANAME, or CNAME flattening feature. Do not replace this with an A record to the InstaTunnel VPS IP.
Mira planes y luego sigue una guia cuando quieras.
Para endpoints MCP en Pro/Business, usa: instatunnel 8787 --mcp.