My H2C will sometimes unbind from my user ID. Once it does that, I get a -6010 error in Bambu Studio. Bambu Studio will still login to the printer, but the printer won’t transfer any info over to Bambu Studio. If I look on the printer console, I can see that I’m logged in … I just can’t use it from Studio. I tried connecting using an access code, but that did the same thing. I also ran the WiFi tests from the printer console and both worked flawlessly. So I opened a ticket with this info and the log file in it.
Bambu’s response: Are you sure your internet is working? Can you test your phone’s HotSpot?
Really? Did you not read the ticket about me testing the WiFi? Do people REALLY run their printers from cell phone HotSpots? I can’t even imagine doing that. I’ve got 1Gig fiber to my house.
Why is Bambu support so ludicrously bad?
The solution, by the way, because Bambu Studio and their cloud service are so bad, is to login again to the printer using Bambu Handy from your phone. It will then, magically, rebind the printer to your user ID. After that, you can go back to Bambu Studio and that will now work as well. I’m not sure why Bambu Studio can’t rebind a printer that it can obviously still login to … but I shouldn’t be surprised I guess. Maybe the people at Bambu run their entire operations from their cell phones and so do everything from Bambu Handy. I would rather shoot myself.
1 Like
99% of the time it’s just either DNS or your isp doing shady stuff, or you have bad wifi signal that you don’t know of, even if you tested it and it seem to be working, it’s not a guaranteed thing.
1 Like
Exactly that.
Which is why a network test usually isn’t helpful in this case. It’s often down to the provider’s DNS, which is often poor quality, and the fiber connection is not the relevant factor if the DNS doesn’t resolve it.
The only thing that helps is to ping the Bambu Cloud directly to see if it is reachable. If necessary, change the DNS or use a VPN.
Why did it work with the phone? No idea, but my guess is that if it can’t reach the address at youre home network, it should use mobile data network and thus bypass the problem. 
My provider often failed to resolve addresses, but it worked on my mobile phone. Eventually, I got fed up and switched to a different DNS.
1 Like
As mentioned previously, if your support request isn’t concise enough, you may receive inadequate responses. For example, avoid mixing different issues in the same request.
If you have conducted tests, please specify them in a list format rather than free-form text. You will receive much faster and more helpful responses this way. From my experience handling numerous support requests with varying degrees of professionalism, I’ve found that adjusting how I formulate my questions significantly improves the quality of responses.
Regarding your specific problem: issues with Bambu Lab addresses can occur for many reasons. My firewall frequently detects unusual behavior from addresses connected to Bambu Lab, so my solution was to give Bambu Lab printers their own VLAN where they can operate without interfering with the rest of my devices.
I get how bad DNS can be. But when my phone is in my house, it’s on my WiFi and therefore being served from my DNS (Ubiquity and Synology as backup). So the DNS at the workstations and the DNS for WiFi nodes is the same. While I’m grateful that Bambu Handy was able to rebind my printer so that Studio could use it, I’m still at a loss as to why that would happen.
I wonder if I should enable direct mode and if that would solve the problem. It doesn’t happen often and so I was just dealing with it. My X1E runs in direct mode without issue.
Like I said, I can still login to the printer from Studio on the network. I just can’t get it to “connect”, which seems to mean “transfer it’s configuration info” in Studio when it loses its binding.
Perhaps the login takes place locally but the “connection” info moves over the cloud service.
A good start would be to read the comments and the many tips that have been given to you. How to find the problem and what to do about it. I have an idea why you had problems with support. 
Just to note …
The printer is connected to a WiFi AP (Ubiquiti U7 Pro Wall in a desktop stand) that is 8 feet away line of sight. A ping from my workstation (wired) to the printer yields …
Pinging 192.168.100.26 with 32 bytes of data:
Reply from 192.168.100.26: bytes=32 time=1ms TTL=64
Reply from 192.168.100.26: bytes=32 time=2ms TTL=64
Reply from 192.168.100.26: bytes=32 time=1ms TTL=64
Reply from 192.168.100.26: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.100.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
My internal DNS forwards external requests to Google DNS at 8.8.4.4 and 8.8.8.8.
I’m not sure how one pings the Bambu cloud directly other than using the test tool on the console of the printer to test the network and router forwarding.
The Bambu Wiki didn’t give me anything on this. Is there a DNS name for the Bambu cloud services that I could use to “ping directly” from my workstation or when “ping directly” was mentioned, did that mean just use the tool on the printer console?
I did find something called Bambu Connect which I’m downloading and installing. That seems like it could be a useful test tool in my case.
I think maybe the best path to figure this out before it happens again is to learn how to reproduce it reliably, if that’s possible.
I’m still thinking that Bambu Handy can do something that Studio can not. I’m not sure what that is. But when I got my X1E, I remember everything started with setting up in Handy before even loading Studio. Generally though, I don’t use Handy for anything.
When the issue happens and I run the network tests from within Studio, two of the tests fail. The system fails to properly lookup upload-file.bambulab.com and upgrade-file.bambulab.com. All of the other tests work fine.
If I open up a cmd window and do an nslookup, I can’t get addresses back for either of these. When I then set my resolver directly to Google DNS at 8.8.8.8, I also can’t get these to resolve.
So, still working on it. It seems to happen at random.
Apparently those two DNS entries are not relevant. Both fail whether the printer properly connects or not.
I do think this issue started after the update to the 1.01.02.00 firmware though.