# Resolved KIAUH Klipper Install Issue on Octopi 1.1.0 **URL:** \ **Category:** General Discussion\ **Created:** [May 11, 2025, 6:53am UTC](https://klipper.discourse.group/t/resolved-kiauh-klipper-install-issue-on-octopi-1-1-0/23379 "2025-05-11T06:53:20Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![pigaro](https://avatars.discourse-cdn.com/v4/letter/p/258eb7/32.png) [@pigaro](https://klipper.discourse.group/u/pigaro)\ **Post date:** [May 11, 2025, 6:53am UTC](https://klipper.discourse.group/t/resolved-kiauh-klipper-install-issue-on-octopi-1-1-0/23379/1 "2025-05-11T06:53:20Z")
### Basic Information: Printer Model: Creality Ender 3, heavily modified MCU / Printerboard: BTT SKR Mini E3 V3 Host / SBC: Raspberry Pi 4B with 4 GB memory klippy.log: not needed for this discussion ### Describe your issue: I had problems with using KIAUH to install Klipper on an Octopi 1.1.0 image. The problem turned out to be **cockpit error**. A lot has changed since I first used KIAUH. At that time there was an option to use a separate directory, _~/klipper\_config_, for the _printer.cfg_ file. That option was deleted, but I did not understand why. Changes in Klipper caused me to believe that the Klipper installation by KIAUH was either incomplete or did not work. 1. I had thought that the default location for the Klipper _printer.cfg_ file was in the home directory, and I liked the idea of the dedicated _klipper\_config_ directory. I found a post on the Internet that told how to modify the _~/klipper/scripts/install-octopi.sh_ file to specify the path to the configuration file by modifying the Klippy argument . As most of you probably know, the current default location for the configuration file is _~/printer\_data/config_. KIAUH installs a sample file there, but it won’t run a printer. 2. When I first installed Klipper, the serial port for the printer in OctoPrint was _/tmp/printer_. This no longer works. The correct printer port is _~/printer\_data/comms/klippy.serial_. When I tried using this in OctoPrint, it did not work, but _/home/pi/printer\_data/comms/klippy.serial_ does work. 3. Likewise, the change in location of the _klippy.log_ file from _/tmp_ to _~/printer\_data/logs_ caused me to believe that Klipper was not running since I could not see a log file. 4. My initial installation of Klipper used the _/etc/init.d_ directory for the Klipper system service definition, and this is where the _~/klipper/scripts/install-octopi.sh_ command file places the file. When I did not see a _klipper_ file there I thought that the KIAUH installation did not work. Now I see that it did not work as I had expected it to, but worked as intended. I would like to thank Sineos for helping me understand my failings. KIAUH works just fine on OctoPrint, at least if the user knows what they are doing. Now, if I could just get my touchscreen display to work again… ---
**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:** [May 11, 2025, 7:40am UTC](https://klipper.discourse.group/t/resolved-kiauh-klipper-install-issue-on-octopi-1-1-0/23379/2 "2025-05-11T07:40:11Z")
Thanks for sharing this. 👍 Regarding the display, it might be best to open a new thread and provide all necessary information: - Exact type of the display - klippy.log - Old configuration / How did you work with it before? / Special OctoPrint plugin / KlipperScreen, etc. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [July 10, 2025, 7:40am UTC](https://klipper.discourse.group/t/resolved-kiauh-klipper-install-issue-on-octopi-1-1-0/23379/3 "2025-07-10T07:40:32Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.