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

[1.4.0rc2] Appkeys request returns 500/Internal server error #3366

fieldOfView opened this issue Dec 2, 2019 · 3 comments

[1.4.0rc2] Appkeys request returns 500/Internal server error #3366

fieldOfView opened this issue Dec 2, 2019 · 3 comments


Copy link

@fieldOfView fieldOfView commented Dec 2, 2019

What were you doing?

I am trying to request an appkey.

curl -X POST -H "Content-Type: application/json" http://octopi.local:80/plugin/appkeys/request -d "{\"app\": \"Cura\"}"

What did you expect to happen?

I expect a 201 response and a Location header so I can continue with the appkey request and probing

What happened instead?

The curl command returns the following:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">                                                                                                 
<title>500 Internal Server Error</title>                                                                                                                
<h1>Internal Server Error</h1>                                                                                                                          
<p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>                                                                                                                                                 

The octoprint.log only shows the following error log, not why the error happened

2019-12-02 22:10:09,980 - tornado.access - ERROR - 500 POST /plugin/appkeys/request ( 132.71ms

Did the same happen when running OctoPrint in safe mode?


Version of OctoPrint

1.4.0 rc2

Operating System running OctoPrint

OctoPi 0.14, which has been updated to Stretch

Printer model & used firmware incl. version


Browser and version of browser, operating system running browser


Link to octoprint.log

Link to contents of terminal tab or serial.log


Link to contents of Javascript console in the browser


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



This comment has been minimized.

Copy link

@GitIssueBot GitIssueBot commented Dec 2, 2019

Hi @fieldOfView,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - that can be found at Go there for any kind of issues with network connectivity, webcam functionality, printer detection or any other kind of such support requests or general questions.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2019-12-16 23:40 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.


This comment has been minimized.

Copy link

@foosel foosel commented Dec 3, 2019

Great. My development environment was still on Py3 for an analysis, and this particular issue seems to be Py2 only, hence it slipped through. That's going to be fun for the next year or so...

foosel added a commit that referenced this issue Dec 3, 2019
And refactor key generation to be located in ONE central utility method
to avoid issues like that in the future.

Closes #3366

This comment has been minimized.

Copy link

@foosel foosel commented Dec 12, 2019

1.4.0rc3 has just been released

@foosel foosel closed this Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.