OctoDash: v2.2.0 update problems (LC_ALL: cannot change local | Stuck at initialization)

Describe the bug Trying to update via the UI results in a failure with the error Can't install update! with the warning /bin/bash:warning: setlocale: LC_ALL: cannot change locale (en-GB)

To Reproduce Steps to reproduce the behavior:

  1. Click update

Expected behavior Should update

General Information:

  • Raspberry Pi 4b -OctoPi
  • OctoDash Version 2.1.2

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (5 by maintainers)

Most upvoted comments

Followed the same answer as @NovaViper and once OctoDash rebooted, everything worked.

@csprocket777 by following the links posted here and checking whether your file look alright. If you don’t feel like this, the manual update is still an option though.

@ all Thanks for posting your tips here for other users! I’m going to keep this issue open and pinned for a week or two 😃. Feel free to post further findings if you have any!

I can confirm this fix. After upgrade, when stuck on initialization screen, go into OctoPrint -> settings -> API, and make sure the Allow CORS checkbox is checked. Then reboot.

I had to follow this answer in order to get it working: https://raspberrypi.stackexchange.com/a/81765. For some reason the first answer didn’t work for me, kept throwing this error despite me setting it to en_US.UTF-8

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
*** update-locale: Error: invalid locale settings:  LANG=en_GB.UTF-8

But once I followed the answer I linked, it allowed me to update OctoDash

I had my local set, but I redid it to what was in the forum post on https://raspberrypi.stackexchange.com/questions/43550/unable-to-reconfigure-locale-in-raspberry-pi and on restart that finally fixed the error. No clue why the en-GB that I already had uncommented wasn’t working. But, doing the locale-gen and update-locale seems to have resolved it

Correct. This is what I’m seeing. image