# Despite following the guide on the Klipper docs perfectly, it is unable to connect to my printer

**URL:** <https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868>\
**Category:** General Discussion\
**Created:** [February 24, 2023, 3:15pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868 "2023-02-24T15:15:36Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 24, 2023, 3:15pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/1 "2023-02-24T15:15:36Z")

</div>

### Basic Information:

Printer Model: First-gen Creality Ender 3  
 MCU / Printerboard: SKR Mini E3 v3.0  
 Klipper log is empty.

### Describe your issue:

I am trying to set up an Octoprint server with Octoklipper. However, when I click ‘connect’ in the OctoKlipper widget, it does literally nothing. No terminal output, no error, no popups, it is a dead button. Klipper’s status is on “Klipper: Standby” as well.

I used KIAUH to install Octoprint and Klipper. Then, I installed the OctoKlipper plugin through the plugin manager.

My steps for setting up Klipper as follows:

1. cd’d into the Klipper directory.
2. ran “make menuconfig” to enter the Klipper config menu.
3. Set the specs for my board as according to their [Github](https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/tree/master/firmware/V3.0/Klipper): STM32, STM32G0B1 (verified this is the right chip on my board), 8KiB, 8MHz, USB…
4. I quit and then copied the klipper.bin file to my sd card and renamed it to firmware.bin.
5. Flashed it to my board and verified it worked by checking for a CUR file.
6. Copied and pasted my board’s cfg data into the OctoKlipper editor (as well as created a printer.cfg file in the Klipper config directory with those values)
7. Ran “ls /dev/serial/by-id/\*”, obtained my serial port info, and input it into the editor under mcu.
8. Went into my Octoprint settings, added /tmp/printer to my serial ports. Set Serial Port to AUTO (since it would not let me select /tmp/printer), and set Cancel any ongoing prints in behaviour.

I actually did these steps twice. Once installing Klipper from KIAUH, and the second time doing it manually from the Github. Right now, I am getting no terminal output and cannot even send terminal commands. And Klipper is on standby.

Here is my config file for reference:

> <https://pastebin.com/fqNSLJ4f>

Is there some obscure step I am missing here or some way to get this working?

Edit:

Why is this being flagged as spam?

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [February 24, 2023, 3:47pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/2 "2023-02-24T15:47:09Z")

</div>

Hello @cray12399 !

Did you restart Klipper after editing the printer.cfg ?

![grafik](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/a/a600ff09f4ea2c0afac63295cde25728b7032270.png)

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 24, 2023, 3:58pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/3 "2023-02-24T15:58:46Z")

</div>

Yes, I have restarted Octoprint and Klipper countless times at this point. Also, despite klippy.log being empty (?), I was able to get logs by temporarily installing Fluidd and pulling the log there. Forum wont let me upload, so here is a pastebin:

> **[===== Config file =====\[mcu\]serial = /dev/serial/by-id/\[pri - Pastebin.com](https://pastebin.com/TU7UN2GR)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [February 24, 2023, 4:08pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/4 "2023-02-24T16:08:47Z")

</div>

Sorry, I can’t pastebin.

You can upload the file (not the contents) here.

![Upload](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/f/f4bca94c8dcd7674a4931461997a8435c81e5495.png)

---

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [February 24, 2023, 4:16pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/5 "2023-02-24T16:16:00Z")

</div>

> [@EddyMI3D](#):
>
> Sorry, I can’t pastebin.

You can! Just klick on the link cray12399 posted 😉

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 24, 2023, 4:17pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/6 "2023-02-24T16:17:35Z")

</div>

If you click the link, it should show the contents of the file.

I tried uploading it using the upload button, but it kept giving me an error.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [February 24, 2023, 4:19pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/7 "2023-02-24T16:19:48Z")

</div>

@cray12399: May I propose that you read the klippy.log and the error message and compare it with your configuration (which is also printed in the log).  
I dare to forecast that the error is pretty obvious.

Hint:

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/5/5831d321ff9e260addbb8e214966e6108c964e85.png)

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 24, 2023, 4:29pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/8 "2023-02-24T16:29:30Z")

</div>

My configuration file mcu section reads as:

[mcu]  
serial: /dev/serial/by-id/usb-Klipper\_stm32g0b1xx\_32003B000B504B5735313920-if00

Might be a Fluidd config specific error since I created that log in Fluidd because Octo couldn’t produce logs.

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [February 24, 2023, 4:32pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/9 "2023-02-24T16:32:46Z")

</div>

> [@cray12399](#):
>
> Octo couldn’t produce logs.

OctoPrint creates the systeminfo bundle.

But are you running on OctoPrint or Fluidd??

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [February 24, 2023, 4:35pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/10 "2023-02-24T16:35:07Z")

</div>

In the Klipper world, there is only one truth: The klippy.log  
From this you can get following information:

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/5/5c3d23961b2f6ea519503fb29636390cad04039e.png)

- `/home/pi/printer_data/config/printer.cfg` is your current relevant config file. Make sure you edit the right one
- `/home/pi/printer_data/logs/klippy.log` is the place of your log file

In addition you will find the complete configuration _as Klipper has parsed_ it and some detailed error messages as shown in the screenshot above.

Octoprint or Fluidd are just web-interfaces and do not change this system.

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 24, 2023, 4:35pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/11 "2023-02-24T16:35:22Z")

</div>

Oh okay, I didn’t know those were logs. My bad. I will try to link the Sysinfo Bundle here:

> **[octoprint-systeminfo-20230224113307.zip](https://drive.google.com/file/d/1xpW-D2tt7k_Fzjnk9f8ktmGe9Tgwn9l2/view?usp=sharing)**
>
> Google Drive file.

(Uploads still not working sorry, so here is a drive link to Sysinfo.)

I am running Octoprint, but I temporarily installed Fluidd to see if perhaps it was an Octoprint exclusive issue. Fluidd is also having issues.

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 24, 2023, 4:39pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/12 "2023-02-24T16:39:57Z")

</div>

Hmm I see. I just became familiarized with Klipper and Octoprint less than a week ago, so I am still wrapping my head around all of this.

So, the logs between the two are the same then. I wonder why it is trying to connect to `/dev/serial/by-id/<your-mcu-id>` then. I have verified that my `printer.cfg` file AND the OK editor both have the serial set as the value I received from `ls /dev/serial/by-id/*`

`printer.cfg` is also saved in `~/klipper/config` if that is the proper location.

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [February 24, 2023, 4:47pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/13 "2023-02-24T16:47:16Z")

</div>

> [@cray12399](#):
>
> `printer.cfg` is also saved in `~/klipper/config` if that is the proper location.

> [@Sineos](#):
>
> `/home/pi/printer_data/config/printer.cfg` is your current relevant config file. Make sure you edit the right one

Uhm, not really, right?

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [February 24, 2023, 4:57pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/14 "2023-02-24T16:57:49Z")

</div>

And please avoid pulling the plug of the Pi to restart it.  
This can lead to a corrupted file system on the Pi’s SD card.

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 25, 2023, 1:02am UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/15 "2023-02-25T01:02:46Z")

</div>

Alright, I edited the cfg one in printer\_data and it still has not fixed the issue. The klippy.log is also showing the same error as in your comment above.

Edit:

While the connect button still does nothing, it appears that there is an octoprint menu on my printer’s screen now. So, I guess that is some progress at least.

---

<div class="post-metadata">

**Author:** ![cray12399](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@cray12399](https://klipper.discourse.group/u/cray12399)\
**Post date:** [February 25, 2023, 3:21am UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/16 "2023-02-25T03:21:07Z")

</div>

I may have come across another clue as to what is going on! I was inspecting the connect button in my browser and it is producing this error:

`POST http://172.20.2.242:5000/api/connection [HTTP/1.1 400 BAD REQUEST 47ms]`

Network issue between my client PC and the Octoprint api when pressing the connect button?

---

<div class="post-metadata">

**Author:** ![cy0l](https://avatars.discourse-cdn.com/v4/letter/c/d26b3c/32.png) [@cy0l](https://klipper.discourse.group/u/cy0l)\
**Post date:** [December 3, 2023, 5:47pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/17 "2023-12-03T17:47:34Z")

</div>

@cray12399 did you end up solving trhe issue?  
I’ve goty a similar problem and this thread has been pretty similar to what I’ve been dealing with.

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [December 3, 2023, 6:01pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/18 "2023-12-03T18:01:54Z")

</div>

@cy0l

Don’t you think opening a new thread with data that can help solve a problem would be better than zombiefying a nine month old thread?

If if your problem seems to be pretty similar, the reason can be quite different.

---

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [December 3, 2023, 6:05pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/19 "2023-12-03T18:05:57Z")

</div>

> [@cy0l](#):
>
> @cray12399 did you end up solving trhe issue?

I would open a new thread.  
Attaching “klippy.log” is the most important task for you to fulfill!

Good luck, hcet14

Fill out

### Basic Information:

Printer Model:  
 MCU / Printerboard:  
 `klippy.log`

_Fill out above information and_ **_in all cases attach your_ `klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_  
_ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [December 3, 2023, 6:34pm UTC](https://klipper.discourse.group/t/despite-following-the-guide-on-the-klipper-docs-perfectly-it-is-unable-to-connect-to-my-printer/6868/20 "2023-12-03T18:34:22Z")

</div>


