markwal / OctoPrint-PolarCloud

OctoPrint plugin that connects OctoPrint to the Polar3D cloud. You easily monitor your printer from outside your LAN without arcane setup of port forwarding, etc. Plus, take advantage of the rapidly evolving Polar Cloud capabilities and UI.
GNU Affero General Public License v3.0
15 stars 8 forks source link

Plugin doesn't install after saying it installed successfully #43

Closed skint007 closed 3 years ago

skint007 commented 6 years ago

I've been trying to install the plugin multiple and haven't been successful. It says it installed, but I noticed when its finished and asks to restart it says "Installed Unknown" instead of Polar Cloud.

Here is what it looks like: https://www.dropbox.com/s/qnmrfgczchlfckr/Install_Polar3d.png?dl=0

AbuKareem commented 6 years ago

I'm having the exact same problem screenshot 14

AbuKareem commented 6 years ago

Update

i followed these commands from issue https://github.com/markwal/OctoPrint-PolarCloud/issues/38 source ~/oprint/bin/activate pip uninstall cryptography pip uninstall cffi pip uninstall Pillow pip install cffi=1.11.5 pip install cryptography==2.2.2 pip install Pillow

now the install shows the plugin name but it is still not showing in the plugins menu and when searching in plugins manager it shows it is not installed and gives the option to install

screenshot 15

AbuKareem commented 6 years ago

Update #2

after the first installation reverted (cryptography) to 2.2.2 and trying to install the plugin again (because it's not showing) the message after installation displayed the name as unknown so perhaps the issue is with the cryptography version that the plugin is using?

stefanuc111 commented 5 years ago

I've the same problem, with octoprint installed in the orange pi lite

AndrewRees commented 5 years ago

I am experiencing the same problem on OctoPrint Version 1.3.10 / OctoPi Version 0.14.0.

markhurlburt commented 5 years ago

I'm running into this as well!

NovaViper commented 5 years ago

Same issue, happened on OctoPrint 1.3.0 and 1.3.10

vmorrisPolar commented 3 years ago

This issue should have been fixed in subsequent releases.