Plugin installation: Unknown


What is the problem?

Whenever I install a plugin, I get a message saying "Install Unknown" with a restart button. After restarting, the plugin works correctly, but I can't uninstall plugins because it says it couldn't find the plugin.

What did you already try to solve it?

  1. Install and attempt to uninstall other plugins
  2. Restart OctoPrint
  3. Restart OctoPi
  4. Reflash SD card with OctoPi image

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)

  • OctoPrint 1.3.8, latest OctoPi release (downloaded today, May 5 2018)

  • Relevant line from octoprint.log:
    2018-05-05 21:23:50,605 - octoprint.plugins.pluginmanager - WARNING - The plugin was installed successfully, but couldn't be found afterwards to initialize properly during runtime. Please restart OctoPrint.

  • Plugin install log:

Installing plugin "Action Commands" from
/home/pi/oprint/bin/python2 -m pip install
Looking in indexes:,
Downloading (77kB)
Requirement already satisfied: OctoPrint in /home/pi/oprint/lib/python2.7/site-packages (from Action-Commands==0.1) (1.3.8)
Requirement already satisfied: pytz>=0a in /home/pi/oprint/lib/python2.7/site-packages (from Babel>=1.0->Flask-Babel<0.10,>=0.9->OctoPrint->Action-Commands==0.1) (2018.4)
Building wheels for collected packages: Action-Commands
Running bdist_wheel for Action-Commands: started
Running bdist_wheel for Action-Commands: finished with status 'done'
Stored in directory: /tmp/pip-ephem-wheel-cache-W0yK0i/wheels/85/79/c9/d8d12337ea9a8dd4a948dd18a13471f1e62ca60ffd0533a5b3
Successfully built Action-Commands
Installing collected packages: Action-Commands
Successfully installed Action-Commands-0.1

Update: Disabling plugins works correctly, but I'd still like to be able to actually uninstall them correctly.


Known issue with pip10 as it was bundled with OctoPi 0.15, sadly only noticed after stable release of OctoPi 0.15 (apparently not enough people were testing this, we need more testers).

OctoPrint 1.3.9 will contain a fix for this, as well OctoPi 0.15.1.

See also


Workaround until either is released is connecting to your OctoPi instance via SSH, then doing this:

~/oprint/bin/pip install pip==9.0.3
sudo service octoprint restart

This downgrades the pip installed into OctoPrint's virtual environment to a version that works. Then either reinstall the plugin via command line (pip uninstall ...) or - untested - force a reinstall through the plugin manager and then uninstall it through OctoPrint.


Oh, okay, thank you! As long as it's a known issue I'll just wait for the next release.

Is there a way to test OctoPi RCs without reflashing the SD card? Or does switching the release channel in settings affect OctoPi as well as OctoPrint?


Since OctoPi is the whole image sadly reflashing is currently the only option to test those. I have a bunch of extra SD cards for situations like that (also since OctoPrint pre-release tests involve update procedure tests from various OctoPi/OctoPrint version combinations).