Bridge fails to connect to printer #1

Closed
opened 2026-04-25 20:33:10 +02:00 by dkuba4 · 6 comments

So I opened Anycubic Slicer, I've selected the printer from the LAN tab, and then run the python script to get the credentials, I made sure to paste them on the website, after I just rebooted the script, and I get the following output:

[20:30:13] INFO Verbinde mit Drucker 192.168.1.102:9883 …
[kobrax] TLS: TLS_AES_256_GCM_SHA384
[20:30:13] WARNING Drucker nicht erreichbar (CONNACK failed: 20020005) – starte im Offline-Modus
[20:30:13] INFO Bridge läuft auf http://0.0.0.0:7125
[20:30:13] INFO OrcaSlicer → Klipper → Host: 0.0.0.0  Port: 7125
[20:30:13] INFO Ctrl-C zum Beenden
[20:30:13] INFO Drucker erreichbar – stelle MQTT-Verbindung her …
[kobrax] TLS: TLS_AES_256_GCM_SHA384
[20:30:13] WARNING Verbindungsaufbau fehlgeschlagen: CONNACK failed: 20020005
[20:30:16] INFO Bridge beendet

Printer information:
Kobra X (Firmware version 1.2.0.2)
KX Bridge version: 0.9.1-beta10

So I opened Anycubic Slicer, I've selected the printer from the LAN tab, and then run the python script to get the credentials, I made sure to paste them on the website, after I just rebooted the script, and I get the following output: ```❯ python kobrax_moonraker_bridge.py ✔ [20:30:13] INFO Verbinde mit Drucker 192.168.1.102:9883 … [kobrax] TLS: TLS_AES_256_GCM_SHA384 [20:30:13] WARNING Drucker nicht erreichbar (CONNACK failed: 20020005) – starte im Offline-Modus [20:30:13] INFO Bridge läuft auf http://0.0.0.0:7125 [20:30:13] INFO OrcaSlicer → Klipper → Host: 0.0.0.0 Port: 7125 [20:30:13] INFO Ctrl-C zum Beenden [20:30:13] INFO Drucker erreichbar – stelle MQTT-Verbindung her … [kobrax] TLS: TLS_AES_256_GCM_SHA384 [20:30:13] WARNING Verbindungsaufbau fehlgeschlagen: CONNACK failed: 20020005 [20:30:16] INFO Bridge beendet ``` Printer information: Kobra X (Firmware version 1.2.0.2) KX Bridge version: 0.9.1-beta10
viewit added reference master 2026-04-25 22:06:47 +02:00
viewit self-assigned this 2026-04-25 22:06:57 +02:00
Owner

Docker or Standalone ?
Ping Printerip is ok ?
It looks like your login credentials are incorrect. Please try running the password recovery tool with the --verbose parameter and test the passwords it finds. Does your username start with “user”?

Docker or Standalone ? Ping *Printerip* is ok ? It looks like your login credentials are incorrect. Please try running the password recovery tool with the --verbose parameter and test the passwords it finds. Does your username start with “user”?
Author

Ye everything was fine, I ended up booting my laptop, and installed ASN there and just extracted the credentials from there, it is working, other than the camera.

Ye everything was fine, I ended up booting my laptop, and installed ASN there and just extracted the credentials from there, it is working, other than the camera.
Owner

Do you use Windows or Linux? For Windows, ffmpeg.exe must be in the same directory as the bridge. I'm currently working on an update for the Windows version as well. A few bugs have been fixed, and the README has been updated accordingly. I'm glad to hear that it works in principl

Do you use Windows or Linux? For Windows, ffmpeg.exe must be in the same directory as the bridge. I'm currently working on an update for the Windows version as well. A few bugs have been fixed, and the README has been updated accordingly. I'm glad to hear that it works in principl
Author

I am using a docker container that just runs the python script. I've also found another issue, should I report it here, or make a new bug report, it is related to what I would assume is filament parsing.

services:
  kx-bridge:
    image: python:3.12-slim
    container_name: kx-bridge
    working_dir: /app

    volumes:
      - /mnt/Ext_Drive/SMB_Share/Docker/kx-bridge:/app

    command: sh -c "pip install --no-cache-dir -r requirements.txt && python kobrax_moonraker_bridge.py"

    ports:
      - "7125:7125"

    restart: unless-stopped

    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

I am using a docker container that just runs the python script. I've also found another issue, should I report it here, or make a new bug report, it is related to what I would assume is filament parsing. ``` services: kx-bridge: image: python:3.12-slim container_name: kx-bridge working_dir: /app volumes: - /mnt/Ext_Drive/SMB_Share/Docker/kx-bridge:/app command: sh -c "pip install --no-cache-dir -r requirements.txt && python kobrax_moonraker_bridge.py" ports: - "7125:7125" restart: unless-stopped logging: driver: json-file options: max-size: "10m" max-file: "3" ```
Owner

add

RUN apt-get update && apt-get install -y --no-install-recommends ffmpeg && rm -rf /var/lib/apt/lists/*

see dockerfile in repo .

add `RUN apt-get update && apt-get install -y --no-install-recommends ffmpeg && rm -rf /var/lib/apt/lists/*` see dockerfile in repo .
Owner

Fixed in v0.9.1-beta12:

The error message for wrong MQTT credentials (code 20020005) is now human-readable: Wrong MQTT credentials (wrong username, password or device ID).

Make sure extract_credentials is run while the Anycubic Slicer is open and connected to your printer.
Fmpeg is now not needed .

Fixed in v0.9.1-beta12: The error message for wrong MQTT credentials (code 20020005) is now human-readable: `Wrong MQTT credentials (wrong username, password or device ID)`. Make sure `extract_credentials` is run while the Anycubic Slicer is open and connected to your printer. Fmpeg is now not needed .
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#1
No description provided.