Troubleshooting
Start with Ship status on the Bridge: each problem is listed there with its reason, and the AI brings up real
problems on the Captain's or First Officer's next message. For what the AI did with a message, Sensors shows each
step and the one that went wrong (Systems and Sensors).
Starbase
| Problem |
Try |
| The Bridge doesn't load |
Is the start.bat (or start.sh) window open? Read its last lines. After 5 crashes in a row it stops trying and waits. |
| "Ollama isn't answering…" |
Start Ollama (on Windows it sits in the tray), or install it from ollama.com. Engineering → Starbase → Network has the address Starbase uses. |
| "Starbase is still running older code" |
The page is newer than Starbase: close the start.bat window, run it again, then refresh. |
| "Starfarer was updated. Reload this page" |
Starbase was updated while the page was open: reload it. |
| "…isn't installed (run install.bat again)" |
An update added a package: run install.bat (or install.sh) again, then restart. |
| A restart didn't happen |
Restart Starbase only works when Starbase was started by start.bat / start.sh. A data\restart.request file is picked up within seconds; if it stays there, Starbase isn't running. |
| Locked out |
Use a recovery code; the Captain can give anyone else a temporary password (Crew); on the Starbase PC, python -m starfarer reset-password <username>. Too many wrong tries locks sign-in for 15 minutes. |
| Low on disk |
Ship status warns about it. The Cargobay keeps space free on its drive, and backups keep only so many. |
Phones and other computers
| Problem |
Try |
| A phone can't reach Starbase |
Engineering → Starbase → Network → Anything on my home network, restart, and on Windows run allow-network.bat once (your network must be set to Private). Then open https://<the Starbase PC's address>:3010. Network |
| A certificate warning |
Trust Starbase's certificate once on that device: Ready Room → You → Security → Trust Starbase on your devices. |
| The mic doesn't work in a browser |
Every device but the Starbase PC needs HTTPS; allow the microphone for the page; tap the page once after it loads. |
| A phone didn't ring a timer |
Phones pause pages with the screen off; it rings when the screen comes back on. A Satellite or a Starship rings on time. |
| Two answers to one thing said |
Two of your devices heard it: the AI answers once if the words match, but keep a listening tab away from a speaker. |
| Can't sign in from outside |
Outside sign-in needs two-step sign-in, and outside access must be on (Domain). |
Satellites, Shuttles and Starships
| Problem |
Try |
| A device shows offline |
Is it on and on the network? Its Log is under More in the Shuttlebay. On a Pi: journalctl --user -u starfarer-satellite -f. |
| Starbase moved to a new address |
On the device: satellite --hub https://<address>:<port>. |
| No sound, or the wrong mic |
satellite --devices, then pick them in the Shuttlebay (Sound) or with --mic / --speaker; satellite --test checks them on their own. |
| It won't pair |
Devices pair only from home, never through the outside address; check the six-digit code matches in the Shuttlebay. |
| It treats you as a Guest |
Teach the AI your voice (Ready Room → Your AIs → Voice), or make the device yours in the Shuttlebay. |
| Clicking a video on a shared Shuttle does nothing |
On a shared screen, say its number ("number 3"): clicks are for your own devices. |
| A Starship's hands do nothing |
Let the AI use this PC must be on in that PC's tray menu; the hands are for its owner only, and away from home only on the Starship itself. Starships |
| Its version is behind |
Shuttlebay → Update (or Update all); on the device itself, satellite --update. |
Voice
| Problem |
Try |
| The AI doesn't react to its name |
Is Listening (the ear) on? Are the wake words downloaded (Engineering → Starbase → Voice)? "Computer" needs "Hey" first. Raise the sensitivity. |
| Devices wake by themselves |
Lower the sensitivity in Engineering → Starbase → Voice. |
| The AI cuts itself off |
Its own voice from the speakers counts as talking over it: turn Talk over the AI to stop it off in Ready Room → Your AIs → Voice, or use headphones. |
| It mishears a word |
Speech-to-text isn't perfect: spelling it out helps. |
| No voice |
Engineering → Starbase → Voice shows what's missing; Download what's missing gets it. |
| It cuts you off mid-sentence |
Raise Pause that means they're done in Engineering → Starbase → Voice. |
The AI's answers
| Problem |
Try |
| Too long, too chatty, too many jokes |
Tell it, or set it in Ready Room → Your AIs → Rapport. |
| Says your name too much |
Rapport: one step lower on how often it uses your name. |
| Its language isn't how you want it |
Rapport → language; the Captain may have set a language cap for you (Crew). |
| It says it couldn't find something it looked up |
The AI checks names and numbers against what it found and won't make them up: ask for the links. |
| "The … model won't fit on the graphics card right now" |
Another app (a game, another AI app) holds graphics memory: close it. Models |
| It won't use a tool |
Is the tool On (Tools), and is it given to that person in Clearance? |
| It asks for your OK every time |
That's the tool's level: the Captain can set it to Look if it's safe to just happen. |
| A persona "isn't installed yet" |
Engineering → Neural Net → Models → Build all. |
| Problem |
Try |
| "Not connected" |
The reason is on its card: a wrong address, a stopped program, a refused token. Fix it and press Reconnect. |
| A refused token |
Make a new one (Home Assistant: your profile → Security → long-lived access tokens) and enter it again. |
| A program server won't start |
The program must be installed on the Starbase PC (for npx, Node.js; for uvx, uv). The card shows its last error. |
Still stuck? Ask the Captain from the Ready Room (Problem), or, for a bug in Starfarer itself, see
Contributing.