Solution: Verify that the entered Access Code is correct and the printer IP settings are properly configured. Ensure necessary ports (8883, 990, 322) are open. To correct the connection details, open the 3DPrinterOS Client web interface, click Edit printer list, and click Edit in the printer's row. If the printer still will not connect once the details are right, click Forget in that row and add it again.

Solution: Verify FTP ports (990, 50000-50100) are open. Update firmware to the latest version. If errors persist, restart the printer and client to clear transient network issues.

Solution: Confirm network connectivity and enable LAN Only Mode on the printer. Enter the IP address, Access Code, and serial number in the 3DPrinterOS Client. If issues persist, enable Verbose Mode, attempt to reconnect, and report the logs to support.

Solution: Open the 3DPrinterOS Client web interface, click Edit printer list, and click Edit in the printer's row to check the IP, Access Code, and serial number. If the printer still will not connect once those are correct, click Forget in that row and add the printer again.

Solution: Update the 3DPrinterOS client to the latest Beta version. Verify network settings, especially DNS and firewall configurations, to ensure uninterrupted connectivity.

Solution: Please refer to our camera troubleshooting guide.

Solution: Manually reassign the correct camera in printer settings within 3DPrinterOS printer settings.

Solution: Bambu printers fully support 3DPrinterOS with the latest firmware. Enable Developer Mode in printer settings to maintain compatibility with third-party services like 3DPrinterOS.

Solution: Disable filament tracking in printer settings within 3DPrinterOS Cloud. Use single-spool mode or manually select AMS slot at print initiation. 3DPrinterOS AMS guide.

Solution: Start the print with the Print button and assign each color to an AMS slot in the print options window before printing. A single-color job still needs its one color mapped to a slot. The Skip & Queue button does not send the AMS mapping table, and current Bambu firmware rejects a job started that way, which produces this error. If it continues after you map the colors through the Print button, enable Verbose Mode, reproduce the error, and send logs with Report Printer Issue. 3DPrinterOS AMS guide.

Solution: Set the external spool to the material the job needs in Printer settings, Advanced tab, under Printer Filaments, or on the printer screen, so the printer reports the correct type, for example PLA-S for Bambu Support For PLA. If the type will not change, make sure the spool is not mid-load, since the printer blocks changing an external spool's type while it is loading. At the print step, turn on the External Spool toggle for the extruder fed by that spool. The material picker there only lists AMS slots, so it looks empty for the external side, which is expected. Once the external material matches, the job queues.

Solution: Enable the auto-refill option via Bambu Studio or Orca Slicer before sending the job through 3DPrinterOS.

Solution: AMS slot selection is not supported when printing through the AutoQueue virtual printer. To print with a specific AMS slot, queue the job directly to the real printer instead.

Solution: Assign a static IP address to each printer by binding their MAC addresses in router settings to prevent IP changes after restarts.

Solution: Verify the printer's IP address is correct and set as static on your router to prevent changes after restarts. Restart the printer and the 3DPrinterOS Client, and ensure they are updated to the latest version.

Solution: Ensure network allows traffic on essential ports: MQTT (8883), FTP (990, 50000-50100), and camera streams (322 for X1/H2/P2 series, 6000 for P1/A1 series). If using advanced firewall rules, explicitly whitelist these ports.

The printer has no readable storage medium. The message says "SD card" on every model, including the ones that use a USB flash drive, so go by your printer model rather than the wording. Insert a working microSD card (A1, P1 and X1 families) or USB flash drive (H2D, H2D Pro, H2S, P2S and X2D), restart the printer so it mounts, and send the job again. If one is already inserted, reseat it or try a different card or drive you know is good.

Error 1007 means the 3DPrinterOS Client could not upload the file to the printer's storage. When a power cycle fixes it only until the next job, the usual cause is a card that is starting to fail rather than the network. Replace the card in one of the affected printers with a new high-quality one and check that it holds up over several prints. If a new card does not help, update the printer to the latest firmware, which you can check on the printer screen.

If uploads fail on every job from the start, check that ports 990 and 50000 to 50100 (FTP, used for uploading jobs) are open between the host and the printer.

This is usually a stale connection. Restart the 3DPrinterOS Client, or open the Client web interface, click Edit printer list, click Forget in the printer's row, and add the printer again. Restarting the printer after inserting the card or drive also helps.

The card or drive may be corrupted, full, or low quality. Replace it with a high-quality one formatted as FAT32, and make sure it has free space. Low-quality or inexpensive cards can cause corrupted data, print interruptions, and reduced card lifespan.

If you have attempted these troubleshooting steps and are still experiencing issues, please report the problem to provide us with detailed logs. You can do this from the Cloud by clicking the three dots beside your printer and choosing "Report Printer Issue"

or from the Client by clicking on "Report problem".

If you require additional assistance, use the support chat in the bottom right corner.