Question 1

How to fix 'No connection adapters were found for git+https' error when installing an OctoPrint plugin from a VCS URL?

Accepted Answer

This is a known bug in OctoPrint's Plugin Manager (present since 2020, broken VCS URL handling). It is fixed in OctoPrint 2.0.0rc2 and later. Until you can upgrade, use the command line as a workaround: activate your OctoPrint virtual environment and run `pip install git+https://github.com/rfinnie/OctoPrint-BedCooldown.git@main`. This bypasses the Plugin Manager's faulty URL download logic.

Question 2

Why can't I move files from the local storage file list in OctoPrint 2.0.0rc1?

Accepted Answer

This is a known bug in OctoPrint 2.0.0rc1 where the file list's move command uses an incorrect destination path. It was fixed in PR #5399. Upgrade to OctoPrint 2.0.0 (stable) or later to resolve the issue. As a temporary workaround, use the upload manager to move files.

Question 3

Why is the Connect button disabled in OctoPrint 2.0.0rc1 after upgrading?

Accepted Answer

A logic flaw in connection.js keeps the button disabled once `connectionParametersValidated` becomes false, even if later checks would pass. Workaround: add a connector-specific override, e.g. for Bambu or Moonraker: set `self.onReevaluateConnectionParameters = (connector) => { if (connector !== 'bambu') return; return true; };`. The bug is fixed in 2.0.0rc2.

Question 4

How to fix 'Upload and Print' in OctoPrint 2.0.0rc1 only uploading but not starting the print?

Accepted Answer

This is a known bug in OctoPrint 2.0.0rc1 affecting printers like the Prusa Core One with firmware 6.5.3. Workaround: manually start the print after upload, or downgrade to the stable OctoPrint 1.10.0 version until a permanent fix is released. Check the issue tracker for updates.

Question 5

Why does OctoPrint get stuck in error state after attempting to connect without a serial port, and how can I fix it?

Accepted Answer

This is a known bug in OctoPrint 1.10+. If you try to connect when the printer is off and no serial port is detected, the system enters a persistent error state ('Error: No more candidates to test...'). Even after turning the printer on, connection remains blocked.

Workaround: Ensure the printer is powered on before clicking Connect. If using a PSU control plugin, increase the power-on delay to allow the serial port to appear before the connection attempt.

For plugin developers: you can prevent automatic connection attempts by checking if ports are available and the printer is not in a transitional state. Example code:
  is_ready = self._printer.get_connection_options()['ports'] and self._printer.get_state_string() not in ("Detecting serial connection", "Opening serial connection", "Connecting")

Alternatively, restarting OctoPrint after the printer is on will clear the error. A permanent fix is being tracked in the OctoPrint repository.

OctoPrint

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects