[GH-ISSUE #221] [Bug]: "Virtual Printer" set-up Instructions aren't appropriate #139

New issue

Closed

opened 2026-05-06 12:26:18 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-06 12:26:18 +02:00

Owner

Originally created by @heviiguy on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/221

Originally assigned to: @maziggy on GitHub.

Bug Description

Well, at least in my case they appear to be inappropriate...

The instructions state:

You must replace the last certificate with the Bambuddy CA. Do NOT simply append - having multiple certificates causes connection failures!

I had a single certificate in my original printer.cer files. Following the instructions, I deleted this "last certificate" and continued to set-up the v printer. In the end, I was able to access it from both Bambu Studio and Orca Slicer. However, I was no longer able to connect to my actual printer!

To solve this problem, I disregarded the instructions and did indeed append the bambuddy cert stanza to the original. I can now "print" to the physical printer as well as to the virtual printer from both slicers.

Expected Behavior

Steps to Reproduce

Printer Model

P1S

Bambuddy Version

0.1.6

Printer Firmware Version

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

No response

Additional Context

No response

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

Originally created by @heviiguy on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/221 Originally assigned to: @maziggy on GitHub. ### Bug Description Well, at least in my case they appear to be inappropriate... The instructions state: > You must replace the last certificate with the Bambuddy CA. Do NOT simply append - having multiple certificates causes connection failures! I had a single certificate in my original printer.cer files. Following the instructions, I deleted this "last certificate" and continued to set-up the v printer. In the end, I was able to access it from both Bambu Studio and Orca Slicer. However, I was no longer able to connect to my actual printer! To solve this problem, I disregarded the instructions and did indeed _append_ the bambuddy cert stanza to the original. I can now "print" to the physical printer as well as to the virtual printer from both slicers. ### Expected Behavior . ### Steps to Reproduce . ### Printer Model P1S ### Bambuddy Version 0.1.6 ### Printer Firmware Version . ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots _No response_ ### Additional Context _No response_ ### 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

BreizhHardware

2026-05-06 12:26:18 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:26:19 +02:00

Author

Owner

@heviiguy commented on GitHub (Feb 1, 2026):

Another suggestion: Consider adding firewall instructions for those who use firewalld.

Firewall rules (if using firewalld):

sudo firewall-cmd --permanent --add-port=2021/udp  # SSDP
sudo firewall-cmd --permanent --add-port=8883/tcp  # MQTT
sudo firewall-cmd --permanent --add-port=990/tcp   # FTPS
sudo firewall-cmd --permanent --add-port=9990/tcp  # FTPS internal

@heviiguy commented on GitHub (Feb 1, 2026): Another suggestion: Consider adding firewall instructions for those who use firewalld. ### Firewall rules (if using firewalld): ``` sudo firewall-cmd --permanent --add-port=2021/udp # SSDP sudo firewall-cmd --permanent --add-port=8883/tcp # MQTT sudo firewall-cmd --permanent --add-port=990/tcp # FTPS sudo firewall-cmd --permanent --add-port=9990/tcp # FTPS internal ```

BreizhHardware commented

2026-05-06 12:26:19 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 2, 2026):

Fixed. Thanks for pointing this out!

@maziggy commented on GitHub (Feb 2, 2026): Fixed. Thanks for pointing this out!