Published routes

Your connector must already have a named local service, such as web pointing to http://127.0.0.1:8080.

Publication from a connectorCopy Anchor Link

To publish a path on an existing website:

1. Select a connector in account Tunnels.
2. Select Add route, then Website path.
3. Enter the Local service name.
4. Select the Website.
5. Enter the public path.
6. Select Publish route.

For example, /admin can forward to http://127.0.0.1:8080/admin. Use / with a prefix match for the whole website.

Select a path card in Connection map to change its service, matching, or enabled state. Remove route removes that publication.

Publish a new hostnameCopy Anchor Link

1. Select Add route, then New hostname.
2. Enter the Local service name.
3. Select Continue to website.
4. Complete website creation with the generated virtual origin.
5. Point the hostname's DNS record to waf-ingress.loclix.network.

Each new hostname needs a website in your account. Several websites can use the same connector and service. Your local application must accept their public Host headers.

Loclix does not create DNS records for you. See DNS connection for root domain requirements. Paths on an existing website need no DNS changes.

Website route setupCopy Anchor Link

You can also add routes from Network > Tunnels on a website:

1. Select Add tunnel route.
2. Select an account connector.
3. Enter the public path.
4. Choose an exact match or path prefix.
5. Enter the configured local service name.
6. Select Save tunnels.

For a whole website, use tunnel://CONNECTOR-ID/SERVICE as its origin. Remove any default HTTP origin pool and direct-origin TLS options when switching to this virtual origin.

Path matchingCopy Anchor Link

The longest enabled path wins; an exact match wins over a prefix of the same length. /admin matches /admin/users, but not /administrator.

Explicit tunnel paths take precedence over HTTP origin routes. An HTTP origin route can override a virtual default origin. Unmatched paths use the website's default routing.

Routes apply to the website and its connected aliases. They preserve paths and query strings. Reserved Loclix and certificate-validation paths cannot be used for tunnel routes.

Failure behaviorCopy Anchor Link

A matched tunnel route returns an error if its connector is unavailable. It does not send the request to the website's other origin.

Pausing a connector keeps its routes in place and stops their requests. Disabling or removing a route removes its match, so that path uses the remaining website routing.

Security and identityCopy Anchor Link

Website security rules and Zero Trust apply before forwarding. Origin-confirmed API sessions require direct origins; choose another API identity mode before using tunnels.

Shared caching is bypassed for the whole website while it has tunnel routes or a tunnel origin. See tunnel limits.