New release: 1.4.2

This is a hotfix release to fix three bugs in 1.4.1 that sadly only were reported after the release candidate phase for 1.4.1.

Due to that the changelog is very short and only consists of three bug fixes:

  • #3674 - Fix a bug that prevents plugin installation via upload for plugins over 1MB in size.
  • #3676 - Work around an issue in a third party dependency causing server startup to fail if there are files in the watched folder and polling of the watched folder is enabled. Also further hardening against similar issues interfering with server startup.
  • #3678 - Fix a bug that prevents plugin installation via URL from servers that enclose the filename option in the Content-Disposition HTTP header in double quotes. Affected some plugins not hosted on Github.

Like every single release (and release candidate) of OctoPrint ever since early 2016 this was made possible only through your continued support of my work 💕


The heads-ups from 1.4.1 still apply, please read them carefully, they might impact you and how you use OctoPrint! Also see the Further Information and Links below for more information, where to find help and how to roll back.


Special thanks to everyone who contributed to this release and provided full, analyzable bug reports and pull requests, especially @osubuu for their PR!

Further Information

It may take up to 24h for your update notification to pop up, so don’t be alarmed if it doesn’t show up immediately after reading this. You can force the update however via Settings > Software Update > Advanced options > Force check for update.

If you get an error about “no suitable distribution” during update, please read this.

If you have any problems with your OctoPrint installation, please seek support on the community forum.


This is a companion discussion topic for the original entry at

There is an issue with 1.4.2 where it says the octoprint server is currently not running. please fix this.

@Ibrahim_Awe, You could help by opening an issue against OctoPrint following all the steps in the template and providing all the information requested (which includes logs).

Without more information than "currently not running" there's a good chance it "won't get fixed".


EDIT: I've done some further testing, and it has nothing to do with connecting or disconnecting during an operation. It is as simple as sending a m997, the gcode command for a board reset through the octo terminal. It will succeed sometimes, but more often than not, it'll hard crash the entire raspberry pi. Here's a sample of the crash output:

Message from syslogd@OctoPi4 at Aug 8 09:08:21 ...
kernel:[ 1084.410951] Internal error: Oops: 206 [#1] SMP ARM

Message from syslogd@OctoPi4 at Aug 8 09:08:21 ...
kernel:[ 1084.411335] Process kworker/0:2 (pid: 1366, stack limit = 0x8f51514e)

@Kokorone, My advice to you is the same as my advice to lbrahim_Awe in the post just above yours. If you open an issue and provide all the requested information, the odds of the problem getting fixed go up tremendously.

1 Like