# Octopi won't connect with new Klipper install **URL:** \ **Category:** General Discussion\ **Created:** [October 12, 2024, 9:49pm UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361 "2024-10-12T21:49:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Valdhor](https://avatars.discourse-cdn.com/v4/letter/v/ebca7d/32.png) [@Valdhor](https://klipper.discourse.group/u/Valdhor)\ **Post date:** [October 12, 2024, 9:49pm UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361/1 "2024-10-12T21:49:49Z")
### Basic Information: Printer Model: Creality Ender-5 S1 MCU / Printerboard: STM32F401 Host / SBC :Raspberry Pi 4B 8GB 64bit Raspbian Bullseye klippy.log: [klippy.log](https://klipper.discourse.group/uploads/short-url/5CyjAwgsrUJwLhe2WX0xfOjcflN.log) (15.0 KB) _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** _ ### Describe your issue: I have been using Octopi for months connected to my Ender-5 S1 and decided I would install Klipper. I am following the instructions at [OctoPrint for Klipper - Klipper documentation](http://www.klipper3d.org/OctoPrint.html). I had issues with using “~/printer\_data/comms/klippy.sock” (The new “Printer” would not appear in the drop down menu to select) but fixed those by using “/home/pi/printer\_data/comms/klippy.sock” and then modifying the permissions of the directories (ie. 777). Now I have the “Serial port” showing up in the Connection dropdown menu (And selected) in the top left section of the Octopi interface. The instructions say to “click Connect” but when I do thgat I get the following log from OctoPi: ```auto Changing monitoring state from "Offline" to "Detecting serial connection" Performing autodetection with 7 port/baudrate candidates: /home/pi/printer_data/comms/klippy.sock@115200, /home/pi/printer_data/comms/klippy.sock@250000, /home/pi/printer_data/comms/klippy.sock@230400, /home/pi/printer_data/comms/klippy.sock@57600, /home/pi/printer_data/comms/klippy.sock@38400, /home/pi/printer_data/comms/klippy.sock@19200, /home/pi/printer_data/comms/klippy.sock@9600 Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 115200 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 115200 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 115200, skipping Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 250000 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 250000 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 250000, skipping Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 230400 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 230400 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 230400, skipping Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 57600 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 57600 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 57600, skipping Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 38400 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 38400 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 38400, skipping Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 19200 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 19200 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 19200, skipping Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 9600 Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 9600 Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 9600, skipping Changing monitoring state from "Detecting serial connection" to "Error" Changing monitoring state from "Error" to "Offline after error" ``` This is the permissions of the files: ```auto pi@octopi:~/printer_data/comms $ ls -al total 8 drwxrwxrwx 2 pi pi 4096 Oct 12 17:25 . drwxrwxrwx 10 pi pi 4096 Sep 29 08:44 .. lrwxrwxrwx 1 pi pi 10 Oct 12 17:25 klippy.serial -> /dev/pts/1 srwxrwxrwx 1 pi pi 0 Oct 12 17:25 klippy.sock ``` Here is the OS info: ```auto pi@octopi:~/printer_data/comms $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" ``` I haven’t even got to the point of flashing the printer. Any help most appreciated. ---
**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:** [October 13, 2024, 3:14am UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361/2 "2024-10-13T03:14:12Z")
Hello @Valdhor ! Try one of these: ```auto /home/pi/printer_data/comms/klippy.serial /tmp/printer ``` ---
**Author:** ![Valdhor](https://avatars.discourse-cdn.com/v4/letter/v/ebca7d/32.png) [@Valdhor](https://klipper.discourse.group/u/Valdhor)\ **Post date:** [October 13, 2024, 4:01am UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361/3 "2024-10-13T04:01:20Z")
Can you explain why? From what I can ascertain /tmp/printer was the old way of doing it. Klippy.sock is the socket connection whilst klippy.serial is the virtual serial port. ---
**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:** [October 13, 2024, 11:51am UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361/4 "2024-10-13T11:51:20Z")
> [@Valdhor](#): > > From what I can ascertain /tmp/printer was the old way of doing it. Have you Moonraker installed? Its only then. > [@Valdhor](#): > > klippy.serial is the virtual serial port. to connect to OctoPrint Have you even tried to do ? ---
**Author:** ![Valdhor](https://avatars.discourse-cdn.com/v4/letter/v/ebca7d/32.png) [@Valdhor](https://klipper.discourse.group/u/Valdhor)\ **Post date:** [October 13, 2024, 3:16pm UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361/5 "2024-10-13T15:16:51Z")
I don’t have anything other than Octoprint installed. With the issues I had getting the port “/home/pi/printer\_data/comms/klippy.sock” to even show up in the menu’s I was loath to modify it. I added port “/home/pi/printer\_data/comms/klippy.serial” and it connected OK. Thank you. Now onto flashing the printer. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [November 13, 2024, 1:17am UTC](https://klipper.discourse.group/t/octopi-wont-connect-with-new-klipper-install/19361/6 "2024-11-13T01:17:11Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.