It’s time to get the next stable release 1.3.11 out of the door and as you all know, the first step towards that goal is always a first release candidate.

The full changelog is somewhat long again and packed with improvements and fixes of existing functionality, most of which this time is behind the scenes. Some highlights:

  • Create a backup of working config.yaml after successful startup, detect incomplete startups and set safe mode flag for next startup in such cases. The latter is a particularly helpful additional “safety belt” against situations where third party plugins cause the whole server to no longer start up, which has happened several times in the past.
  • Remove UI_API_KEY and API disabling. With the inclusion of the ForceLogin plugin that doesn’t serve a real purpose anymore in most cases, and it was only ever more of a rate limiting feature than an actual security measure anyhow. Plus it lead to a ton of false security alarms.
  • Two new plugin hooks:
    • octoprint.printer.sdcardupload to allow overriding the SD card upload functionality and
    • to allow adding new events.
  • Addition of a new Error Tracking plugin (opt-in only of course!) which in the future will hopefully make it easier to get error traces from installations in the field for further analysis, especially during the Release Candidate phase. See also the heads-up below.
  • Action Command Prompt plugin: Streamlining of the involved commands and protocol in collaboration with the Marlin Firmware project.
  • GCODE Viewer: Bring back the total number of printed layers (I know several of you have been waiting for this)
  • Cura plugin: Unbundled and renamed to “Cura Legacy”, see also the heads-up below.
  • Anonymous Usage Tracking plugin: Track firmware/communication errors, printer safety warnings and uptime of OctoPrint.
  • Updates of various third party dependencies - note that this slightly increases the duration of installing 1.3.11.
  • Various bug fixes, for example notifications in the UI taking up more vertical space than available, the API keys from the Application Keys plugin not properly working when access control is disabled, fixed caching headers on the UI that will hopefully mitigate some issues caused by browser caching, fixing some bugs in the Backup plugin and more.

There are also two heads-ups. One concerns the Cura slicing plugin which got unbundled and renamed to “Cura Legacy” as already mentioned:

Heads-up: 1.3.11 unbundles the Cura plugin

If you rely on the Cura Plugin for your workflow that so far was bundled with OctoPrint, be sure to install the Cura Legacy plugin that’s now also available on the plugin repository.

Once installed the Cura Legacy plugin will import the settings and profiles from the former bundled Cura plugin automatically on first start.

The other is about the newly introduced Error Tracking plugin which you should please enable on Release Candidates such as this one 🙂

Heads-up: 1.3.11 bundles a new Error Tracking plugin, please enable it on Release Candidates

The Error Tracking plugin is a completely separate plugin from the existing Anonymous Usage Tracking plugin. Its tracking is disabled by default. Its purpose is to collect error information from instances in order to allow better issue analysis especially during the Release Candidate phase, or when prompted after reporting a bug. Thus it will also ask you to enable it on start while subscribed to an RC release channel.

The plugin uses a instance, kindly provided to OctoPrint by

You can find the full changelog and release notes as usual on Github.

Special thanks to everyone who contributed to this release candidate, especially @agrif, @akraus53, @AndyQ, @CapnBry, @DanielJoyce, @devildant, @Fabi0San, @fake-name, @fieldOfView, @gloomyandy, @HarlemSquirrel, @hgross, @jubaleth, @melgish, @rgriebl and @tedder for their PRs.

As the past RCs have shown me that a lot of people appear to be unaware of this: Please do not install this RC if you expect a fully stable version. It is not a stable release, it is a release candidate: severe bugs may occur, and they might be bad enough that they make a manual downgrade to an earlier version necessary - maybe even from the command line.

You should feel comfortable with and capable of possibly having to do this before installing an RC.

If you want to and can help test this release candidate, you can find information on how to switch to the “Maintenance RCs” release channel in this guide if not already done (also linked below).

Please provide feedback on this RC. For general feedback you can use this ticket on the tracker. The information that everything works fine for you is also valuable feedback 😄. For bug reports please follow “How to file a bug report” - I need logs and reproduction steps to fix issues, not just the information that something doesn’t work so make sure to fill out all fields of the issue template.


Depending on how the feedback for this release candidate turns out, I’ll either look into releasing 1.3.11 or fix any observed regressions and push out a new release candidate ASAP.