Bambu Lab: Webcam not working guide

Welcome to the Quick Reference Handbook for the SimplyPrint Bambu Lab Integrations webcam support. We'll go over some of the basic requirements to check if everything is in order before potentially collecting important debug information you'll need to send over to us.

Each step in this guide will result in some information that will be relevant either later or for the final information piece that will help us keep track of what is going on. You can, for your own sake, keep track of this information in a makeshift document.

Make sure to read everything carefully so as not to miss anything.

Resetting everything.

A good practice before testing if a system is in a consistent state is to initially, before going over any checklists, to quickly and visually identify everything is in order: Are your printers connected, online, have the right settings for what you want (LAN-only mode vs Cloud-mode), connected to the same network as the client, visible in SimplyPrint?

This guide focuses on debugging when the webcam does not load, but everything else is fine. If you're experiencing more symptoms, the problem might be more general, and perhaps easier to fix, terminate this guide and find/open an appropriate ticket.

Once you've quickly visually identified this, power-cycle the printers you want to debug. Then, afterwards, gracefully reboot the device on which you are running the SimplyPrint client. At this point, after things have stabilised in a couple of minutes, is the system in the same state as before?

What we are asking is: Do the things that did work, still work (Printers are online and I can home them from SimplyPrint). And did the things that did not work, still not work (Webcam still does not load).

A side note on verifying if your webcam is loading on simplyprint.io

To check whether your webcam is loadable on SimplyPrint, navigate to simplyprint.io, and click on the printer you want to test.

1. If the webcam tab is not expanded, click the drop-down menu to expand it.
2. If the webcam tab now says "No webcam detected", click "Detect webcam".
3. If nothing happens after a while, go into the printer's settings in SimplyPrint (Gear icon on the same page) -> Modifications-> Webcam and enable "Has webcam", remember to click save.
4. No matter what, reload the page at this point.
5. Wait a couple of seconds (max 30 seconds) and see if your webcam loads

Reference this every time you need to check if your webcam works; you can skip straight to steps 4 + 5 after having made sure that Has webcam is enabled once.

Identifying your printer(s)

For each applicable printer, first collect the following information, which can all be found on your printer's display. To ease the collection of some of this information, taking pictures of it on the screen can make it easier.

Once you have this information for each of the printers that are relevant to debug, we can continue along. We will refer back to this information once in a while. You are also welcome to just look up the information when you need it in this guide.

• X1C/H2D: WiFi (connected) + WiFi IP (not empty / not all zero) + LAN-Only Liveview (enabled)
• P1S/P1P: WiFi (connected) + WiFi IP (not empty / not all zero)
• A1/A1 Mini: WiFi (connected) + WiFi IP (not empty / not all zero) + Video (enabled)

Identifying your SimplyPrint Bambu Lab Client setup

Once you have your printers checked out, we need to verify your client installation and setup.

First, gather information about the device running the SimplyPrint client:

Operating System Requirements

macOS

• Version: Which macOS version (e.g., Monterey 12.6, Ventura 13.2)
• Architecture: Intel or Apple Silicon (M1/M2, etc.)
• Find version: Apple Menu → About This Mac

Windows

• Architecture: 32-bit or 64-bit
• Version: Windows 7, 8, 10, or 11
• Find version: Windows key + R → type winver → Enter

Linux

• Get system info: uname -a
• Get OS details: cat /etc/os-release

Network Connection Details

Determine your network setup:

Get Your IP Address

Windows:

ipconfig | findstr IPv4

macOS:

ifconfig | grep "inet " | grep -v 127.0.0.1

Linux:

ip addr show | grep "inet " | grep -v 127.0.0.1

Once completed, check that your client and printers pass this list; if the checklist fails at any step, terminate the guide at that point.

1. Is the client running: Try to access http://localhost:8000 - if not, terminate this guide and follow a different one.
2. What version is the client on: Bambu Lab Integration: How to find your version number in the client
3. Are all your printers online and added?

• • With the same serial numbers
  • With the same IP addresses

4. Do any warnings appear here?
5. Are your printers online and responsive at simplyprint.io?

• • They can be homed/moved
  • Print start works

If all of this is correct, then check once again with the steps on checking your webcam in SimplyPrint to make sure they still are not operational.

Debugging the webcam

Finally, after a lot of setup, we can get straight to business. In essence, the goal of this section is not to fix your webcam but instead to understand where the issue occurs. There are three primary suspects.

1. The printer itself
2. The network between your printer and the client, firewalls on your network or your computer.
3. There is a bug in the client that makes your webcams not load.

Does the webcam load from Bambu Studio / Bambu Handy?

1. What program are you using to test this: Orca/BambuStudio/Bambu Handy?
2. Are you logged into your Bambu Lab cloud account here?
3. Can you load all of the webcams like this?
4. Are you running the application on the same device as the SimplyPrint Bambu Lab Client?

Webcam Port Information

Different Bambu Lab printers use different protocols for webcam streaming:

Authentication: All printers use the username bblp and the access code as a password.

Diagnostic Commands

Replace PRINTER_IP with your printer's actual IP address from your printer information table.

1. Port Scan - Is the Port Up?

Windows:

telnet PRINTER_IP 322
telnet PRINTER_IP 6000

macOS/Linux:

# Check RTSP port (X1C/H2D)
nc -zv PRINTER_IP 322

# Check camera port (P1P/P1S/A1)
nc -zv PRINTER_IP 6000

Example Outputs:

# Success
Connection to 192.168.1.100 port 322 [tcp/*] succeeded!

# Failure - port closed
nc: connect to 192.168.1.100 port 322 (tcp) failed: Connection refused

# Failure - network/firewall issue
nc: connect to 192.168.1.100 port 322 (tcp) failed: Operation timed out

2. Port Reachability - Debug Firewall Issues

Windows:

# Test connection and show routing
tracert PRINTER_IP
netstat -an | findstr :322
netstat -an | findstr :6000

macOS:

# Test network path and firewall rules
traceroute PRINTER_IP
netstat -an | grep :322
netstat -an | grep :6000
lsof -i :322
lsof -i :6000

Linux:

# Test network path and check local firewall
traceroute PRINTER_IP
ss -tulpn | grep :322
ss -tulpn | grep :6000
iptables -L | grep -E "(322|6000)"

Example Outputs:

# Successful traceroute
traceroute to 192.168.1.100 (192.168.1.100), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.234 ms  1.156 ms  1.089 ms
 2  192.168.1.100 (192.168.1.100)  2.345 ms  2.234 ms  2.123 ms

# Active connection found
tcp4       0      0  192.168.1.50.54321     192.168.1.100.322      ESTABLISHED

# No active connections
(no output - port not in use)

3. RTSPS Stream Test with FFmpeg (X1C/H2D Only)

macOS:

# Install ffmpeg if not present: brew install ffmpeg
ffmpeg -rtsp_transport tcp -i "rtsps://bblp:ACCESS_CODE@PRINTER_IP:322/streaming/live/1" -f null -

Linux:

# Install ffmpeg if not present: sudo apt install ffmpeg (Ubuntu/Debian)
ffmpeg -rtsp_transport tcp -i "rtsps://bblp:ACCESS_CODE@PRINTER_IP:322/streaming/live/1" -f null -

Replace ACCESS_CODE with your printer's actual access code.

Example Outputs:

# Success - stream working
Input #0, rtsp, from 'rtsps://bblp:12345678@192.168.1.100:322/streaming/live/1':
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: h264, yuv420p, 1920x1080, 30 fps
frame= 150 fps= 30 q=-1.0 Lsize=N/A time=00:00:05.00 bitrate=N/A speed=1x

# Failure - authentication error
[rtsp @ 0x...] method DESCRIBE failed: 401 Unauthorised

# Failure - connection timeout
[rtsp @ 0x...] Connection to tcp://192.168.1.100:322 failed: Operation timed out

4. Network Connectivity Verification

Ping Test (All Platforms):

# Basic connectivity test
ping -c 4 PRINTER_IP

Extended Network Test:

# Test different packet sizes to check MTU issues
ping -c 4 -s 1400 PRINTER_IP
ping -c 4 -s 1000 PRINTER_IP

Example Outputs:

# Success
PING 192.168.1.100 (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: icmp_seq=0 time=1.234 ms
64 bytes from 192.168.1.100: icmp_seq=1 time=1.156 ms
--- 192.168.1.100 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss

# Failure - host unreachable
PING 192.168.1.100 (192.168.1.100): 56 data bytes
Request timeout for icmp_seq 0
--- 192.168.1.100 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss

5. DNS and Local Network Resolution

Check if using hostname vs IP makes a difference:

Windows:

nslookup PRINTER_IP
arp -a | findstr PRINTER_IP

macOS/Linux:

# Check ARP table and DNS resolution
arp -a | grep PRINTER_IP
host PRINTER_IP
dig -x PRINTER_IP

Example Outputs:

# ARP table entry found
? (192.168.1.100) at aa:bb:cc:dd:ee:ff on en0 ifscope [ethernet]

# No ARP entry (device not reachable recently)
(no output)

# Reverse DNS lookup
100.1.168.192.in-addr.arpa domain name pointer bambu-printer.local.

Potential next steps based on issues:

• All tests pass: The Issue is likely in the SimplyPrint client
• Port scan fails: Check printer camera settings and network configuration
• FFmpeg fails but port scan passes: Authentication or printer service issue
• Network tests fail: Check network configuration and firewall rules

Sharing your results

The final step of this guide is to collect all the information you've been able to find on your own and share it with us. Afterwards, we'll provide you with custom debugging steps, or we'll find the issue from which we can publish a fix! It is important you are as accurate and inclusive of information as possible, potentially sharing 1:1 copy-pasted command outputs and screenshots of information. The more detailed you can make it, the easier it will be for us to notice the important details and provide you with a solution as fast as possible.

We'll want:

• The information from the printers you've tested collected from Identifying your printer(s)
• The information collected from Identifying your SimplyPrint Bambu Lab Client setup
• The full results from Debugging the webcam including:

1. Does the webcam load from Bambu Studio / Bambu Handy? (Yes/No and any error messages)
2. Port 322 test output (X1C/H2D) - copy/paste exact command output
3. Port 6000 test output (P1P/P1S/A1/A1 Mini) - copy/paste exact command output
4. Traceroute output to printer IP
5. Netstat/ss output for ports 322 and 6000
6. Any firewall rules found (iptables/lsof output)
7. FFmpeg command output (X1C/H2D only) - complete log with success/failure status
8. Basic ping test output (4 packets) with packet loss percentage
9. Extended ping test with different packet sizes
10. ARP table entry for printer
11. DNS lookup results (if applicable)

• Full client logs collected after you're done testing, see here on how to collect them: Bambu Lab Integration: Where to find your logs
• Anything else special about your setup:
• Like: Your router only supports X connections?
• Or: It stopped working after I upgraded my firmware/router/power outage.

You can share this information in a couple of different ways, the easiest is to collect a text document and related files into a single ZIP-archive, be sure to name it something memorable, and email it directly to us at javad.asgari@simplyprint.io or upload the files to something like Google Drive, or a private GitHub Gist and share the links via email, our livechat or on Discord.

Once shared, we'll collect a lot of similar reports to churn out a solution ASAP If you're interested in more testing, for instance, letting us inspect Wireshark traffic on your network, we have done so in the past to solve some types of problems, and might reach out regarding something like that.

But don't hesitate to involve us at every step in this guide; we are more than happy to help.

Updated on: 09/08/2025