However, a connection can be established but later it's the printer that denies further communication:
2023-02-26 14:29:24,754 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2023-02-26 14:29:24,779 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 7 port/baudrate candidates: /dev/ttyUSB0@115200, /dev/ttyUSB0@250000, /dev/ttyUSB0@230400, /dev/ttyUSB0@57600, /dev/ttyUSB0@38400, /dev/ttyUSB0@19200, /dev/ttyUSB0@9600
2023-02-26 14:29:24,779 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyUSB0, baudrate 115200
2023-02-26 14:29:24,792 - octoprint.util.comm - INFO - Connecting to port /dev/ttyUSB0, baudrate 115200
2023-02-26 14:29:24,863 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2023-02-26 14:29:24,875 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2023-02-26 14:29:24,931 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2023-02-26 14:29:24,952 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2023-02-26 14:29:55,113 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2023-02-26 14:29:57,117 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2023-02-26 14:29:59,121 - octoprint.util.comm - INFO - No response from printer after 3 consecutive communication timeouts, considering it dead.
2023-02-26 14:29:59,142 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline after error"
2023-02-26 14:29:59,162 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2023-02-26 14:33:49,697 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial connection"
2023-02-26 14:33:49,713 - octoprint.util.comm - INFO - Connecting to port /dev/ttyUSB0, baudrate 115200
2023-02-26 14:33:49,748 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial connection" to "Connecting"
2023-02-26 14:33:49,777 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2023-02-26 14:33:49,788 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2023-02-26 14:33:49,792 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2023-02-26 14:33:49,869 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2023-02-26 14:33:49,931 - octoprint.util.comm - INFO - Printer reports firmware name "2.0.8.2 (Jul 6 2022 19:18:56)"
2023-02-26 14:33:49,992 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2023-02-26 14:33:50,030 - octoprint.util.comm - INFO - Firmware states that it supports emergency GCODEs to be sent without waiting for an acknowledgement first
2023-02-26 14:33:50,034 - octoprint.plugins.firmware_check - INFO - Your printer's firmware supports host action commands, but they are disabled. The firmware will not inform OctoPrint about job pause & cancellations, filament runouts, and similar firmware-side events. If you want this functionality, you need to change your firmware's configuration.. More information at https://faq.octoprint.org/warning-firmware-hostcommands
2023-02-26 14:34:20,197 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2023-02-26 14:34:50,229 - octoprint.util.comm - INFO - Communication timeout while idle, trying to trigger response from printer.
2023-02-26 14:35:20,261 - octoprint.util.comm - INFO - No response from printer after 3 consecutive communication timeouts, considering it dead.
2023-02-26 14:35:20,283 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline after error"
You may put this values:
port /dev/ttyUSB0, baudrate 115200
manually to the Connection settings in hope the connection stay stable.