[GH-ISSUE #1120] [Bug]: Can't connect to virtual printer on docker host

BreizhHardware commented

2026-05-07 00:13:54 +02:00

Owner

Originally created by @maugsburger on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1120

Originally assigned to: @maziggy on GitHub.

Component

Bambuddy

Bug Description

The virtual printer is shown in Orca Slicer, I can start the connection process, but it always fails.

Orca Slicer 2.3.2, tried with Network Plugin 02.01.01.52 and 02.03.00.62

Expected Behavior

The connection works.

Steps to Reproduce

Start the Connection process, either auto discovered or with access code, after entering the access code it always yields the same result: Connection fails with code -1:

Afterwards, the printer is shown in the device list:

Trying to connect to it gives the same -1 error as above.

Printer Model

X1 Carbon

Bambuddy Version

v0.2.3.2

SpoolBuddy Version

No response

Printer Firmware Version

No response

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

bambuddy-support-20260424-211043.zip

Screenshots

No response

Additional Context

Orca Slicer always has the same error in the logs when trying to connect (detected with the correct ip):

[info]  2026-04-24 21:10:01.995038[Thread 0x00007fdd28a10d00]:on_machine_alive New Machine, dev_id= 00M00A391800001, ip = x.x.52.53, printer_name = x1cbuddy, con_type= lan, signal= -44, bind_state= free
[…]
15094-[info]	2026-04-24 21:10:09.054791[Thread 0x00007fdd28a10d00]:process_ui_task{ type:Backup, id:0, path:, object:0, extra:2} and interval = 10
15095:[info]	2026-04-24 21:10:16.101377[Thread 0x00007fdd28a10d00]:set_selected_machine=00M00A391800001 cur_selected=
15096:[info]	2026-04-24 21:10:16.101409[Thread 0x00007fdd28a10d00]:set_selected_machine: select new lan machine, dev_id =00M00A391800001
15097:[trace]	2026-04-24 21:10:16.101419[Thread 0x00007fdd28a10d00]:reset dev_id=00M00A391800001
15098:[trace]	2026-04-24 21:10:16.101423[Thread 0x00007fdd28a10d00]:diff2all_base_reset
15099:[trace]	2026-04-24 21:10:16.102863[Thread 0x00007fdd28a10d00]:status_panel: set_default
15100:[info]	2026-04-24 21:10:16.102917[Thread 0x00007fdd28a10d00]:market_scoring_hide hide market scoring page
15101:[info]	2026-04-24 21:10:16.103162[Thread 0x00007fdd28a10d00]:monitor: show_status = 32
15102:[trace]	2026-04-24 21:10:16.103496[Thread 0x00007fdd28a10d00]:status_panel: set_default
15103:[info]	2026-04-24 21:10:16.103525[Thread 0x00007fdd28a10d00]:market_scoring_hide hide market scoring page
15104:[info]	2026-04-24 21:10:16.103847[Thread 0x00007fdd28a10d00]:is_info_ready: not ready, failed to check version
15105:[info]	2026-04-24 21:10:16.318495[Thread 0x00007fdd28a10d00]:set_selected_machine= cur_selected=00M00A391800001
15106:[info]	2026-04-24 21:10:16.323682[Thread 0x00007fdd28a10d00]:is_info_ready: not ready, failed to check version
15107:[info]	2026-04-24 21:10:16.323692[Thread 0x00007fdd28a10d00]:build_filament_ams_list: name Ext setting_id  type  color 
15108:[info]	2026-04-24 21:10:16.323714[Thread 0x00007fdd28a10d00]:load_ams_list: 1 items
15109:[info]	2026-04-24 21:10:16.323965[Thread 0x00007fdd28a10d00]:add_ams_filaments:  Ext 's filament_id is empty.
15110:[info]	2026-04-24 21:10:16.900576[Thread 0x00007fdd28a10d00]:monitor: show_status = 4
15111:[trace]	2026-04-24 21:10:16.901044[Thread 0x00007fdd28a10d00]:status_panel: set_default
15112:[info]	2026-04-24 21:10:16.901093[Thread 0x00007fdd28a10d00]:market_scoring_hide hide market scoring page
15113-[info]	2026-04-24 21:10:19.054687[Thread 0x00007fdab17fa6c0]:process_task{ type:Backup, id:0, path:, object:0, extra:3} and interval = 10

Also checked tcpdump on bost hosts, same packets on both hosts, no firewall is rejecting any packets

Docker config for reference:

services:
  bambuddy:
    image: ghcr.io/maziggy/bambuddy:latest
    container_name: bambuddy
    volumes:
      - bambuddy_data:/app/data
      - bambuddy_logs:/app/logs
    environment:
      - TZ=Europe/Berlin  # Your 
    labels: 
      - traefik.enable=true
      - traefik.http.services.bambuddy.loadbalancer.server.port=8000
    cap_add:
      - NET_BIND_SERVICE  # Required for virtual printer proxy (port 990)
    restart: unless-stopped
    networks:
      proxy:
      x1cbuddy:
        ipv4_address: x.x.52.53

networks:
  proxy:
    external: true
  x1cbuddy:
    driver: ipvlan
    driver_opts:
      parent: eth0
    ipam:
      config:
        - subnet: "x.x.52.0/24"
          gateway: "xx.x.52.1"

volumes:
  bambuddy_data:
  bambuddy_logs:

SSL certificate is copied and added to local keyring as well, started with SSL_CERT_FILE=/path/to/certs.crt orca-slicer

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @maugsburger on GitHub (Apr 24, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1120 Originally assigned to: @maziggy on GitHub. ### Component Bambuddy ### Bug Description The virtual printer is shown in Orca Slicer, I can start the connection process, but it always fails. Orca Slicer 2.3.2, tried with Network Plugin 02.01.01.52 and 02.03.00.62 ### Expected Behavior The connection works. ### Steps to Reproduce 1. Start the Connection process, either auto discovered or with access code, after entering the access code it always yields the same result: Connection fails with code -1: <img width="557" height="186" alt="Image" src="https://github.com/user-attachments/assets/9908942e-f52f-4952-8bc3-47745ba3e840" /> Afterwards, the printer is shown in the device list: <img width="238" height="153" alt="Image" src="https://github.com/user-attachments/assets/67160e74-c94d-4211-a39d-0e7adcc82113" /> Trying to connect to it gives the same -1 error as above. ### Printer Model X1 Carbon ### Bambuddy Version v0.2.3.2 ### SpoolBuddy Version _No response_ ### Printer Firmware Version _No response_ ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package [bambuddy-support-20260424-211043.zip](https://github.com/user-attachments/files/27064370/bambuddy-support-20260424-211043.zip) ### Screenshots _No response_ ### Additional Context Orca Slicer always has the same error in the logs when trying to connect (detected with the correct ip): ``` [info] 2026-04-24 21:10:01.995038[Thread 0x00007fdd28a10d00]:on_machine_alive New Machine, dev_id= 00M00A391800001, ip = x.x.52.53, printer_name = x1cbuddy, con_type= lan, signal= -44, bind_state= free […] 15094-[info] 2026-04-24 21:10:09.054791[Thread 0x00007fdd28a10d00]:process_ui_task{ type:Backup, id:0, path:, object:0, extra:2} and interval = 10 15095:[info] 2026-04-24 21:10:16.101377[Thread 0x00007fdd28a10d00]:set_selected_machine=00M00A391800001 cur_selected= 15096:[info] 2026-04-24 21:10:16.101409[Thread 0x00007fdd28a10d00]:set_selected_machine: select new lan machine, dev_id =00M00A391800001 15097:[trace] 2026-04-24 21:10:16.101419[Thread 0x00007fdd28a10d00]:reset dev_id=00M00A391800001 15098:[trace] 2026-04-24 21:10:16.101423[Thread 0x00007fdd28a10d00]:diff2all_base_reset 15099:[trace] 2026-04-24 21:10:16.102863[Thread 0x00007fdd28a10d00]:status_panel: set_default 15100:[info] 2026-04-24 21:10:16.102917[Thread 0x00007fdd28a10d00]:market_scoring_hide hide market scoring page 15101:[info] 2026-04-24 21:10:16.103162[Thread 0x00007fdd28a10d00]:monitor: show_status = 32 15102:[trace] 2026-04-24 21:10:16.103496[Thread 0x00007fdd28a10d00]:status_panel: set_default 15103:[info] 2026-04-24 21:10:16.103525[Thread 0x00007fdd28a10d00]:market_scoring_hide hide market scoring page 15104:[info] 2026-04-24 21:10:16.103847[Thread 0x00007fdd28a10d00]:is_info_ready: not ready, failed to check version 15105:[info] 2026-04-24 21:10:16.318495[Thread 0x00007fdd28a10d00]:set_selected_machine= cur_selected=00M00A391800001 15106:[info] 2026-04-24 21:10:16.323682[Thread 0x00007fdd28a10d00]:is_info_ready: not ready, failed to check version 15107:[info] 2026-04-24 21:10:16.323692[Thread 0x00007fdd28a10d00]:build_filament_ams_list: name Ext setting_id type color 15108:[info] 2026-04-24 21:10:16.323714[Thread 0x00007fdd28a10d00]:load_ams_list: 1 items 15109:[info] 2026-04-24 21:10:16.323965[Thread 0x00007fdd28a10d00]:add_ams_filaments: Ext 's filament_id is empty. 15110:[info] 2026-04-24 21:10:16.900576[Thread 0x00007fdd28a10d00]:monitor: show_status = 4 15111:[trace] 2026-04-24 21:10:16.901044[Thread 0x00007fdd28a10d00]:status_panel: set_default 15112:[info] 2026-04-24 21:10:16.901093[Thread 0x00007fdd28a10d00]:market_scoring_hide hide market scoring page 15113-[info] 2026-04-24 21:10:19.054687[Thread 0x00007fdab17fa6c0]:process_task{ type:Backup, id:0, path:, object:0, extra:3} and interval = 10 ``` Also checked tcpdump on bost hosts, same packets on both hosts, no firewall is rejecting any packets Docker config for reference: ``` services: bambuddy: image: ghcr.io/maziggy/bambuddy:latest container_name: bambuddy volumes: - bambuddy_data:/app/data - bambuddy_logs:/app/logs environment: - TZ=Europe/Berlin # Your labels: - traefik.enable=true - traefik.http.services.bambuddy.loadbalancer.server.port=8000 cap_add: - NET_BIND_SERVICE # Required for virtual printer proxy (port 990) restart: unless-stopped networks: proxy: x1cbuddy: ipv4_address: x.x.52.53 networks: proxy: external: true x1cbuddy: driver: ipvlan driver_opts: parent: eth0 ipam: config: - subnet: "x.x.52.0/24" gateway: "xx.x.52.1" volumes: bambuddy_data: bambuddy_logs: ``` SSL certificate is copied and added to local keyring as well, started with `SSL_CERT_FILE=/path/to/certs.crt orca-slicer` ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:13:54 +02:00

closed this issue
added the
invalid
label

BreizhHardware commented

2026-05-07 00:13:55 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 25, 2026):

You didn't follow the installation instructions.

  "developer_mode": null,

Developer mode is not enabled.

"network_mode_hint": "bridge"

Docker network is not using host mode.

@maziggy commented on GitHub (Apr 25, 2026): You didn't follow the installation instructions. > "developer_mode": null, Developer mode is not enabled. > "network_mode_hint": "bridge" Docker network is not using host mode.

BreizhHardware commented

2026-05-07 00:13:55 +02:00

Author

Owner

@bjQrnen commented on GitHub (Apr 25, 2026):

And if you still get '-1' after this, make sure the certificate is appended correctly. Claude borked this one in its first attempt for me

@bjQrnen commented on GitHub (Apr 25, 2026): And if you still get '-1' after this, make sure the certificate is appended correctly. Claude borked this one in its first attempt for me

BreizhHardware commented

2026-05-07 00:13:56 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 25, 2026):

Wondering why you guys don't read the docs. That's why we write it.

@maziggy commented on GitHub (Apr 25, 2026): Wondering why you guys don't read the docs. That's why we write it.

BreizhHardware commented

2026-05-07 00:13:56 +02:00

Author

Owner

@maugsburger commented on GitHub (Apr 25, 2026):

You didn't follow the installation instructions.
  "developer_mode": null,

At this time, my X1C was still updating to the latest firmware, and the old FW was too old for developer mode. It is updated now, but this didn't change anything. Error is still the same.

Additionally, I don't see any reason why the config of the physical printer should affect the virtual one.

Developer mode is not enabled.

"network_mode_hint": "bridge"

Docker network is not using host mode.

As I wrote above, I'm using ipvlan with a seperate IP. This should (and if not, I'd love to find the reasion and fix it) be identical to host mode, except for using a different IP. There are reasons I can't use host mode here.

Wondering why you guys don't read the docs. That's why we write it.

The docs suggest there is no hard need for host mode, only leading to SSDP discovery failing: https://wiki.bambuddy.cool/features/virtual-printer/#docker-macos-windows

@maugsburger commented on GitHub (Apr 25, 2026): > You didn't follow the installation instructions. > > > ``` > > "developer_mode": null, > > ``` At this time, my X1C was still updating to the latest firmware, and the old FW was too old for developer mode. It is updated now, but this didn't change anything. Error is still the same. Additionally, I don't see any reason why the config of the physical printer should affect the virtual one. > Developer mode is not enabled. > > > "network_mode_hint": "bridge" > > Docker network is not using host mode. As I wrote above, I'm using ipvlan with a seperate IP. This should (and if not, I'd love to find the reasion and fix it) be identical to host mode, except for using a different IP. There are reasons I can't use host mode here. > Wondering why you guys don't read the docs. That's why we write it. The docs suggest there is no hard need for host mode, only leading to SSDP discovery failing: https://wiki.bambuddy.cool/features/virtual-printer/#docker-macos-windows

BreizhHardware commented

2026-05-07 00:13:56 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 25, 2026):

At this time, my X1C was still updating to the latest firmware, and the old FW was too old for developer mode. It is updated now, but this didn't change anything. Error is still the same.

Reboot aber enabling dev mode.

Did you import the certificate as per the docs?

@maziggy commented on GitHub (Apr 25, 2026): > At this time, my X1C was still updating to the latest firmware, and the old FW was too old for developer mode. It is updated now, but this didn't change anything. Error is still the same. Reboot aber enabling dev mode. Did you import the certificate as per the docs?

BreizhHardware commented

2026-05-07 00:13:56 +02:00

Author

Owner

@maugsburger commented on GitHub (Apr 25, 2026):

Did you import the certificate as per the docs?

I tried :>

But this was finally the solution, yesterday I copied /etc/ssl/certs/ca-certificates.crt, added the cert there and set this as SSL_CERT_FILE (see above), as there is no ~/.local/share/OrcaSlicer/resources/cert/printer.cer on my system.

Today I digged a bit deeper and searched for the exact printer.cer file, finally found it in /opt/orca-slicer/resources/cert/printer.cer, and now it seems to work flawlessly.

I will prepare a clarification and PR for the docs, had I understand earlier that there are two different keyrings used by OrcaSlicer, and you should not get fooled by the warning when starting up, this would have saved me some trouble and pointless debugging.

@maugsburger commented on GitHub (Apr 25, 2026): > Did you import the certificate as per the docs? I tried :> But this was finally the solution, yesterday I copied `/etc/ssl/certs/ca-certificates.crt`, added the cert there and set this as `SSL_CERT_FILE` (see above), as there is no `~/.local/share/OrcaSlicer/resources/cert/printer.cer` on my system. Today I digged a bit deeper and searched for the exact `printer.cer` file, finally found it in `/opt/orca-slicer/resources/cert/printer.cer`, and now it seems to work flawlessly. I will prepare a clarification and PR for the docs, had I understand earlier that there are two different keyrings used by OrcaSlicer, and you should not get fooled by the warning when starting up, this would have saved me some trouble and pointless debugging.

BreizhHardware commented

2026-05-07 00:13:56 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 25, 2026):

Yeah, I know that the docs are not perfect. We are desperately seeking for a contributor who is willing the improve the docs. Unfortunately I simply don't have the time.

@maziggy commented on GitHub (Apr 25, 2026): Yeah, I know that the docs are not perfect. We are desperately seeking for a contributor who is willing the improve the docs. Unfortunately I simply don't have the time.

BreizhHardware commented

2026-05-07 00:13:56 +02:00

Author

Owner

@maugsburger commented on GitHub (Apr 25, 2026):

Here you go: https://github.com/maziggy/bambuddy-wiki/pull/20

@maugsburger commented on GitHub (Apr 25, 2026): Here you go: https://github.com/maziggy/bambuddy-wiki/pull/20

BreizhHardware commented

2026-05-07 00:13:57 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 25, 2026):