Relay Ports
Which ports a Viaalink Relay uses, the NAS package defaults, how to change any port, and how to get addresses without a port number.
The ports
Every port is a setting. The NAS packages (ASUSTOR, Synology) give a new install from Relay 1.39 its own range, so it does not collide with the NAS’s own services:
| Setting | NAS default | What it is | Forward on the router? |
|---|---|---|---|
ssh-address | :28022 | Where devices connect (SSH) | Yes, as is |
http-address | :28081 | The Relay’s own HTTP listener, and the dashboard on your home network | Only for addresses without a port, see below |
https-address | :28443 | The Relay’s own HTTPS listener | Only for addresses without a port, see below |
stun-port | 3478/udp | Control port for calls through firewalls (the standard port for it) | Yes, as is |
| ADM reverse proxy (ASUSTOR) | 28080 | The dashboard with ADM’s certificate; the ADM desktop icon opens it | Yes; ADM’s EZ-Router asks the router for it when port forwarding is on (the default) |
caddy-http-port / caddy-https-port | 80 / 443 | Only when HTTPS via Caddy is on (ASUSTOR) | Yes, as static rules |
A NAS installed before 1.39 keeps the ports it has: SSH 2222, HTTP 8080 and HTTPS 8443. An update never rewrites an existing config.yml, so your router forwards keep working.
The Docker image is a separate case: it listens on 2222, 80 and 443, because a server of its own usually has those free. See Run Relay with Docker and Run Relay on Synology or QNAP.
Changing a port
Open the dashboard, go to Settings › Domain & Ports, change the port and save. The Relay restarts; a few seconds of a 502 error in the browser is that restart. Nothing needs reinstalling.
- Devices read the SSH port when they join. A device asks the Relay where to connect (
/_relay/discovery) when it joins, so a device that joins after the change gets the new port. A device that joined before may keep dialling the port it was given. Keep that port working from the outside: leave the router’s external port as it was, point it at the new port on the NAS, and fill in Public SSH address (Settings › Network / UPnP) with that external port, so new devices are told the same one. - Router forwards are yours to move. On ASUSTOR, ADM’s EZ-Router follows the dashboard’s Network tab for the SSH, dashboard and
stun-portports, while Automatically forward ports on my router (via ADM EZ-Router) is ticked (the default) and the router accepts UPnP for high ports. On Synology, DSM manages router forwards itself: change them under Control Panel › External Access › Router Configuration, or on the router. Change every static rule on the router too. - The NAS desktop icons keep working. ASUSTOR’s icon opens
28080, and ADM’s reverse proxy followshttp-address, so moving the HTTP port does not break it. Synology’s icon opens28081on a new install; if you move the HTTP port elsewhere, or the install is from before 1.39 and kept8080, open the dashboard by its address instead (http://<NAS-LAN-IP>:8080/_relay/dashboardon such an older install).
Addresses without a port number
Published addresses carry a port whenever the Relay’s public HTTPS port is not 443: https://app.example.com:28443. That works, but most people want https://app.example.com. A NAS cannot simply listen on 443, because the NAS’s own web server (ADM, DSM) usually holds 80 and 443. Two setups give addresses without a port.
1. Port translation on the router (Synology, or ASUSTOR without Caddy)
Forward external 443 to the NAS’s HTTPS port and external 80 to its HTTP port:
router :443 → NAS :28443
router :80 → NAS :28081
router :28022 → NAS :28022 (devices)Then tell the Relay which ports the outside world sees, so the addresses it prints and the invite and sign-in links it hands out carry no port. Add to config.yml:
https-port-override: 443
http-port-override: 80The dashboard has no field for these yet. They take effect after a restart, and change only what the Relay advertises, not where it listens.
2. HTTPS via Caddy (ASUSTOR)
With Settings › HTTPS on, the Relay’s own Caddy takes the public ports (caddy-http-port / caddy-https-port, default 80 / 443) and gets a wildcard certificate over DNS-01. Published addresses then advertise Caddy’s port. If ADM’s web server already holds 80 and 443, either move ADM’s web server, or give Caddy free ports and translate on the router as above (for example external 443 to Caddy’s port) with https-port-override: 443.
Routers commonly refuse UPnP for ports below 1024, so 80 and 443 are static rules in the router’s own settings, never something EZ-Router or UPnP opens for you.
Checking the result
The tunnel banner on a device shows the address as the Relay advertises it.
From outside your network (a phone on mobile data, for example), this prints the app’s HTTP status and
0for a valid certificate:bashcurl -sS -o /dev/null -w '%{http_code} %{ssl_verify_result}\n' https://<name>.relay.example.com/An invite link or sign-in link from the dashboard opens as is.