GitHub
Meet WireRiftA small binary. A direct connection. Your infrastructure.InstallationNative binaries for your machine. No runtime to manage.Run your own serverThe public edge belongs to you.HTTP & WebSocket tunnelsShare web apps, receive webhooks, and keep WebSockets connected.TCP tunnelsA path for the protocols beyond HTTP.Security & accessLayer access controls around what you share.Traffic inspectorSee the request. Understand the response. Try it again.Under the wireOne connection. Many independent streams.Dashboard APIYour tunnels and traffic, programmatically.ConfigurationKeep your connections together in a readable config file.Docker deploymentGive your public edge a reproducible home.Local HTTPS developmentA trusted development edge, without a public domain.TroubleshootingGet back to a working connection.
Documentation, without the detour.ESC to close
Browse documentation
DOCUMENTATION / REFERENCE

Troubleshooting

Get back to a working connection.

The client cannot connect

Check the --server host and control port, the server process, and inbound firewall rules. Confirm that the client and server use the same token. A local app's port and the server's control port are different endpoints.

The URL does not resolve

Check DNS for both the base tunnel domain and its wildcard. The records must point at the tunnel server, rather than the machine running the client. Wait for DNS propagation after a change.

The browser reports a certificate error

A self-signed certificate is not publicly trusted. Configure ACME with a domain you control and a reachable HTTP challenge endpoint, or install an appropriate certificate. Check that the certificate covers the hostname you are opening.

The tunnel connects, but the app does not respond

Open the app locally first. Verify the local port and process, then use --inspect to check paths, headers and responses. If your development server restricts allowed hosts, configure its explicit host allowlist for the tunnel URL.

Still stuck?

Run the server with --v for verbose logs and inspect --help on both binaries. When reporting an issue, include your OS, version, commands with secrets removed, and a minimal reproduction.

Based on the upstream WireRift reference . Check the source for the latest options.

PreviousLocal HTTPS developmentNeed a hand?Ask on GitHub