further information
i tried to connect again using http://octopi42.local (I had set the hostname to octopi42)
and it now works?!?
attached is more of octoprint log:
2025-05-01 17:28:59,277 - octoprint.server - INFO - ------------------------------------------------------------------------------
2025-05-01 17:28:59,720 - octoprint.plugins.healthcheck.python_eol - INFO - Fetched Python EOL data from https://get.octoprint.org/python-eol
2025-05-01 17:43:59,228 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-05-01 17:58:59,229 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-05-01 18:09:46,193 - octoprint.plugins.softwareupdate - INFO - Fetching check overlays from https://plugins.octoprint.org/update_check_overlay.json
2025-05-01 18:09:48,550 - octoprint.util.pip - INFO - Using "/home/pi/oprint/bin/python -m pip" as command to invoke pip
2025-05-01 18:09:48,553 - octoprint.util.pip - INFO - pip installs to /home/pi/oprint/lib/python3.9/site-packages (writable -> yes), --user flag needed -> no, virtual env -> yes
2025-05-01 18:09:48,554 - octoprint.util.pip - INFO - ==> pip ok -> yes
2025-05-01 18:09:49,236 - octoprint.server.util.flask.PreemptiveCache - INFO - Adding entry for / and {'path': '/', 'base_url': 'http://192.168.1.37/', 'query_string': 'l10n=en', '_timestamp': 1746119389.236282, '_count': 1}
2025-05-01 18:13:07,141 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.1.9
2025-05-01 18:13:08,056 - tornado.access - WARNING - 403 GET /api/printer/error (192.168.1.9) 162.81ms
2025-05-01 18:13:08,093 - tornado.access - WARNING - 403 POST /api/plugin/tracking (192.168.1.9) 192.13ms
2025-05-01 18:13:08,141 - tornado.access - WARNING - 403 GET /api/printerprofiles/_default (192.168.1.9) 27.45ms
2025-05-01 18:13:08,186 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.1.9
2025-05-01 18:13:59,231 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2025-05-01 18:14:20,814 - octoprint.server.util.flask.PreemptiveCache - INFO - Adding entry for / and {'path': '/', 'base_url': 'http://octopi42.local/', 'query_string': 'l10n=en', '_timestamp': 1746119660.8140235, '_count': 1}
2025-05-01 18:14:22,396 - octoprint.server.util.sockjs - INFO - New connection from client: 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:14:23,265 - tornado.access - WARNING - 403 GET /api/printer/error (2a0a:ef40:70:9201:a80a:2cf2:b686:3496) 190.82ms
2025-05-01 18:14:23,269 - tornado.access - WARNING - 403 POST /api/plugin/tracking (2a0a:ef40:70:9201:a80a:2cf2:b686:3496) 190.52ms
2025-05-01 18:14:23,340 - tornado.access - WARNING - 403 GET /api/printerprofiles/_default (2a0a:ef40:70:9201:a80a:2cf2:b686:3496) 27.96ms
2025-05-01 18:14:55,551 - octoprint.access.users - INFO - Logged in user: pi
2025-05-01 18:14:55,554 - octoprint.server.api - INFO - Actively logging in user pi from 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:14:55,662 - octoprint.server.util.sockjs - INFO - User pi logged in on the socket from client 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:14:56,484 - octoprint.plugins.announcements - INFO - Loaded channel _important from https://octoprint.org/feeds/important.xml in 0.19s
2025-05-01 18:14:57,596 - octoprint.plugins.pluginmanager - INFO - Loaded plugin notices data from https://plugins.octoprint.org/notices.json
2025-05-01 18:14:57,658 - octoprint.plugins.announcements - INFO - Loaded channel _releases from https://octoprint.org/feeds/releases.xml in 0.22s
2025-05-01 18:14:58,350 - octoprint.plugins.softwareupdate - INFO - Saved version cache to disk
2025-05-01 18:14:58,451 - octoprint.plugins.announcements - INFO - Loaded channel _blog from https://octoprint.org/feeds/octoblog.xml in 0.14s
2025-05-01 18:14:58,778 - octoprint.plugins.announcements - INFO - Loaded channel _plugins from https://plugins.octoprint.org/feed.xml in 0.11s
2025-05-01 18:14:59,119 - octoprint.plugins.announcements - INFO - Loaded channel _octopi from https://octoprint.org/feeds/octopi.xml in 0.11s
2025-05-01 18:16:24,182 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 2873, 'printer_state': 'OFFLINE'}
2025-05-01 18:16:24,354 - octoprint.plugins.tracking - INFO - Sent tracking event startup, payload: {'version': '1.11.0', 'os': 'linux', 'platform': 'Linux-6.1.21-v7+-armv7l-with-glibc2.31', 'bits': 32, 'python': '3.9.2', 'pip': '22.3', 'cores': 4, 'freq': 1200.0, 'ram': 912703488, 'pi_model': 'Raspberry Pi 3 Model B Rev 1.2', 'octopi_version': '1.0.0', 'octopiuptodate_build': '1.0.0-1.11.0-20250422094030'}
2025-05-01 18:16:24,516 - octoprint.plugins.tracking - INFO - Sent tracking event pong, payload: {'version': '1.11.0', 'os': 'linux', 'platform': 'Linux-6.1.21-v7+-armv7l-with-glibc2.31', 'bits': 32, 'python': '3.9.2', 'pip': '22.3', 'cores': 4, 'freq': 1200.0, 'ram': 912703488, 'pi_model': 'Raspberry Pi 3 Model B Rev 1.2', 'octopi_version': '1.0.0', 'octopiuptodate_build': '1.0.0-1.11.0-20250422094030', 'plugins': '', 'achievements': 'the_wizard'}
2025-05-01 18:17:23,662 - octoprint.server.util.flask - INFO - Passively logging in user pi from 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:17:23,663 - octoprint.access.users - INFO - Logged in user: pi
2025-05-01 18:17:24,892 - octoprint.server.util.sockjs - INFO - Client connection closed: 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:17:25,139 - octoprint.server.util.sockjs - INFO - New connection from client: 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:17:25,237 - octoprint.server.util.flask - INFO - Passively logging in user pi from 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:17:25,238 - octoprint.access.users - INFO - Logged in user: pi
2025-05-01 18:17:25,882 - octoprint.server.util.sockjs - INFO - User pi logged in on the socket from client 2a0a:ef40:70:9201:a80a:2cf2:b686:3496
2025-05-01 18:17:27,394 - octoprint.plugins.tracking - INFO - Sent tracking event webui_load, payload: {'browser_name': 'Safari', 'browser_version': '18.4', 'os_name': 'Mac OS', 'os_version': '10.15.7'}
2025-05-01 18:17:34,061 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2025-05-01 18:17:34,100 - 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
2025-05-01 18:17:34,101 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyUSB0, baudrate 115200
2025-05-01 18:17:34,104 - octoprint.util.comm - INFO - Connecting to port /dev/ttyUSB0, baudrate 115200
2025-05-01 18:17:34,155 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2025-05-01 18:17:34,173 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2025-05-01 18:17:34,449 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2025-05-01 18:17:34,478 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2025-05-01 18:17:34,494 - octoprint.server - INFO - Autorefresh of serial port list stopped
2025-05-01 18:17:40,107 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin Creality 3D"
2025-05-01 18:17:40,108 - octoprint.util.comm - INFO - Firmware info line: FIRMWARE_NAME:Marlin Creality 3D SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:Ender-3 Pro EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
2025-05-01 18:17:40,141 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2025-05-01 18:17:40,208 - octoprint.util.comm - INFO - Firmware sent the following capability report:
EEPROM: supported
AUTOREPORT_TEMP: supported
PROGRESS: not supported
PRINT_JOB: supported
AUTOLEVEL: supported
Z_PROBE: supported
LEVELING_DATA: supported
SOFTWARE_POWER: not supported
TOGGLE_LIGHTS: not supported
CASE_LIGHT_BRIGHTNESS: not supported
EMERGENCY_PARSER: not supported
2025-05-01 18:17:40,279 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {'firmware_name': 'Marlin Creality 3D', 'printer_port': 'AUTO', 'printer_baudrate': 0}
2025-05-01 18:17:51,809 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2025-05-01 18:17:55,295 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
wonder why it took so long to get bump started?
cheers
