Articles on: Connect & set up printers

Re-link a Klipper printer after deleting it or moving networks

Re-link a Klipper printer after deleting it or moving networks


A Klipper printer remembers which SimplyPrint printer it is linked to. Moonraker stores that link on the printer, and connects with it every time it starts. If the link points to a printer you deleted, or to an account you can't get into, Moonraker keeps using it and no new setup code appears. This guide shows how to get a new setup code and connect the printer again.


In this guide


Which case is yours

Your situation

What to do

You moved the printer to a new network, and it is still in your SimplyPrint account

Nothing to re-link. A new network doesn't change the stored link. If the printer stays offline, follow Why is my Klipper-powered printer offline?

The printer is still in your account, and you want to connect it again (new host, reinstalled software)

Connect it again

You deleted the printer in SimplyPrint, and no setup code appears

Clear the stored link

The printer is still linked to an old account you can't log in to

Clear the stored link. If you can't, see The printer is on an account you can't get into


Before anything else, check that [simplyprint] is in your moonraker.conf and that Moonraker is v0.8.0 or newer. Without it, no setup code ever appears: see Troubleshooting Klipper/Moonraker setup with SimplyPrint.


Connect a printer that is still in your account again

This keeps the printer's print history and settings in SimplyPrint.


  1. In SimplyPrint, open the printer's menu and click Delete printer.
  2. Click Remove Pi connection. Don't click Permanently delete.
  3. Restart Moonraker: use the power menu in Mainsail or Fluidd, or run sudo systemctl restart moonraker over SSH.


Check: a SimplyPrint Setup Request with a 4-character code appears under the notification bell in Mainsail or Fluidd, and the printer shows under Pending printers in SimplyPrint.


  1. Add the printer with the setup code. When SimplyPrint asks, choose Link to existing and pick the printer.


Check: the printer comes online under its old name, with its print history.


Why this works: removing the connection makes SimplyPrint forget the printer's old device key. The next time Moonraker connects with it, SimplyPrint sends the printer back to setup, and Moonraker clears its stored link and shows a new code.


Use this when the printer is gone from your account, or sits in an account you can't use. Moonraker keeps the link in its own database, in a part that Mainsail and Fluidd can't edit, so removing [simplyprint] from moonraker.conf doesn't clear it.


This needs SSH access to the computer that runs Klipper, and a temporary change to how Moonraker starts. The paths below are the standard ones; some manufacturers' systems put them elsewhere.


  1. Log in to the Klipper computer over SSH.
  2. Open ~/printer_data/systemd/moonraker.env. Add -g at the end of the MOONRAKER_ARGS line, inside the quotes, and save. This turns on Moonraker's debug tools, which can edit that part of the database.
  3. Run sudo systemctl restart moonraker.
  4. Run this command to delete the stored printer ID:

curl -X DELETE "http://localhost:7125/debug/database/item?namespace=simplyprint&key=printer_id"
(7125 is Moonraker's default port. Use yours if you changed it.)

  1. Open moonraker.env again, remove the -g you added, save, and run sudo systemctl restart moonraker once more.


Check: a SimplyPrint Setup Request with a 4-character code appears under the notification bell in Mainsail or Fluidd.


  1. Add the printer in SimplyPrint with the code. If the printer still exists in your account, choose Link to existing to keep its history.


The printer is on an account you can't get into

If you can't clear the link yourself, contact support. We look at each request individually, because releasing the printer removes it from someone else's account. Send the printer ID from moonraker.log or a screenshot of the printer's Mainsail or Fluidd page, so we can see you have the printer, and tell us how it came to be on that account (second-hand, a former employee or student, an old login).


ZMOD on Flashforge printers: moonraker.conf is read-only

On a Flashforge printer running ZMOD (Adventurer 5M, 5M Pro, AD5X, Creator 5 or Creator 5 Pro), you can't edit moonraker.conf. ZMOD reads your own Moonraker settings from a separate file:


  1. In Fluidd, go to Configuration and open the mod_data folder.
  2. Open user.moonraker.conf, add a line with [simplyprint], and save.
  3. Restart Moonraker.


Check: a SimplyPrint Setup Request with a 4-character code appears under the notification bell.


The steps in Clear the stored link on the printer don't work on ZMOD as written. ZMOD doesn't start Moonraker through systemd, so there is no moonraker.env to change and no systemctl to restart it with. If your ZMOD printer is still in your SimplyPrint account, use Connect a printer that is still in your account again instead: it needs no SSH. If it isn't, there is no way yet to clear the link on ZMOD yourself: see The printer is on an account you can't get into.


The SimplyPrint Client also connects these Flashforge printers on their own firmware, with nothing installed on the printer. See Connect your printers with the SimplyPrint Client.


Klipper stopped with "Timer too close"

MCU 'mcu' shutdown: Timer too close is a Klipper error, not a SimplyPrint one. Klipper stops the printer, and SimplyPrint shows the printer in an error state with that message, so the print ends.


Klipper's own explanation is that the computer running Klipper is often overloaded. To fix it:

  1. Check the Klipper computer for programs using a lot of CPU, heavy swap use, disk errors, overheating, or an unstable power supply.
  2. Fix what you find, then send FIRMWARE_RESTART from the console in Mainsail or Fluidd.


Check: Mainsail or Fluidd shows the printer as ready, and SimplyPrint shows it online again.


If it keeps happening during prints, see Print ended in "Printer error" for other reasons a printer stops a print.


Updated on: 27/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!