Local services

Dashboard service management requires connector release 0.19.0 or later. Update your connector if addresses are unavailable or saved changes cannot be applied. Contact support if setup reports that service management is unavailable.

Destination inspectionCopy Anchor Link

1. Open account Tunnels.
2. Select the connector.
3. Review its Local service cards.

Cards show addresses reported by the connector, including unpublished services. If replicas report different addresses for one service, the card lists each address.

Address unavailable means there is no current address report. Reports arrive about every 15 seconds, expire after 60 seconds, and are cleared when you replace the credential. The dashboard refreshes about every five seconds.

An address report confirms configuration, not whether the application is responding. Test the published website after changing a service.

Destination changesCopy Anchor Link

1. Select a local service card or Edit tunnel.
2. Enter the Local address.
3. Review every service address in the form.
4. Select Save changes.

Use an HTTP or HTTPS origin without a path, query, fragment, or embedded credentials. HTTPS requires a trusted certificate for that hostname.

The first address edit enables dashboard management for all services on the connector. The complete saved map applies to every replica. If replicas used different addresses, choose an address that works on all of them before saving.

Applying a new service map closes existing tunnel connections, so active requests and WebSockets can be interrupted. Configuration pending remains until current connector reports confirm the saved map. Offline or older connectors cannot confirm the change until they reconnect or update.

Dashboard-managed addresses take precedence over the local connector.json service map, including after restarts. Changing only the tunnel name or update preference does not enable service management. Address edits do not replace the token.

Service addition and removalCopy Anchor Link

Use Add service in Edit tunnel to add a destination, then Add route to publish it through a website.

A connector supports up to 64 services. Names contain 1–48 letters, numbers, underscores, or hyphens.

Remove attached routes and virtual origins before renaming or removing a service. An unpublished service stops accepting requests after the connector applies its removal. You can remove every service and leave the connector connected without publishing an application.

Data accessCopy Anchor Link

Your dashboard shows service names, local addresses, connector versions, and replica identifiers reported by the connector. Treat local addresses as account configuration and review who has access to your account.

See Published routes to connect a service to a hostname or path.