No Moonraker connection

General Discussion
1

Basic Information:

Printer Model: ender 3 pro
MCU / Printerboard:
Host / SBC
moonraker.log (61.6 KB)

Moonraker updated, performed a print after the update but now Fluidd won’t connect to moonraker. I haven’t changed any other settings or command prompts

2

See K1C unable to connect to moonraker after update - #2 by Sineos

3

These Creality machines do not update correctly when a Moonraker dependency changes. Yesterday I pushed a change that replaces an unmaintained library (dbus-next) with a maintained fork (dbus-fast). On normal machines the new dependency is installed during the update. It appears that Creality machines do not install Moonraker in a proper virtualenv with pip installed, thus the failure.

4

Thanks @Arksine. Yes, it looks like a dependencies / installation problem.
This machine seems an Ender, so I was more referring to:

image
image609×177 4.3 KB

to get an idea what is actually happening during installation. Python version according to the log is 3.8.2, which should be compatible with the recent changes.

@LDD is this a Sonic Pad?

5

I’m guessing its either a Sonic Pad or the Klipper Edition of the Ender 3. From moonraker.log I can see its a MIPS processor running Creality’s custom linux build. Unfortunately the install script won’t work for it. Someone created an issue with a solution.

Apparently there is also a repo with helper scripts for Creality devices, but I don’t have a link.

6

Thanks for the replies, its a Nebula Pad. Honestly, i wish I had never got it… but I’m on the journey now… do you have any advise on how to roll back the update?