This was the first result that popped up when I googled “Fluidd shutdown due to webhooks request” so wanted to add that restarting both my printer & raspberry pi fixed the issue for me!
This just got me too. I have to say, the text posted to screen after I hit the estop button is nonsensical. Yeah, I made a mistake. But man, this shouldn’t be a google. This should communicate, “You hit the estop and we shut down, you’re welcome” instead of anything about webhooks.
You need to differentiate between the webinterfaces (Mainsail, fluidd, KlipperScreen etc) and Klipper itself.
- You hit a button in the webinterfaces
- Klipper is telling you what kind of command it has received and why continuing in the given condition, i.e. emergency stopped, is not possible
Essentially your request would need to be fulfilled by the webinterfaces with a popup “I have killed the print at your request. No need to thank me”
2 Likes
so i’m having the exact same message and it only happens when I try to heat up the bed, any idea why? Or how to fix it?
Also is there a way to bi pass the wifi settings so that it can connect to my wifi even though it has a apostrophe in the name? And I can’t use wired.
I have the same issue here, also with a Sonic pad. A file which should take a few days to print, where the first day and night everything went fine. But since yesterday it keeps throwing this error, with variable in-between times, from 30 secs (!) to 15 minutes. UP till now, I can Restart the connection with the printer, and then Resume the printing process. But his way, it could take a year to finish this print…
The out-of-range message you see should not be happening here, because already the first layers has the maximum size (X-Y)of the print, and these sizes are well below the max of he printer (an Ender 5plus).
Looking at the posts here, I stopped the browser window on my desktop (running Firefox on openSuse Tumbleweed) and on my phone. But that did not make any difference. So it is now only the Sonic Pad connected to the printer…
Would be very nice if this could be solved…
The SonicPad is not something we are supporting here since they:
- Use modified components WRT Klipper, Moonraker etc
- Do not comply with the GPL license of Klipper
So if the Sonic Pad is causing this kind of issue, then the best course of actions would be contacting Creality for a fix.
What you could do (I do not know if even possible on the Sonic Pad) is setting Moonraker on debug to see where the Shutdown request is actually coming from.
1 Like
OK, thanks for your quick and clear reply. I have already contacted the firm I bought this (both printer and sonic pad) from, I’ll point them to what is discussed here. Thanks again!
regards, jehojakim
Following up with the solution to my problem even though it involves a Sonic Pad. (Reminder here that I was only using the Sonic Pad and printing from a USB stick inserted in the pad; no remote connection via browser).
One or both of the following fixed my problem however, given the seriousness of the issue and the fact that it was my only printer, I did not further explore which was the fix. I was just happy to be printing again.
- Made sure I had latest firmware for the Sonic Pad.
- Stopped using Cura.
- Un-installed Creality slicer, then installed the most recent version from the Creality website.
- Used only newly sliced files from updated Creality slicer and deleted any saved gcode files from the usb stick (even though they had successfully worked prior to the error/issue).
I have not since tried Cura again. I did however buy a new printer that actually provides good customer service in case something catastrophic happens. I’ll no longer buy Creality products going forward. **Note I see from recent post that the Sonic Pad doesn’t run an official Klipper version so I realize now that this may be a Creality Sonic Pad issue specifically, that I experienced.
@Sineos This was good to know. Thank you for informing us. Had no idea.