On this page
Troubleshooting
Starboard does not open
If your browser cannot open Starboard, find what happens on the chart, then follow its numbered answer. Most of the time Starboard is not running, the address is wrong, or Starboard is set to open on the server only.
The chart in words
Start: Starboard does not open in the browser
- Then: Is Starboard running? (docker compose ps says Up)
- No, or you do not know: 1. Start Starboard
- Still does not open: 5. Read Starboard's own messages
- Yes: Does it open on the server, at 127.0.0.1:8095?
- No: 2. Check the address and port
- Still does not open: go to 5. Read Starboard's own messages
- Yes, but not on a phone: What does the phone or other computer show?
- Only the computer it runs on is allowed: 3. Let other devices in
- Nothing loads: 4. Open the port in the firewall
- Still does not open: go to 5. Read Starboard's own messages
- No: 2. Check the address and port
- No, or you do not know: 1. Start Starboard
Before you begin
- You can type commands on the server, at its keyboard or over SSH (secure shell). Read The terminal: entering commands and Connect to your server from another computer.
1 Start Starboard
- Check that Starboard is running. On the server, go to the Starboard folder:
cd ~/starboard
Then list its container:
docker compose ps
Starboard is running if the starboard line says "Up". If you installed from the ready-made image, use
this command instead:
docker compose -f compose.image.yaml ps
- If it is not running, start it:
docker compose up -d
With the ready-made image, use this command instead:
docker compose -f compose.image.yaml up -d
2 Check the address and port
- Check the address. It is the server's address, a colon and the port, such as
http://192.168.1.20:8095. It starts withhttp, nothttps, unless you set up a reverse proxy. On the server itself, usehttp://127.0.0.1:8095. - Check the port. Starboard uses port 8095 unless you chose another when you installed. The
.envfile in the Starboard folder shows it on the lineSTARBOARD_PORT. - Try on the server itself, at
http://127.0.0.1:8095. If it opens there but not on a phone, carry on with Let other devices in.
3 Let other devices in
On the server, go to Settings, then Security, and check that Phones and other computers on your home network is active. If the server has no monitor, read Choose who can open Starboard to reach the setting from your own computer.
4 Open the port in the firewall
A firewall is a program that blocks connections the server has not allowed. On Ubuntu, Debian and Linux Mint, this command shows whether ufw, a common firewall, is active:
sudo ufw status
If it says "Status: active" and port 8095 is not listed, allow it:
sudo ufw allow 8095/tcp
5 Read Starboard's own messages
If it still does not open, read Starboard's own messages:
docker compose logs starboard
With the ready-made image, use this command instead:
docker logs starboard
The last lines usually say what went wrong.
Things to note
- The phone or computer must be on the same home network as the server. Mobile data and guest Wi-Fi networks cannot reach it.
- If the page says "This dashboard only accepts connections from the computer it runs on", home network access is inactive. Follow Let other devices in on the server.
- If the page says "Starboard does not answer to the name", you used a name Starboard does not know. Use the
server's address, such as
http://192.168.1.20:8095, or read Put Starboard behind a reverse proxy. - If you installed with the installer's
--nativeoption, Starboard runs without Docker. Instead of Start Starboard, check it with this command:
systemctl --user status starboard
If it does not work
Copy the last lines of docker compose logs starboard and open an issue, as described in
Read the log and report a problem. Remove anything private before you post it.
Find out more
This page on GitHub, where the help is written.