Virtual Printer Issues

Virtual Printer Issues

Virtual-printer features depend heavily on network reachability and port binding.

Slicer cannot find the virtual printer

Check:

• Printbuddy container is running.
• Linux Docker host uses network_mode: host.
• Required ports are not already in use.
• Workstation and Printbuddy host are on reachable networks.
• Firewall allows the virtual-printer ports.

Proxy mode does not forward

Check:

• The virtual printer has a target printer configured.
• The target printer is reachable and online.
• Proxy mode is selected instead of queue/review mode.
• Logs show no target-printer errors.

Queue/review jobs do not appear

Check:

• The slicer is sending to the Printbuddy virtual printer, not directly to the real printer.
• The selected virtual-printer mode is queue or review.
• Printbuddy logs show the incoming connection.

Diagnostics

Use the virtual-printer diagnostic action where available. It should verify enabled state, service state, bind interface, target printer, and port reachability.