Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings, Logging, Download Icon(s) give 500: Internal Server Error #2501

Closed
b-morgan opened this issue Mar 20, 2018 · 4 comments
Closed

Settings, Logging, Download Icon(s) give 500: Internal Server Error #2501

b-morgan opened this issue Mar 20, 2018 · 4 comments

Comments

@b-morgan
Copy link

@b-morgan b-morgan commented Mar 20, 2018

What were you doing?

Attempting to download octoprint.log through the web interface (Settings, Logging)

  1. Click Settings
  2. Click Logging
  3. Click Download Icon next to octoprint.log

What did you expect to happen?

File would be downloaded

What happened instead?

500: Internal Server Error

Did the same happen when running OctoPrint in safe mode?

I didn't try as I'm in the middle of a print.

Version of OctoPrint

1.3.7rc1

Operating System running OctoPrint

Octopi 0.14

Printer model & used firmware incl. version

LulzBot TAZ 6, Marlin 1.1.5.71

Browser and version of browser, operating system running browser

Firefox Quantum 59.0.1 (64-bit) running on Windows 10 Pro (64-bit).

Link to octoprint.log

octoprint.log

Link to contents of terminal tab or serial.log

N/A (a print job is active)

Link to contents of Javascript console in the browser

Nothing there (I looked).

Screenshot(s)/video(s) showing the problem:

Screen is blank except for 500: Internal Server Error in the upper left corner.

Yes, I have read the FAQ.

@b-morgan

This comment has been minimized.

Copy link
Author

@b-morgan b-morgan commented Mar 20, 2018

Print finished, same thing happened in Safe Mode.

Rebooting OctoPi didn't help either.

@chippypilot

This comment has been minimized.

Copy link

@chippypilot chippypilot commented Mar 20, 2018

I tried this on a number of the files listed in Logs. All produced the same error.

@foosel

This comment has been minimized.

Copy link
Owner

@foosel foosel commented Mar 22, 2018

I refactored something in the server initialization for 1.3.7, and I think this is what causes this bug. Or rather, something I forgot during this refactoring. Good find!

foosel added a commit that referenced this issue Mar 22, 2018
Fixes #2501
@foosel

This comment has been minimized.

Copy link
Owner

@foosel foosel commented Mar 23, 2018

1.3.7rc2 was released earlier today which should fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.