A practical guide to setup, forwarding, troubleshooting, limits, and the security model.
Run your local web app.
Choose the Web, Windows, or Python agent.
Open the client and answer its prompts.
No command-line parameters are required.
WebTNX is a lightweight path-based HTTP relay.
WebTNX is optimized for temporary HTTP sharing on constrained infrastructure.
Local hosting is your localhost app; proxy capability is recreating HTTP requests there.
WebTNX forwards the complete safe HTTP envelope.
Static same-site asset paths receive the active Tunnel ID automatically.
Hop-by-hop headers are regenerated; native clients provide better header fidelity.
Confirm the app and port.
Allow the site origin; native clients do not need CORS.
The local response took too long.
WebTNX automatically prefixes statically identifiable same-site assets with your Tunnel ID.
Reduce the payload.
Keep the agent running and reconnect expired sessions.
Registration creates separate random token and AES keys.
The relay is trusted, so this is not claimed as end-to-end encryption.
WebTNX adds the Tunnel ID automatically.
TLS and AES-256-GCM protect traffic.
It keeps deployment simple.
Browsers enforce same-origin policy.
Use a different ID for each.
It protects small servers.
Wait for the old session to expire.
Short non-streaming calls can work.
Usually, with the same CORS requirements.
No; active state is in memory.
Keep the process alive with a process manager.
It disappears only after a successful check.