On this page

Troubleshooting

A plug-in will not add

When Starboard will not add a plug-in from the collection, the message on the Catalogue page says why. Find it here.

Find your answer
Flow chart: A plug-in will not add. The same chart is written out in words after it.It needs a newerplug-in APINo access to DockerhereThis plug-in cannot beaddedThe file changed sincethe catalogue listed itA plug-in will notaddWhat doesStarboard say?Update Starboard1Give Starboard accessto Docker2Read the test results3Try again tomorrow4
The chart in words

Start: A plug-in will not add

1 Update Starboard

Every plug-in here needs plug-in API 1.14, in Starboard 0.18.0 or later, and Library clean-up needs plug-in API 1.15, in Starboard 0.19.0 or later. An older Starboard is offered each plug-in's version before, from the catalogue, except Library clean-up, which has no earlier version. Read Update Starboard.

2 Give Starboard access to Docker

Plug-ins that run containers need it. Styles does not. Read Change what Starboard can access.

3 Read the test results

Starboard tests every plug-in before it is added. The results under the message say what is wrong and how to fix it. Tell its maker, at the plug-ins' issues on GitHub.

4 Try again tomorrow

The catalogue and the file do not match, so Starboard did not use it. Starboard reads the catalogue at most once a day: try again the next day.

Find out more

This page on GitHub, where the help is written.