Upgraded to 1.8.3 and logins stopped working

Get Help
12

pi@raspberrypi:~/OctoPrint source venv/bin/activate (venv) pi@raspberrypi:~/OctoPrint pip -V
pip 22.2.2 from /home/pi/OctoPrint/venv/lib/python3.7/site-packages/pip (python 3.7)
(venv) pi@raspberrypi:~/OctoPrint $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="RaspbianForums - Raspbian"
BUG_REPORT_URL="RaspbianBugs - Raspbian"

uname -a

Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
Hardware: Raspberry pi 3b, 1GB ram

And second one is:

jonni@pine64:~/OctoPrint$ source bin/activate
(OctoPrint) jonni@pine64:~/OctoPrint$ pip -V
pip 22.0.2 from /home/jonni/OctoPrint/lib/python3.10/site-packages/pip (python 3.10)
(OctoPrint) jonni@pine64:~/OctoPrint$ cat /etc/os-release
PRETTY_NAME="Armbian 22.05.3 Jammy"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="Data privacy | Ubuntu"
UBUNTU_CODENAME=jammy
(OctoPrint) jonni@pine64:~/OctoPrint$ uname -a
Linux pine64 5.15.48-sunxi64 #22.05.3 SMP Wed Jun 22 07:33:24 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
Hardware: pine64, 1GB RAM

13

same with me.

(octoprint2) root@Ph-3D-Druck:~# pip -V
pip 22.1.1 from /home/octoprint/python_venvs/octoprint2/lib/python3.8/site-packages/pip (python 3.8)

(octoprint2) root@Ph-3D-Druck:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-poli cy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

14

Would a force reinstall fix it up maybe?

source venv/bin/activate
pip install --force-reinstall --no-cache-dir OctoPrint==1.8.3
15

No, don't work either. Same Issue.

16

Can somebody give me a hint how to rollback to 1.8.2. on my ubuntu installation ? I did

source /home/octoprint/python_venvs/octoprint2/bin/activate
pip install https://github.com/foosel/OctoPrint/archive/1.8.2.zip

but afterwards the service do not start

pkg_resources.DistributionNotFound: The 'OctoPrint==1.8.2' distribution was not found and is required by the application

17

Rollback instructions are here: How do I roll back from 1.8.3+ to a version prior without losing the ability to login?

1 Like
18

With what guide did you install OctoPrint on Ubuntu?

I used this one and there have been no update issues.

19

I followed that one:

but one of my 3 octoprint instances are broken now...

20

If you're using virtual environments (venv), are you sure you installed argon2_cffi into the same virtual environment? What happens if you run Octoprint server via the CLI (octoprint serve -v) instead of the daemon?

21

Are you using a reverse proxy in front of Octoprint?

I have HAProxy in front of my Octoprint instance and had to add

        option forwardfor
        http-request set-header X-Real-IP %[src]
        http-request set-header X-Forwarded-Proto https if { ssl_fc }

in order to log in.

1 Like
22

Hello,

argon2_cffi pip binary is ducked. just do a:
pip install --force-reinstall --no-binary :all: argon2_cffi

23

No luck running that force no-binary all command on raspberry....

  Collecting importlib-metadata
    Downloading importlib_metadata-4.12.0.tar.gz (48 kB)
       ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 48.2/48.2 kB 1.2 MB/s eta 0:00:00
    Installing build dependencies: started
    Installing build dependencies: still running...
    Installing build dependencies: still running...
    Installing build dependencies: finished with status 'error'
    error: subprocess-exited-with-error
24

Managed to fix it on raspberry by installing with following command in venv:

pip install --force-reinstall --no-binary=argon2-cffi-bindings argon2_cffi

And by adding haproxy forwardfor rules also the remote access now works.

And same fix also worked for my pine64 venv env.

25

This did not work for me on 1.8.4

26

I am DIW also since 1.8.3 or 4
no password or name is valid. 3 instances on 2 rock64's are now DIW, Cant''t login to the web page at localhost:5000, or from another machine at rock64:5000 both of which worked with 1.8.2.

And as an additional seemingly unrelated, clue cura 5.2.0 beta for linux is crashing at the file save after a simple .stl is sliced. AND restoring to 5.1.0 which has been working well, but now 5.1.0 is also locking
up, responding only to a ctl+c from the terminal that started it. The save to disk bar changes color
slightly when clicked on after the slice, and its DIW until the terminal that started it gets a ctl+c.

So my theory is that some other library it uses, has been updated, and broke both cura and octoprint in the last 3-5 days.
cura is normally ran on this machine, and the gcode is then saved over my local network directly to the "watched" directory on which ever printer I'm feeding.

27

unforch, argon2_cffi is not know to armbian 11's apt. And it says this topic has been solved, but I don't
see the solution?

28

turns out to be a pip responsibility, put that in my install script and now I can login again. I wonder if that's the same problem with cura? Back to the drawing board I think.

29

maybe you forgot to update haproxy settings too, as you only pasted pip on your reply. Or maybe you should try to downgrade to 1.8.3 and apply fix before going to 1.8.4. Or paste the error message on pip install. But that pip force reinstall has worked for others (make sure that you have activated venv before runnin pip). Or paste the error message when you use command line to set the password (octoprint user password admin).

30

@WOWElectronics, Cura and OctoPrint are installed & run very differently, so they won't have a common problem or common solution unfortunately.

The solution to this topic is marked, the below post:

31

@rainisto

I started by doing this.

this is the link that appears on the Login Screen when we have problems. this is the first not been able to print stuff. I could not solve the issue yet.