Skip to content

Console troubleshooting

A console problem does not stop model routing. If the console listener cannot bind its address, load its TLS certificate or serve, Prism keeps answering on the main address, logs the error and reports it in /prism/status:

Terminal window
curl -s http://127.0.0.1:18000/prism/status | python3 -c 'import json,sys; print(json.load(sys.stdin).get("console"))'
# {'state': 'unavailable', 'reason': 'bind_failed'}

reason is bind_failed, tls_failed or serve_failed; a working console reports state: running. Prism does not switch to another port or fall back to plain HTTP. Fix [console] bind or the TLS files and restart Prism.

prism console prints the configured address and token; it does not check that the console is running.

Symptom Cause What to do
Connection refused on port 18081, while curl http://127.0.0.1:18000/health answers the console listener is not running: [console] enabled = false, [personal] enabled = false, the bind failed, or the browser dials another address than bind run prism console in the config directory to see the address; check /prism/status as above; check [console] and restart
403 local access required on /prism/ui/ from another machine the URL points at the main address (:18000), not the console port open the address prism console prints
404 on /prism/ui/ [personal] enabled = false: no console set [personal] enabled = true (the default) and restart
The token is refused PRISM_ADMIN_TOKEN in Prism’s environment replaces the token file, or the tab keeps an old value run prism console for the token Prism uses; sign out in the page and paste it again
Prism does not start: serve failed: console token "…/console-token" must not be readable by group or others (chmod 600) the token file was created or copied with open permissions chmod 600 the file and restart, or delete it so Prism creates a new one
Prism does not start: [console] bind "…" serves the admin console in plaintext on a non-loopback address: … a non-loopback bind without TLS set tls_cert and tls_key, bind a loopback address, or set allow_plaintext = true on a trusted network (remote access)
No passkey option on the sign-in page the console is opened as 127.0.0.1 or over HTTP on a network address open it as http://localhost:18081, through an SSH tunnel, or over HTTPS with a host name
Email sign-in link does not sign in on an HTTP console the session cookie needs HTTPS set [personal] trusted_http_origin to the exact HTTP origin (remote access)
Restart Prism is missing or disabled Allow restart and stop from the console is off, or was turned on without a restart since turn it on under Configuration → Maintenance and restart Prism on the server once
After Stop, Prism starts again 5 seconds later the systemd unit lacks RestartPreventExitStatus=0 add RestartForceExitStatus=75 and RestartPreventExitStatus=0 to [Service], then systemctl --user daemon-reload (restart rules)
A saved setting has no effect Prism reads its configuration once at start restart Prism; a value saved in the console wins over the same key in config.toml

Service logs: journalctl --user -u prism (installer, Linux), ~/Library/Logs/prism/prism.err.log (macOS), journalctl -u prism (Debian package).