On this page

Troubleshooting

An app shows as not responding

When Starboard cannot reach one of your apps, its card says Not responding. Either the app has stopped, or Starboard has the wrong address or API key for it. Find what the app's details say on the chart, then follow its numbered answer.

Find your answer
Flow chart: An app's card says Not responding. The same chart is written out in words after it.Cannot reach the appRefused the API keyAnswered with an errorNoYesAn app's card says NotrespondingOpen the app's detailsSelect its name on AppsWhat do the detailssay?Does the app open inyour browser?Start the app again1Check the addressStarboard uses2Copy the API key again3Read the app's ownmessages4
The chart in words

Start: An app's card says Not responding

Find what went wrong

On Apps, select the app's name on its card to open its details. They say what went wrong, such as "Cannot reach Jellyfin" or "Jellyfin refused the API key".

1 Start the app again

Open the app itself in your browser. If it does not open, the app has stopped. Start it again, then select Check again in the app's details.

2 Check the address Starboard uses

  1. If the app opens in your browser, select Edit app in its details. The app's Edit panel opens in Manage apps.
  2. Check Address Starboard uses. Starboard uses your server's own network, so an app on the same server is at http://127.0.0.1 and the app's port, such as http://127.0.0.1:8096 for Jellyfin.
  3. Select Test connection. Starboard shows Connected and how quickly the app answered, or Cannot connect and the reason.
  4. When the test says Connected, select Save app. For Sonarr, Radarr, Lidarr and Readarr, from an existing set-up, select Save and continue, then Save adding options.

3 Copy the API key again

  1. Select Edit app in the app's details.
  2. Check API key: copy it again from the app and paste it in. Read Find an app's API key.
  3. Select Test connection, and when it says Connected, select Save app.

4 Read the app's own messages

When the details say the app answered with error and a number, the app is running but had a problem. Open the app and read its own messages.

Things to note

  • Address Starboard uses can differ from the address you open in your browser. The one for your browser is Address to open in your browser.
  • A Docker container name, such as http://jellyfin:8096, only works between containers that share a Docker network. Starboard does not join one, so use 127.0.0.1 and the port the app publishes.
  • The port is the one the app publishes on the server, which is not always the app's usual port. This command, run on the server, lists each container and its ports. The port is the number before ->:
docker ps
  • An app on another computer uses that computer's address, such as http://192.168.1.21:8096.
  • A background service with no address can follow another app's status instead. Read Add a background service.

If it does not work

  • "Cannot reach" the app: the address or port is wrong, or the app is not running. Check both again.
  • "refused the API key": the key is wrong or was changed in the app. Copy it again.
  • "answered with error" and a number: the app is running but had a problem. Open the app and read its own messages.
  • If none of this helps, activate detailed logging and report the problem. Read Report a problem.

Find out more

This page on GitHub, where the help is written.