mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #52] [Bug]: Unable to connect to virtual printer #21
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pinionless on GitHub (Jan 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/52
Originally assigned to: @maziggy on GitHub.
Bug Description
I have tried from windows and from linux
Setup my server locally and on my docker machine
I get this error every time
Connect Bambuddy failed! [SN:00M09A391800001, code=-1]
Discovery works. Changed access code. Nothing worked.
Do I need cert installed on my machine so its trusted?
Never had an "untrusted cert error" Always -1 and logs are not very helpfull.
Expected Behavior
connects to virtual printer
Steps to Reproduce
1 install using docker compose
2 try to connect from orca slicer and bambu slicer
Printer Model
A1
Bambuddy Version
v0.1.6b5
Printer Firmware Version
01.07
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs
Screenshots
No response
Additional Context
No response
Checklist
@k33v89 commented on GitHub (Jan 4, 2026):
Same problem here....
@maziggy commented on GitHub (Jan 4, 2026):
Did you guys follow the docs? For Docker based installations, network_mode host and certificate persistence is required. In addition you need some iptables rules as shown in frontend beside the virtual printer settings.
https://wiki.bambuddy.cool/features/virtual-printer/#docker-configuration
@pinionless commented on GitHub (Jan 4, 2026):
I showed tcpdump to AI and it told me:
virtual_printer folder is at /app/data/virtual_printer
So volumes: ./apps/bambuddy/data:/app/data is sufficient
@maziggy commented on GitHub (Jan 4, 2026):
Yes, already saw the wrong mounts. Will check today and let you know.
@maziggy commented on GitHub (Jan 4, 2026):
Please use latest 0.1.6b6 release. Virtual printer module was completely refactored. Please follow the new detailed instructions in Wiki. There's now a help link in Virtual Printer tab.
@pinionless commented on GitHub (Jan 4, 2026):
.crt files on arch linux are not in the location listed in your wiki
I added printer cert somewhere... and run some tests
MQTT test
mosquitto_sub -h 192.168.1.100 -p 8883 --cafile "/etc/ssl/certs/ca-certificates.crt" -u "bblp" -P 12345678 -t "device/+/report"{"print": {"sequence_id": "12", "command": "push_status", "msg": 0, "gcode_state": "IDLE", "gcode_file": "", "gcode_file_prepare_percent": "0", "subtask_name": "", "mc_print_stage": "", "mc_percent": 0, "mc_remaining_time": 0, "wifi_signal": "-44dBm", "print_error": 0, "print_type": "", "bed_temper": 25.0, "bed_target_temper": 0.0, "nozzle_temper": 25.0, "nozzle_target_temper": 0.0, "chamber_temper": 25.0, "cooling_fan_speed": "0", "big_fan1_speed": "0", "big_fan2_speed": "0", "heatbreak_fan_speed": "0", "spd_lvl": 1, "spd_mag": 100, "stg": [], "stg_cur": 0, "layer_num": 0, "total_layer_num": 0, "home_flag": 256, "hw_switch_state": 0, "online": {"ahb": false, "rfid": false, "version": 7}, "ams_status": 0, "sdcard": true, "storage": {"free": 1000000000, "total": 32000000000}, "upgrade_state": {"sequence_id": 0, "progress": "", "status": "", "consistency_request": false, "dis_state": 0, "err_code": 0, "force_upgrade": false, "message": "", "module": "", "new_version_state": 2, "new_ver_list": [], "ota_new_version_number": "", "ahb_new_version_number": ""}, "ipcam": {"ipcam_dev": "1", "ipcam_record": "enable", "timelapse": "disable", "resolution": "1080p", "mode_bits": 0}, "xcam": {"allow_skip_parts": false, "buildplate_marker_detector": true, "first_layer_inspector": true, "halt_print_sensitivity": "medium", "print_halt": true, "printing_monitor": true, "spaghetti_detector": true}, "lights_report": [{"node": "chamber_light", "mode": "on"}], "nozzle_diameter": "0.4", "nozzle_type": "hardened_steel"}}SSL test 8883
FTP test
Looks like I can connect to the sftp but I am not able to get a list of files from virtual printer this same way curl shows me a list of files on my A1
@maziggy commented on GitHub (Jan 4, 2026):
"not able to get a list of files from virtual printer"??? What are you trying to do?
@maziggy commented on GitHub (Jan 4, 2026):
Perhaps you misunderstood the feature?
The Virtual Printer feature allows Bambuddy to emulate a Bambu Lab printer on your network. This enables you to send prints directly from Bambu Studio or Orca Slicer to Bambuddy, even without a physical printer connected.
@pinionless commented on GitHub (Jan 4, 2026):
just testing why cant connect to virtual printer from Slicer. I still have error -1
It seams like the certificate is working in all of the test
Only the ftp test hangs and does not produce file list like in a real printer.
@maziggy commented on GitHub (Jan 4, 2026):
The virtual printer thing is quite tricky. Did you exactly followed the new docs which I've updated today?
https://wiki.bambuddy.cool/features/virtual-printer/
Replacing the certificate in your slicer is essential!!!
@pinionless commented on GitHub (Jan 4, 2026):
Was the wiki made by ClaudeCode?? This might be a hallucination.
From New Docs:
Bambu Studio: ~/.local/share/BambuStudio/resources/cert/printer.cerOrcaSlicer: ~/.local/share/OrcaSlicer/resources/cert/printer.cerI could not find printer.cer file
I think I have a Virtual Printer .pam file somewhere on the system
There is a prompt starting Slicer on Linux, you can see it here.
https://github.com/OrcaSlicer/OrcaSlicer/issues/5333
They both force "/etc/ssl/certs/ca-certificates.crt". Pressing NO in the prompt will close the slicer.
So I run all the tests above to check if my cert is working.
It looks like I can connect to MQTT and to SFTP and the certificate is working fine.
IDK why its still failing with error =-1
I will try from my windows laptop if I find some time this week.
And I will maybe try an Appimage of OrcaSlicer.
From Orca Logs:
This might be part of the issue.
@pinionless commented on GitHub (Jan 4, 2026):
Also, I was never able to add the virtual printer by IP address(and code) by itself
I had to add it from the discovered list or the "manual" way with serial number + IP
It shows up in the list as "online" but its impossible to connect
@maziggy commented on GitHub (Jan 4, 2026):
Show me the output of /api/v1/settings/virtual-printer
@pinionless commented on GitHub (Jan 4, 2026):
{"enabled":true,"access_code_set":true,"mode":"queue","model":"N2S","status":{"enabled":true,"running":true,"mode":"queue","name":"Bambuddy","serial":"03900A391800001","model":"N2S","model_name":"A1","pending_files":0}}@pinionless commented on GitHub (Jan 4, 2026):
For anyone that have an issue connecting with the virtual printer here is my small script that watches local folder and uploads files saved there to the Bambuddy sftp.
So you can just press "Export plate sliced file" and save it in the "watched folder"
You can add "--insecure" to the curl command to avoid having to copy printer cert from the server.
requires inotify-tools and curl
print_later.sh
@maziggy commented on GitHub (Jan 5, 2026):
OK, let's debug it in detail....
Make sure you are on the latest version 0.1.6b6 and enable debug logging (https://wiki.bambuddy.cool/getting-started/installation/?h=debug#development-settings). Then test and send me the complete logs.
@maziggy commented on GitHub (Jan 5, 2026):
In addition you need to find the printer.cer file from BambuStudio and replace the certificate as explained in documentation. Before this is not done, it doesn't makes sense to debug further. Without the correct slicer certificate it cannot work.
@maziggy commented on GitHub (Jan 5, 2026):
If you use branch 0.1.6b7 you could use the new "export debug logs" function.
https://wiki.bambuddy.cool/features/system-info/#support-bundle
@pinionless commented on GitHub (Jan 5, 2026):
I don't know why and how but today it works. PC restarts? server restart? who knows :)
@FoxxMD commented on GitHub (Feb 9, 2026):
I am having the same issue as @pinionless . Also on arch linux. Orcaslicer built from source. I've added
bbl_ca.crtto my certs and can succefully run the same individual testopenssl s_client .... Running bambuddy with docker network_mode host and iptables redirecting for sftp. Also getting -1 error@maziggy commented on GitHub (Feb 9, 2026):
Please use branch 0.1.9b and send me a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
A screenshot from Settings -> Virtual Printer would also be helpful.
@FoxxMD commented on GitHub (Feb 9, 2026):
Attached is the support bundle. It's a 10 second window where all I did was attempt to connect to the virtual printer using orceslicer and received the
-1errorbambuddy-support-20260209-133127.zip
Something else I noticed: it looks like the wrong IP is being used for generating for the cert and for starting SSDP server. I have several interfaces on this host. The Main LAN interface
ens18is bound on192.168.0.0/24but the cert/server is using another interfaceenp0s19that is for a private subnet not accessible from the LAN192.168.99.0/24. Is there a way to specify what interface to use?My compose stack is using
network_mode: host@maziggy commented on GitHub (Feb 10, 2026):
Your machine has multiple network interfaces and the auto-detection picks the wrong one. The virtual printer uses 192.168.99.3 (from enp0s19, your private subnet) instead of your LAN IP on ens18. This affects both the TLS certificate (wrong IP in SAN) and SSDP discovery (advertising the wrong IP), so OrcaSlicer can't reach the virtual printer.
You already have remote_interface_ip set to 192.168.0.161 in your virtual printer settings, but that setting currently only takes effect in proxy mode — in print queue mode (which you're using), it's ignored.
Let me fix that.
@maziggy commented on GitHub (Feb 10, 2026):
Please use branch 0.1.9b, set the interface in virtual printer settings and let me know if it works now.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@FoxxMD commented on GitHub (Feb 10, 2026):
I pulled the newest
0.1.9bimage and redeployed but there was no change in the IP used for cert/SSDP. Do I need to use0.1.9b2or0.1.9b5?@maziggy commented on GitHub (Feb 10, 2026):
Always the latest please
@maziggy commented on GitHub (Feb 10, 2026):
Normally I don't push beta Docker images. You're lucky that there is a 0.1.9b image availabale due to some tests.
When using a beta branch you need to rebuild the container locally with the updated code.
@FoxxMD commented on GitHub (Feb 10, 2026):
Understood. The current commit on that branch,
6ecc29de54, is not building.P.S. you might be interested in the github workflow I use for automating publishing docker images for pull requests or branches. I use it for my own non-trivial OSS project. It makes it much easier for end-users to test changes as all they need to do is specify the PR tag rather than build from source.
@maziggy commented on GitHub (Feb 10, 2026):
NO I usually don't push beta images. I have a complete pipeline.
Wait a few minutes. I'll release 0.1.9.