Network and HTTPS¶
Engineering → Starbase → Network is where Starbase listens.
| Setting | |
|---|---|
| Who can connect | Only this computer, or Anything on my home network (Satellites, Shuttles, Starships, your phone) |
| Port | 3010 to start with |
| HTTPS | Automatic (on whenever other devices can connect), Always on, or Off (not recommended on a network) |
| Ollama address | where the models run: http://127.0.0.1:11434 to start with |
| Share the GPU | only unload models Starbase loaded itself (keeps other AI apps, games and ComfyUI safe) |
A new port or HTTPS needs Restart Starbase (top right).
HTTPS and the certificate¶
With other devices allowed, Starbase serves HTTPS with its own certificate authority, made and renewed on the Starbase PC. Browsers need HTTPS for the microphone, and it keeps passwords off the network in the clear.
Each phone or computer trusts Starbase's certificate once, or its browser warns every time: Ready Room → You → Security → Trust Starbase on your devices has the download and the steps for Windows, a Mac, iPhone and iPad, and Android. Satellites, Shuttles and Starships check the certificate's fingerprint when they pair.
Windows Firewall¶
On Windows, run allow-network.bat once (it asks for administrator rights): it adds a rule for Starbase's port on
home (Private) networks only. If Windows has your network set to Public, the rule doesn't apply: set it to Private.
Ollama¶
Keep Ollama on the Starbase PC only (OLLAMA_HOST=127.0.0.1, its default). It has no password, so Starbase warns the
Captain if it answers on the home network, or if the Ollama address points at another machine.
From outside the home: Domain.