Failure to initialise after updating to OctoPi 0.18.0 & OctoPrint 1.8.3

[ruralaccent]

I updated my three Raspberry Pi4 octopi installations today to Octoprint 1.8.3.

On the two installations where OctoDash wasn't connected to the printer, it failed to pass the initialisation screen when the system was restarted.

On the installation where OctoDash was up and running and had been connected to the printer, it was displayed 'port is dead', and when I rebooted that installation, it then got stuck on the initialisation screen like the other two.

Octoprint functions as per normal and I can print just fine via OctoPrint, but OctoDash is now broken and won't ever finish initialising.

I all cases I used the prompt in octoprint to update to the latest version.

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36 connectivity.connection_check: 1.1.1.1:53 connectivity.connection_ok: True connectivity.enabled: True connectivity.online: True connectivity.resolution_check: octoprint.org connectivity.resolution_ok: True env.hardware.cores: 4 env.hardware.freq: 1500.0 env.hardware.ram: 3960369152 env.os.bits: 32 env.os.id: linux env.os.platform: linux env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.2 env.plugins.pi_support.octopi_version: 0.17.0 env.plugins.pi_support.throttle_check_enabled: True env.plugins.pi_support.throttle_check_functional: True env.plugins.pi_support.throttle_state: 0x0 env.python.pip: 22.0.4 env.python.version: 3.7.3 env.python.virtualenv: True octoprint.last_safe_mode.date: unknown octoprint.last_safe_mode.reason: unknown octoprint.safe_mode: False octoprint.version: 1.8.3 printer.firmware: Prusa-Firmware 3.10.1 based on Marlin systeminfo.generated: 2022-09-21T19:46:37Z systeminfo.generator: zipapi

[ruralaccent]

Just to add, I am getting the same screen as shown in https://github.com/UnchartedBull/OctoDash/issues/3164, but for me it only began after upgrading all of my octoprint installations to 1.8.3

[Al3601]

same issue after upgrading from 0.180 to 1.8.3

[ruralaccent]

Following advice from Charlie over on the Octoprint forum, this issue relates to an API bug in 1.8.3 that prevents the global api working correctly. I fixed the issue by switching from a global api key to an application api key.

So, to resolve the issue (and future proof OctoDash as the global api is depreciated), follow these steps:

1. Set up an application api key for OctoDash in OctoPrint,

2. Update the OctoDash config file via SSH with that new application api key,

   Open the config file using this command: sudo nano .config/octodash/config.json
   (then ctl-X to exit, selecting Y to save the changes)

3. Reboot the system and OctoDash should initialise just fine.

[cp2004]

The global API key usage should be fixed in the next bugfix release (1.8.4 I think), however for anyone else that finds this issue, now is a good time to realise that eventually the global API key will go away entirely and to switch to using an application key, or the API key specific to your user.

[lluisd]

same issue here after updating octoprint from 1.8.0 to 1.8.3. Screen shows always initializing... with the CORS API message.

[jneilliii]

Probably the same problem, you're using a global api key and not an application key in your OctoDash settings? You can edit that using the command nano /home/pi/.config/octodash/config.json via SSH.

[lluisd]

Probably the same problem, you're using a global api key and not an application key in your OctoDash settings? You can edit that using the command nano /home/pi/.config/octodash/config.json via SSH.

yes it was easy to solve it by doing that, but I didn't expect a breaking change by jumping to 1.8.3.

[cp2004]

It wasn't a deliberate breaking change, and is now fixed with 1.8.4.

The global API key will be going away so it's a good reminder to not use it 😉

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[army11b1980]

I just did a fresh install and now I'm stuck on the welcome screen. It's like the touch is not responding anymore. I will try to do this solution.