forked from maziggy/bambuddy
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Windows Installer Issues
Marko@VMHOMELAB edited this page Jun 13, 2026
·
1 revision
Check:
- The install path has no restrictive permissions.
- Antivirus did not quarantine files.
- Required ports are free.
- The service account can read/write the data directory.
Verify that Printbuddy is running and listening on the configured port. Also check Windows Firewall rules for the selected port.
From the Windows host, test the printer API URL in a browser or PowerShell.
Examples:
Test-NetConnection <printer-ip> -Port 7125
Invoke-WebRequest http://<printer-ip>:7125/server/infoAdjust the port and URL for Bambu or PrusaLink printers.
Use the installer-created log path or Windows service logs to inspect startup and runtime errors. Redact secrets before sharing logs.