Skip to content

Published services

A published service makes something on the site's LAN — a camera, a recorder, a management page — reachable from the internet at its own HTTPS address, even when the site has no public IP address. The gateway carries the connection through a relay, so nothing on the LAN is exposed directly.

Where: Connectivity > Published services. The entry is always in the sidebar, whether or not anything is published.

Publishing a service

  1. Click Publish a service.

  2. Fill in:

    Field Meaning
    Name Becomes the start of the address, e.g. cam1. Lower-case letters, digits and hyphens. Cannot be changed later
    Address on the LAN The machine to reach. Suggestions come from the devices the gateway has seen; any address is accepted
    The device speaks http or https
    Port Leave empty for the usual port of that protocol
    Name in the portal Optional label
    Require an access code On by default. Off means anybody who knows the address reaches the device, and the form says so

  3. Click Publish, then apply and confirm the change.

Until the device has applied it and reported back, the service shows Waiting for the gateway. It then gets an address of the form https://cam1.<gateway name>.<relay domain> with a publicly trusted certificate. Before the certificate exists the card says No address yet — waiting for a certificate.

Services can also be added from the Integrations catalogue (Open the catalogue).

Each service

The card shows the address, forwards to the LAN target, and:

Badge Meaning
Answering / Not answering Whether the gateway is serving it
Access code required / Open to anyone with the address Whether a code is needed
Not published Switched off but still configured
Not in the saved configuration The gateway reports it but the configuration does not describe it, usually a deletion not yet applied. Add to the configuration makes it editable again

Below are its access codes and its path.

A warning above the list says when a service needs a code and has none: nobody can reach it until you create one.

Changing a service

Edit changes the LAN address, protocol, port, label and whether a code is required. The name cannot change: it is part of the address, and a new name means a new URL on which every code already issued stops working. Saved changes go out with the next apply.

Stopping or deleting

  • Stop publishing switches the service off. The address, the certificate and the access codes are kept; Publish again restores it unchanged.
  • Delete (Yes, delete it to confirm) removes the address and every access code issued for it.

The relay

The relay this gateway uses card shows whether the relay is reporting normally. The relay forwards by hostname without decrypting: the gateway holds the certificate and terminates TLS. Which relay, and its address, is shown to platform administrators only; everyone else reaches services by their own names, because the relay behind them can change at any time.

If a relay is drained or fails, gateways move to another one automatically and DNS follows (60-second TTL). The service address does not change.