# Permission issue when connecting to printer - Unable to open serial port, operation not permitted

**URL:** <https://klipper.discourse.group/t/permission-issue-when-connecting-to-printer-unable-to-open-serial-port-operation-not-permitted/11230>\
**Category:** General Discussion\
**Created:** [October 27, 2023, 5:23pm UTC](https://klipper.discourse.group/t/permission-issue-when-connecting-to-printer-unable-to-open-serial-port-operation-not-permitted/11230 "2023-10-27T17:23:40Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [October 28, 2023, 1:04pm UTC](https://klipper.discourse.group/t/permission-issue-when-connecting-to-printer-unable-to-open-serial-port-operation-not-permitted/11230/11 "2023-10-28T13:04:54Z")

</div>

You cannot compare the two. In Klipper, the host process running on the SBC (or in your case in Docker) is the central “brain” of this solution and is responsible for maintaining the necessary timings and it requires constant, precisely timed and permanent access to the MCU. Any delay or interference will result in Klipper errors.

For a better understanding of the Klipper architecture refer to [Klipper Architecture / Ecosystem](https://klipper.discourse.group/t/klipper-architecture-ecosystem/6313)

---

_[View the full topic](https://klipper.discourse.group/t/permission-issue-when-connecting-to-printer-unable-to-open-serial-port-operation-not-permitted/11230)._