Auricast Manuals· Installation Manual

Remote Access And HTTPS

Auricast has two ways in: the LAN address for PCs in your building, and Auricast Connect for reaching the screens from outside.

On Your Own Network

The screens are served over HTTPS on the box's address, at port 8443 by default:

https://<box name or IP address>:8443/

This comes from AIR_WEB in /etc/auricast/air.env (default 0.0.0.0:8443). Allow that port through any firewall between the studio PCs and the box.

The Certificate

Without a certificate of your own, Auricast makes a self-signed certificate once, for the box's names and addresses, and keeps it in a folder beside the station folder (/var/lib/auricast/tls/ by default). Browsers warn about a certificate they do not know. Accept it once on each PC.

To use your own certificate, set both in air.env and restart:

SettingWhat it does
AIR_TLS_CERTThe certificate file.
AIR_TLS_KEYIts private key. Needed whenever a certificate is set.

The Control Address

A second, plain-HTTP address, 127.0.0.1:8095 (AIR_CONTROL), is for scripts on the box itself. It has no sign-in, so it listens on the box only and is not reachable from the network.

From Outside: Auricast Connect

Remote Management, the screens from anywhere, is part of the free plan. Auricast Connect gives the station an address of the form <station>.auricast.net. It works through an outbound tunnel from the box, so you do not open any ports on your router and do not need a fixed IP address.

To turn it on you need an enrollment code from Auricast, then on the box:

sudo auricast-setup connect <code>

This installs the tunnel program from Cloudflare's package repository if it is not there, enrolls the station, starts a tunnel service that runs at every boot, and sets the station's public address in air.env. The tunnel's key is stored encrypted and never shown. Then restart the service so invite links use the public address:

sudo systemctl restart auricast-air

To switch it off again, run sudo auricast-setup disconnect. The screens go back to the LAN only.

Signing In From Outside

From outside the building, signing in asks for a code from an authenticator app as well as the password, so a stolen password alone is not enough. Inside the LAN it is never asked. The first time, each user scans a QR code with an authenticator app. See Signing In For The First Time.

Admins manage this per user in Setup → Users & Access, in the Code From Outside column: Clear after a lost phone (they set up a new one at their next sign-in from outside), and for users who are not Admins, No Code to allow a password alone. An Admin is always asked.

The Public Address

The address Connect gives (AIR_PUBLIC_URL) is where invitation links point, so a new user invited from outside gets a link that works from outside.

Remote Broadcasting

Browser remotes (a microphone and return feed from a laptop or phone) are a paid feature. They use the same public address. Where a direct connection is not possible, audio goes through a relay, and a station may use its own relay key in Setup → Overview. See the Administration manual for using remotes.