Tunnels
Publish local HTTP services without opening an inbound port on your server.
Install a connector on your server to make a local service available through a Loclix website. The connector opens an encrypted outbound connection to Loclix and forwards website requests to the service.
One connector can serve several websites and up to 64 named local services in your account. For example, app.example.com can use a service on http://127.0.0.1:8080, while api.example.com uses one on port 3000.
Get started
- Install and activate a connector on your server.
- Publish a hostname or path for a named service.
- Complete DNS and certificate setup for each new website.
Open Tunnels in the account navigation to manage connectors. Select a tunnel to view its Connection map, which groups published hostnames and paths by local service.
Connection status
The connection map shows your publications and services reported by the connector, including unpublished services. Select a service card or Edit tunnel to change its destination.
Ready means the tunnel is connected, the publication is enabled, and DNS setup is complete. Dashboard-managed destinations also need confirmation that the connector has applied the saved settings.
DNS pending, Paused, and Tunnel unavailable identify the next issue to resolve. Select a path card to edit its route, or a hostname card to open website settings.
Access controls
Website security rules and Zero Trust apply before requests reach the connector. To require sign-in, configure a Zero Trust application and verify its access assertions at your service.
Shared caching is bypassed for the whole website while it has tunnel routes or a tunnel origin.
Private service hostnames
A Virtual origin, such as tunnel://connector-id/web, identifies a connector and one of its named services. Use it as the origin when creating a website without a public origin IP.
Several websites can use the same named service. Your application must accept each public hostname in its Host header. See published routes for DNS and path setup.
Existing website connectors
If your account shows a connector migration notice, install the current connector and replace connector.json with the account configuration supplied by setup. Use that generated configuration even if a connector ID has changed.
Existing tokens remain valid during this migration. Manage new connectors and credential changes from account Tunnels. An account supports up to 16 connectors; contact support if an older configuration exceeds that limit.