I have the exact same issue.
Sometimes it will work after power cycling more often not.
When it does work it will work over WLAN, then the next print hangs at 99%, file usually shows up but studio says it failed. Then if I try and print again it hangs at 30% and says LAN failed. Same issue with support…
Can confirm that I have the same issue; especially on slightly larger files (we’re talking only 21MB or so but still). BS says it timed out (usually at 99%), whether I send it or print it from BS. But the file will end up on the printer anyway and can be started without issue from there. LAN-only mode. Power cycling doesn’t solve it (for long).
G-day. I was experiencing the exact same issue yesterday for the first time. The ‘send print job’ window would load to 30% and freeze. After a few hours I found a post on another thread that mentioned running a calibration in BS fixed the issue for this BL user. I thought it couldn’t be that easy because I had tried everything else without success. However, to my surprise running the calibration fixed the issue for me. Just thought I would share in hopes it helps others experiencing the same issue. All the best with it guys.
OK, guys, some update from me having this problem already.
For me it seems a timing problem. I mean, the problem occurs randomly, but the more time is between two prints, the more likely the error is shown up. Although I thought first, that the dialog has something to do with it - it does not.
I have a WLAN mesh setup here. I think by definition, this technical base should never interfere with application issues on a higher level.
And actually I have no evidence for my theory. I will try to investigate about that in future print processes.
This just started happening to me for the first time. Switching to LAN only mode appeared to work for me for now. We’ll see what tomorrow brings. Multiple printers having the same problem from X1C to A1 to A1 mini.
So ive had hangs and issues constantly for 2 years with my bambu’s. I’ve tried everything, lan’s, swapping unifi AP’s, moving all sorts of stuff to get the ap client balances happy, I even created a separate AP and ssid on an isolated channel. These use ESP32’s for wifi and those things dont always play well with ubiquiti gear. It occurred to me everyone’s talking about FTP being some sort of a problem. So I went into my firewall (UDM pro) and turned off the FTP contrack module. I went from not being able to print to ANY of my printers, to all of them. It had been working on and off for about a year (would die at 30%) but then recently it would just stop entirely at 10%. I wonder if the firewall was playing games with FTP traffic. Skimming the docs, it appears that its only supposed to affect lan to wan ftp, but its hard to ignore an hour of rebooting printers and computers and getting nowhere and then I uncheck a box on the firewall and everything magically works. I’ll probably get better data once my new palo comes in next week and the UDM pro goes away.
I bring this up because I see ALOT of people with ubiquiti gear having trouble with LAN only mode.
Wow, not even ONE reply from bambulab? Obviously they don’t care that they are selling a $1,200 doorstop. I’ve gotten exactly one print to work this week. Everything else is “FTP error” at 30% or 70% on print or at 99% on send.
So I may have the solution: turn off windows firewall for whatever network you are on (for me my home network is “public”) and try sending the print a few times. I did this after days of no prints and the very next print worked. I turned the firewall back on and the next print failed. I turned it off and then next print also failed, but I tried again and it worked. The next print after that worked too. So, I’m 90% sure this is the cause.
The next question is how is this the cause? My firewall settings allow 2 bambu programs through. My best wild guess is:
- I plugged my laptop into a monitor
- Windows automatically turns off notifications when you do that, doesn’t tell you, and leaves them off forever in “do not disturb” mode, even after you stop using the monitor, and doesn’t tell you. Because MS. (click the bell icon in the lower right corner and see)
- Defender notified me there was a change in a bambu executable after an update and I needed to reauthorize it, maybe?
- But windows blocked it
- So defender blocked the reply from the printer – a file named “verify_job” with the deceptive contents “just a test file” which completely disables printing. Because Bambu
It’s not windows firewall because I am on Mac with no firewall enabled. I’ve also reproduced it with multiple macs, Ubuntu 24.04, and multiple windows 11 machines. I’ve also sent them low level traces of me connecting directly over ftp, showing where it hangs (when it does) and they don’t care. It’s over their head and they don’t care to support LAN only mode anyway.
I haven’t recorded the traffic or reversed their software yet, is my suspicion correct that the printer attempts to connect to the computer and send the “test” file? And if so, are those ports open on your system? I doubt they are open by default, I wonder if opening them would help.
Also, can you use an FTP client to transfer files? That worked for me when their software wasn’t working. A barebones FTP client also provides SOOOOOOOOOOO many more features that hapless Bambu is in capable of providing: browsing files, downloading and viewing timelapse, uploading files, everything but printing.
I’m experiencing the same issue, but only with P1P printers. I’m running Ubuntu 24.04 on a Ubiquiti network. So far, the only solution that has worked for me is power cycling the printer.