Skip to content

Open the console from another machine

By default the console listens on 127.0.0.1:18081 and only a browser on the Prism machine can open it. Choose one of three ways to reach it from another machine. No reverse proxy is needed for any of them.

Keep the console on loopback and forward its port from the machine with the browser:

Terminal window
ssh -N -L 18081:127.0.0.1:18081 user@prism-host

Open http://localhost:18081/prism/ui/ on that machine and sign in with the token from prism console on the Prism host. Closing the SSH session closes the access. Because the address is localhost, passkeys work too.

Bind the console to an address of the Prism machine and confirm that the network is trusted:

[console]
bind = "100.64.0.10:18081" # this machine's tailnet address
allow_plaintext = true # only on a network you trust, such as a WireGuard tailnet

Restart Prism. prism console now prints http://100.64.0.10:18081/prism/ui/. The same settings are under Configuration → Network and access (Console address, Allow plaintext HTTP outside loopback).

Plain HTTP is accepted without allow_plaintext only on loopback. Private address ranges (LAN, tailnet, link-local) do not count as encrypted. A non-loopback bind without TLS and without allow_plaintext = true stops Prism from starting:

[console] bind "192.0.2.10:18081" serves the admin console in plaintext on a non-loopback address: set [console] tls_cert and tls_key, bind a loopback address, or acknowledge the exposure with [console] allow_plaintext = true

Give the console a certificate and key in PEM format (both or neither):

[console]
bind = "console.example.net:18443"
tls_cert = "/etc/prism/console.crt"
tls_key = "/etc/prism/console.key"

With tls_cert set, prism console prints an https:// URL.

Passkeys need a secure context and a host name:

  • a loopback console opened as http://localhost:18081 (or through an SSH tunnel to localhost);
  • an HTTPS console with a host name. Set [console] public_url to the origin people open, for example https://console.example.net:18443, when it differs from the bind. Passkeys are bound to that host; changing it later can make existing passkeys unusable.

An HTTP console on a tailnet or LAN address offers no passkeys. Owner-secret sign-in works there. Email links and invitation links need one more setting, because the session cookie is normally sent over HTTPS only:

[personal]
trusted_http_origin = "http://100.64.0.10:18081"
[mail]
link_base_url = "http://100.64.0.10:18081"

trusted_http_origin names one exact HTTP origin on which Prism issues session cookies without the Secure flag. It does not open a listener; the console still needs allow_plaintext = true for that bind. Sign-in requests on any other HTTP address are refused. Browsers do not separate cookies by port, so use a host whose other HTTP services you trust. Changing it needs a restart.

Reaching the console address is not enough to use it. Every data request needs the owner token or a signed-in session, a matching browser Origin, and JSON bodies without unknown fields. The main address (:18000) answers 403 local access required to the console pages and API from another machine; only the console listener serves them to remote browsers.