# OctoPrint 2.0.0rc1 - Product: OctoPrint (https://whatsnew.fyi/product/octoprint) - Vendor: Gina Häußge - Date: 2026-04-27 - Version: 2.0.0rc1 - Original notes: https://github.com/OctoPrint/OctoPrint/releases/tag/2.0.0rc1 - Permalink: https://whatsnew.fyi/product/octoprint/releases/2.0.0rc1 - Labels: Pre-release What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- - **changed** — OctoPrint now requires Python 3.9 or higher, dropping support for Python 3.7 and 3.8 - **changed** — The accessControl.trustedRemoteUser setting has been replaced with a list of trusted authentication proxies that must be configured in accessControl.trustedRemoteUser - **removed** — Numerous long-deprecated methods and endpoints have been removed, affecting third-party plugins and clients - **removed** — Calling octoprint without a subcommand is no longer supported; use octoprint serve to run the server instead

Click here if you want to help with OctoPrint's funding!

##### ⚠️ Important note on release candidates This is a **R**elease **C**andidate of OctoPrint. It is not a stable release: severe bugs can occur, and they can be bad enough that they make a manual downgrade to an earlier version necessary - maybe even from the command line. You should be comfortable with and capable of possibly having to do this before installing an RC. > [!NOTE] > Should you get stuck due to a plugin that got broken by this RC (due to removing deprecated things), remember that you can always access a recovery page at `/recovery/` that allows you to restart in safe mode! ##### 🔁 Feedback on this RC Please provide *general* feedback on this RC [in this ticket](https://github.com/OctoPrint/OctoPrint/issues/5373). An "All is working fine" is valuable feedback as well because it tells me people are actually testing this RC and just not finding problems with it. **If you run into any obvious bugs, please follow ["How to file a bug report"](https://github.com/foosel/OctoPrint/blob/master/CONTRIBUTING.md#how-to-file-a-bug-report)** - I need logs and reproduction steps to fix issues, not just the information that something doesn't work. Thanks! ###### Things to take a closer look at For this RC, these things should get a closer look while testing, if possible: - proper behaviour when using the included web interface as well as any third party clients at your disposal - printing via a serial connection - managing files on your printer's storage via a serial connection - If you have a Klipper/Moonraker based printer available: can you use it through OctoPrint when you install the [Moonraker Connector](https://github.com/OctoPrint/OctoPrint-MoonrakerConnector)? - If you have a Bambu based printer available: can you use it through OctoPrint when you install the [Bambu Connector](https://github.com/OctoPrint/OctoPrint-BambuConnector)? ##### ✋ Heads-ups ###### ☝️ OctoPrint 2.0.0 requires Python 3.9+ This release of OctoPrint requires **Python 3.9+**. Python 3.7 & 3.8, still supported by OctoPrint 1.11.x, are no longer supported. [Please also see this FAQ entry on OctoPrint's Python version requirements](https://community.octoprint.org/t/61076). ###### 🔐 A new setting is available to configure trusted authentication proxies So far, if you set `accessControl.trustRemoteUser` to `true` in your `config.yaml`, OctoPrint would trust any incoming `X-Remote-User` header. That could of course in theory be abused if your OctoPrint instance was reachable directly in addition through your trusted authentication proxy. In OctoPrint 2.0.0, the `accessControl.trustedRemoteUser` setting has been replaced with a list of trusted authentication proxies. This defaults to empty, but if you had `trustedRemoteUser` enabled it will get set to your list of configured trusted reverse proxies. OctoPrint will now only accept and evaluate the `X-Remote-User` header if the request it is seeing came via any of your configured trusted authentication proxies - which must also be among your trusted reverse proxies. If you are currently using the `accessControl.trustedRemoteUser` feature in OctoPrint, you will want to check whether your list of trusted reverse proxies is configured correctly & contains your trusted authentication proxy prior to upgrading. And once upgraded, you'll want to limit the list of trusted authentication proxies further to only those of your reverse proxies that actually provide authentication. ###### 🧩 Plugin authors need to check if they are still using any of the now removed deprecated features OctoPrint has been logging deprecations warnings for some of its A _[Truncated at 4000 characters — full notes: https://github.com/OctoPrint/OctoPrint/releases/tag/2.0.0rc1]_