Home SoLoPrint

SoLoPrint

Support and guides for SoLoPrint - cloud-based 3D printer management platform.

By Jeremy Smith

• 19 articles

[Getting Started] [Coming Soon] Downloading and linking the SoLoPrint Mobile App

Take SoLoPrint in your pocket While the SoLoPrint web dashboard is fully responsive and pristine on mobile devices via Safari or Chrome, we are actively developing native iOS and Android applications. Features coming to the Native App: - Push Notifications: Get instant vibration alerts when a print finishes, fails, or requires a filament change, bypassing email delays. - NFC Tag Scanning: Instantly assign a spool to a printer simply by hovering your phone over the spool's NFC sticker. - Background PiP: Watch your printer's WebRTC camera feed via a Picture-in-Picture window while surfing other apps. The native mobile companion app will be launching shortly. Please keep an eye on our changelogs!

Last updated on May 01, 2026

[Getting Started] [Coming Soon] Migrating your data from a legacy platform to SoLoPrint

Welcome to the future of 3D printing management Transitioning from platforms like SimplyPrint, OctoEverywhere, or Obico to SoLoPrint should be painless. We are actively building an automated Ingestion Wizard. What will the Wizard do? - Spool Sync: Export your filament inventory as a CSV from your old platform, and SoLoPrint will instantly map it into Filament Intelligence. - G-Code Porting: We will ingest your cloud G-Code repositories locally, retaining your file folder structures. - Telemetry History: Import your historical print logs to maintain your cumulative print hour statistics. If you are an enterprise print farm needing migration assistance immediately, please click "Contact Support" and we will help you map your database manually.

Last updated on May 01, 2026

[Bridge Connectors] What is the SoLoPrint Bridge Connector and why is it required?

The Secure Middleman The SoLoPrint Bridge is a lightweight Rust-based application that sits on your local network (usually installed directly alongside OctoPrint or Klipper on a Raspberry Pi). Why not connect directly? Your 3D printer and its OctoPrint server reside behind your home or business router's firewall. To access it from the beach using a mobile phone, you traditionally have two choices: 1. Open your router ports (Port Forwarding), making your printer susceptible to ransomware. 2. Set up a VPN. The Bridge ignores both options. Instead, it securely dials out of your network to the SoLoPrint cloud, establishing a persistent, encrypted WebSocket tunnel. The SoLoPrint Dashboard then communicates exclusively through this tunnel. Do I always need a Bridge? Yes, unless you are using Bambu Lab Cloud natively. However, if you wish to run your Bambu Lab printers in LAN-Only Mode to keep your files local, a Bridge on the same network is required to proxy the traffic.

Last updated on May 01, 2026

[Bridge Connectors] Step-by-Step: Installing the SoLoPrint Bridge on a Raspberry Pi

Installation Guide (OctoPi / MainsailOS) Most makers run their 3D printers using a Raspberry Pi. Installing the Bridge takes less than 2 minutes. 1. Get your Bridge Key On your SoLoPrint Dashboard, log in and navigate to Settings > Bridges & Hardware. Click Add New Bridge and copy the resulting bridge_key. 2. Connect via SSH Open a terminal on your computer (or PuTTY on Windows). Type ssh pi@octopi.local (or whatever your Pi's IP address is) and hit enter. Enter your password (usually raspberry). 3. Run the Installer Paste the following command into your terminal: curl -sSL https://raw.githubusercontent.com/SoLoVisionLLC/soloprint-bridge/main/install.sh | bash Follow the prompts to paste your bridge_key when requested. 4. Verify the Connection The script installs the Bridge as a systemd service so it auto-starts on boot. Head back to your SoLoPrint Dashboard. Within 30 seconds, your Bridge will show a status of Online. Your Pi is now securely tunneled.

Last updated on May 01, 2026

[Bridge Connectors] Step-by-Step: Installing the SoLoPrint Bridge on a Linux/Debian Host

Advanced Installation (NUCs, Micro PCs, Mini Forums) Many users prefer running Klipper arrays on x86 machines. The SoLoPrint Bridge natively supports Debian-based environments (Ubuntu, Mint, Debian). 1. Requirements - A Debian-based Linux distribution. - Sudo privileges. - curl installed. 2. Execution 1. Ensure you have copied a valid bridge_key from your SoLoPrint Settings > Bridges page. 2. Open your host's terminal. 3. Run the installer script: curl -sSL https://raw.githubusercontent.com/SoLoVisionLLC/soloprint-bridge/main/install.sh | sudo bash 4. Follow the prompt to paste your bridge_key. 3. Log checking If you ever need to debug the outbound tunnel from your host, you can trace the logs using: journalctl -u soloprint-bridge -f

Last updated on May 01, 2026

[Bridge Connectors] Generating, managing, and rotating remote Bridge Keys

Security Tokens The bridge_key is uniquely generated when you click Add New Bridge in the dashboard. This defines the cryptographic claim that limits hardware to your SoLoPrint Workspace. Rotating a Key If you suspect someone gained unauthorized access to your Pi and read the configuration file, you should rotate the key: 1. Go to Settings > Bridges & Hardware. 2. Click precisely on the ... menu next to the compromised Bridge. 3. Select Reset Key. 4. Important: Your Bridge will instantly disconnect and go Offline. You must SSH back into your hardware and update the /etc/soloprint/bridge.env file with the newly generated key, then execute sudo systemctl restart soloprint-bridge. Deleting a Bridge If you decommission hardware, selecting Delete Bridge from the dashboard instantly revokes the connection. All physical printers tethered to that bridge will also be archived in your statistics.

Last updated on May 01, 2026

[Bridge Connectors] Troubleshooting: Why is my Bridge showing 'Offline'?

Connectivity Issues If your SoLoPrint dashboard shows an Offline indicator next to your Bridge, our cloud has lost the WebSocket heartbeat. 1. Is the Pi Powered On? The most common issue is that the Raspberry Pi or host computer was powered off, lost Wi-Fi, or crashed. Ensure the green networking LEDs are blinking on the Pi. 2. Is the Service Running? SSH into your Pi (ssh pi@octopi.local) and check the daemon status: sudo systemctl status soloprint-bridge If it says failed or exited, there may be a configuration error. 3. Was the Key Rotated? If you recently generated a new token in the dashboard, the Bridge is attempting to authenticate with a revoked token. Update /etc/soloprint/bridge.env with the new key. 4. DNS Issues In rare cases, your Pi's DNS setting acts up, meaning it cannot resolve soloprint.app. Try ping google.com from your SSH terminal to ensure outbound internet functions correctly.

Last updated on May 01, 2026

[Bridge Connectors] Understanding WebRTC: How SoLoPrint securely streams video

Zero-Latency Cameras Explained Traditional 3D printing apps grab screenshots (JPEGs) of your webcam every few seconds and send them to the cloud. This provides terrible framerates and multi-second delays. SoLoPrint uses WebRTC. How WebRTC Works When you open your Dashboard, the Cloud uses signaling to negotiate a direct peer-to-peer data stream between your web browser and the SoLoPrint Bridge sitting near the printer. Once connected, the video stream traverses directly over UDP to your screen. It doesn't pass through our centralized database, ensuring massive bandwidth capabilities (up to 60fps 1080p) with latencies frequently under 200ms. Your Network's Role The bridge handles NAT traversal (STUN/TURN) automatically. Simply install the bridge, plug in your USB camera to OctoPrint or Mainsail, and WebRTC does the rest.

Last updated on May 01, 2026

[Bridge Connectors] Configuring enterprise network firewalls for SoLoPrint WebRTC/UDP traffic

Commercial Print Farms If your SoLoPrint array is deployed in a school or enterprise locked behind an aggressive firewall (e.g., SonicWall, Fortinet), your camera feeds may fail to connect, showing a perpetual spinning wheel. Why? Enterprise firewalls often block non-standard outbound UDP ports, which are required for WebRTC peer-to-peer tunnels. The Solution You must whitelist the outbound traffic to ensure the Bridge and your Browser can successfully negotiate the tunnel. 1. Whitelist Domains: Ensure that wildcard domains *.soloprint.app and *.solovisionllc.com are allowed outbound HTTP/HTTPS. 2. STUN/TURN Servers: Our signaling infrastructure operates out of standard WebRTC ports. Please ask your IT administrator to allow outbound UDP traffic on ports 3478 and 443 directed toward standard AWS STUN ranges. If strict UDP blocking remains in place, SoLoPrint will fall back to deeply routed TCP relays (TURN), which will function but may result in slightly higher latency.

Last updated on May 01, 2026

[Bridge Connectors] [Coming Soon] Configuring high-availability Bridges for print farm redundancy

Zero Downtime For enterprise customers managing 50+ printers on a single network, running a single Raspberry Pi as a SoLoPrint Bridge introduces a single point of failure. Coming Soon: Bridge Clustering We are developing a clustering architecture that will allow you to deploy the SoLoPrint Bridge on multiple edge nodes (e.g., three separate Raspberry Pi 4s) on the same subnet. If the primary node drops off the network, the secondary node will instantly assume the heartbeat and WebSocket duties for traversing your OctoPrint/Klipper HTTP data to the cloud. Stay tuned for the High-Availability beta release!

Last updated on May 01, 2026

[Printer Setups] Connecting an OctoPrint instance to SoLoPrint (Auto-Discovery)

The Standard Protocol If you run OctoPi on your 3D printer, adding the machine to SoLoPrint takes seconds. The Bridge connector auto-discovers OctoPrint instances responding on your local network (e.g. octopi.local). 1. Generating your OctoPrint API Key 1. Open your local OctoPrint web interface (usually http://octopi.local). 2. Click the Wrench icon to open Settings. 3. Navigate to Application Keys. 4. Click Generate and type "SoLoPrint". 5. Copy the resulting long alphanumeric string. 2. Linking the Printer in SoLoPrint 1. Head to the Printers page in the SoLoPrint cloud dashboard. 2. Click Add Printer. 3. The wizard will prompt you to select the Bridge running on the local subnet. 4. The Bridge will report back any available OctoPrint IP addresses. 5. Select your machine, paste the Application Key, and hit Save. Your printer's telemetry and live video will instantly appear in the cloud!

Last updated on May 01, 2026

[Printer Setups] Connecting a Klipper (Moonraker) instance to SoLoPrint

High-Speed Firmwares SoLoPrint fully supports Klipper via its underlying API daemon: Moonraker. Regardless of whether your frontend is Mainsail or Fluidd, the Moonraker port (typically 7125) must be accessible to the Bridge. 1. Discovering Moonraker If you installed the Bridge directly onto the Klipper-host Pi, discovery is automatic. 1. Go to the Printers tab on your SoLoPrint dashboard and click Add Printer. 2. Select Klipper/Moonraker. 3. Choose your Bridge. 4. If discovery fails, explicitly enter the local IP address (e.g., 192.168.1.55) and port 7125. 2. Entering the API Key If your Moonraker is secured with an API key (common for internet-exposed or secure arrays), paste it into the wizard. Otherwise, you can leave it blank. 3. Connect Click Connect. You should see live nozzle and bed temperatures appearing inside the SoLoPrint dashboard immediately.

Last updated on May 01, 2026

[Printer Setups] Connecting a Bambu Lab printer using Native LAN-Only Mode

Fully Local Bambu Integrations Bambu Lab’s cloud isn’t meant for enterprise control. By switching to LAN-Only Mode, SoLoPrint routes the G-Code exclusively through your local network Bridge, bypassing externally synced Chinese servers entirely. 1. Preparing the Machine 1. Walk to your physical Bambu printer (X1C, P1S, A1, etc.) and tap the Settings gear icon. 2. Tap the Network tab. 3. Switch LAN Only Mode to ON. 4. Note the displayed IP Address and the Access Code (PIN) shown on the screen. 2. SoLoPrint Integration 1. Go to Printers > Add Printer in the SoLoPrint Dashboard. 2. Select Bambu Lab (Native LAN). 3. Enter the IP Address and the Access Code you noted earlier. 4. Ensure you select the Bridge located on the same logical subnetwork as the Bambu machine (otherwise the multicast protocol will fail). 3. Verification You will instantly see native Bambu Lab features load into the SoLoPrint UI, including their proprietary camera streams routed through our WebRTC tunnel.

Last updated on May 01, 2026

[Printer Setups] Enabling MQTT protocols on your Bambu Lab X1C / P1S for SoLoPrint integration

Real-time Telemetry for Bambu SoLoPrint communicates with Bambu Lab printers over MQTT (Message Queuing Telemetry Transport), not HTTP. We essentially subscribe to a continuous stream of metrics broadcast by the machine itself. Is MQTT enabled? MQTT is permanently enabled on modern Bambu firmwares, but requires the Access Code for decryption. If you see 0°C for your temperatures, your Access Code is incorrect, or the printer is ignoring the MQTT handshake from the SoLoPrint Bridge. Ensure that you are not running two competing control interfaces (like HomeAssistant and Bambu Studio simultaneously) dragging down the physical printer's processing threads. Sometimes rebooting the physical Bambu Lab printer solves a stale MQTT connection.

Last updated on May 01, 2026

[Printer Setups] Linking multiple physical printers to a single SoLoPrint Bridge

The Hub-and-Spoke Model You do NOT need a separate Raspberry Pi or Bridge software installation for every printer. One Bridge can confidently handle the network proxying for dozens of 3D printers on the exact same subnet. How to link multiple 1. Install the SoLoPrint Bridge on a centralized computer or a dedicated Raspberry Pi on your local network (like a server closet). 2. Navigate to Printers > Add Printer in the dashboard. 3. Select that exact same Bridge from the dropdown. 4. Simply input the diverse IP Addresses of your scattered OctoPrint or Moonraker nodes (e.g., 192.168.1.5 and 192.168.1.6). The single Bridge securely fetches the HTTP/WebSocket strings from multiple endpoints and tunnels them all securely up to our cloud backend! Enjoy a much cleaner physical setup.

Last updated on May 01, 2026

[Printer Setups] Passing custom G-Code macros from the cloud to your local Klipper firmware

Controlling the Firmware Power users love writing custom macros in printer.cfg. SoLoPrint natively supports triggering these directly from the cloud UI. 1. Locating the Terminal Open the expanded view for your connected Klipper printer. Click the Terminal tab. 2. Macro Execution You can type standard G-Code commands directly (e.g. G28 to home) and watch the printer react in real-time on the camera feed. If you have custom macros listed in Klipper, type their exact name (e.g., CLEAN_NOZZLE or HEAT_SOAK). SoLoPrint's terminal instantly forwards this string through the Bridge's WebSocket to Moonraker, kicking off your custom sequence.

Last updated on May 01, 2026

[Printer Setups] Calibrating Z-Offset and Babystepping directly from your mobile dashboard

Mid-Print Perfect First Layers You no longer need to run back to the printer physical screen to fix a bad first layer squish. During an Active Print If your printer is connected and printing via OctoPrint or Klipper: 1. Open the SoLoPrint dashboard on your mobile device. 2. Tap the active printer. 3. Switch to the Controls tab. 4. Look for the Babystep (Z-Offset) up/down widgets. The Impact Tapping these buttons issues real-time micro-commands to the firmware (commonly M290 Z-0.01). You can watch the nozzle descend live onto your WebRTC camera interface, dialing in the perfect first layer completely from your couch.

Last updated on May 01, 2026

[Printer Setups] [Coming Soon] Connecting PrusaLink / PrusaConnect hardware

The Prusa Ecosystem For users deploying Prusa MK4s or XLs with the native PrusaLink board, integrating with SoLoPrint is currently under development. Our Upcoming Approach We are actively writing a native plugin component for the SoLoPrint Bridge that implements the PrusaLink HTTP digest authentication standard. Once live, you will be able to treat Prusa firmware exactly like OctoPrint or Bambu, seamlessly ingesting Live Z parameters, MMU statuses, and sending toolpaths from the Cloud Slicer directly to the Prusa board without switching software paradigms.

Last updated on May 01, 2026

[Filament Intelligence] What is Filament Intelligence and how does it calculate usage?

Stop Wasting Plastic Filament Intelligence is SoLoPrint's flagship inventory engine. As you print through the SoLoPrint platform, our cloud receives extrusion data (E-steps, filament density calculations) and deducts the exact gram weight used from your digital spool inventory in real-time. Why track by gram? Most slicing packages output G-Code stating exactly how many grams of plastic a job will require. Before dispatching a job from the Cloud Slicer, SoLoPrint cross-checks the job's requirement against the remaining weight of the spool assigned to your printer's hotend. The Math If a 24-hour helmet print requires 820g of PLA, but your assigned spool only has 750g remaining, SoLoPrint halts the job and flashes a warning. You can swap the spool before wasting 24 hours of plastic on a headless print.

Last updated on May 01, 2026