Cannot connect to Mainraker

[ematt]

Printer Model

Voron 2.4 300

Extruder Type

Clockwork 2

Cooling Type

Stealthburner

I have a Voron 2.4. It has been running with no problems for sometime. I did an update and now get the error "Cannot connect to Moonraker". I can SSH in but cannot figure out what is wrong. I would really to fix this without starting over, I feel sure it is just a configuration issue.

I ran Kiauh and everything is at the latest version.

pi@mainsailos:~ $ service klipper status
● klipper.service - Klipper 3D Printer Firmware SV1
Loaded: loaded (/etc/systemd/system/klipper.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2026-03-22 13:16:12 CET; 32min ago
Docs: https://www.klipper3d.org/
Main PID: 540 (python)
Tasks: 13 (limit: 1933)
CPU: 19.751s
CGroup: /system.slice/klipper.service
└─540 /home/pi/klippy-env/bin/python /home/pi/klipper/klippy/klippy.py /home/pi/p>

Mar 22 13:16:12 mainsailos systemd[1]: Started Klipper 3D Printer Firmware SV1.

pi@mainsailos:~ $ service moonraker status
● moonraker.service - API Server for Klipper SV1
Loaded: loaded (/etc/systemd/system/moonraker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2026-03-22 13:49:14 CET; >
Process: 2515 ExecStart=/home/pi/moonraker-env/bin/python $MOONRAKER_ARGS (code=exited, st>
Main PID: 2515 (code=exited, status=1/FAILURE)
CPU: 510ms
lines 1-6/6 (END)

The klippy.log and moonraker.log are to big to attach. I can cut out sections if you tell what to look for.

Any help is appreciated.

Eric

 

[NoGuru]

Need logs or screen shots.

 

[ematt]

Need logs or screen shots.

Hello, Thank you very much for responding to my post.
I tried a bunch of things, read the Moonraker manual, read pretty much everthing I could. End result nothing worked for me.

Now I am at the nuculer option, start a fresh version of Pi and go from there. The good part is I got in and copied out all of my .cfg files before I nuked it.

Wish me luck.

Eric

 

[shiftingtech]

journalctl -u moonraker -r

might give you enough info to help us figure out what moonraker is angry about, without having to deal with an oversized log file.