Monraker can't connect to klipper on fresh install

General Discussion
1

Basic Information:

Printer Model: voron trident
MCU / Printerboard: fysec spider 2.3
Host / SBC Opi 3B with Ubuntu Focal
klippy.log: Unavalible ( see code block)

{"error": {"code": 404, "message": "Not Found", "traceback": "Traceback (most recent call last):\n\n  File \"/home/orangepi/moonraker-env/lib/python3.8/site-packages/tornado/web.py\", line 1790, in _execute\n    result = await result\n\n  File \"/home/orangepi/moonraker/moonraker/components/application.py\", line 797, in get\n    self.absolute_path = self.validate_absolute_path(\n\n  File \"/home/orangepi/moonraker-env/lib/python3.8/site-packages/tornado/web.py\", line 2900, in validate_absolute_path\n    raise HTTPError(404)\n\ntornado.web.HTTPError: HTTP 404: Not Found\n"}}

Describe your issue:

I did a fresh install of klipper after it wouldn’t boot into the OS, straight into Kailco as that’s what I use on this machine. Upon entering mainsail however moonraker didn’t connect to klipper.

I checked the systemd service and it showed it as running but with this output

â—Ź klipper.service - Klipper 3D Printer Firmware SV1
     Loaded: loaded (/etc/systemd/system/klipper.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Fri 2025-03-21 11:57:38 UTC; 8s ago
       Docs: https://www.klipper3d.org/
    Process: 7135 ExecStart=/home/orangepi/klippy-env/bin/python $KLIPPER_ARGS (code=exited, status=1/FAILURE)
   Main PID: 7135 (code=exited, status=1/FAILURE)

mind you the first install showed klipper as running, but still wasn’t connecting, but the 2nd and third time it’s doing this. the klipper.sock file also isn’t there for some reason and using /tmp/klippy_uds didn’t seem to work either

attached moonraker log just in case:
moonraker (3).log (83.5 KB)

2

@nathan22211 ,

Firstly, we can only really help with vanilla Klipper. Here’s what I recommend:

  1. Switching to vanilla Klipper
  2. Upload a klippy.log from ~/printer_data/logs/klippy.log. You can also use KIAUH for this step.
1 Like
3

In the first place, it seems Klipper is not running correctly. You should debug this first. However, Kalico is something we do not support here.

4

I just swapped over to mainline with the same results. I’m still trying to debug why klipper isn’t running

5

ok well KIAUH shows I’m using mainline but Mainsail still shows Kailco so something’s funky for sure

6

That code block is empty. Can you please use KIAUH to get the klippy.log file?

7

can’t because klipper won’t start and mainsail can’t find the klippy.log. that’s what I’ve been trying to debug

8

@nathan22211 ,

You DON’T need Mainsail to get the klippy.log. The klippy.log is located at ~/printer_data/logs/klippy.log. You can also use KIAUH to retrieve the log.

9

ok, apparently using KIAUH V6 helped, I’ll mark this as the solution so search engines pick it up.