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

Octoprint integration: 500 error #2481

Closed
PxT opened this Issue Jan 2, 2015 · 5 comments

Comments

Projects
None yet
3 participants
@PxT

PxT commented Jan 2, 2015

Slic3r 1.2.4
Mac OS 10.10.1

If I upload a very large gcode file (20MB) I get an error back:
Error while uploading to the OctoPrint server: 500 read timeout

I can upload the same file manually with no error.

@PxT

This comment has been minimized.

Show comment
Hide comment
@PxT

PxT commented Jan 2, 2015

screen shot 2015-01-01 at 10 46 57 am

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 2, 2015

Member

What OctoPrint version?

Member

alexrj commented Jan 2, 2015

What OctoPrint version?

@PxT

This comment has been minimized.

Show comment
Hide comment
@PxT

PxT Jan 2, 2015

Octoprint Version: 1.1.1 (master branch)

PxT commented Jan 2, 2015

Octoprint Version: 1.1.1 (master branch)

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 4, 2015

Member

I increased the timeout now. Works also with large files.

Member

alexrj commented Jan 4, 2015

I increased the timeout now. Works also with large files.

@alexrj alexrj closed this Jan 4, 2015

@alexrj alexrj added this to the 1.2.5 milestone Jan 4, 2015

@lordofhyphens

This comment has been minimized.

Show comment
Hide comment
@lordofhyphens

lordofhyphens Mar 27, 2015

Member

That got fixed months ago, and the version number you give makes no sense.
Use the master branch.
On Mar 27, 2015 5:40 AM, "twproject" notifications@github.com wrote:

I have the same problem in the devel branch
Version: 1.2.0-dev-687-g45bf398 (devel branch)


Reply to this email directly or view it on GitHub
#2481 (comment).

Member

lordofhyphens commented Mar 27, 2015

That got fixed months ago, and the version number you give makes no sense.
Use the master branch.
On Mar 27, 2015 5:40 AM, "twproject" notifications@github.com wrote:

I have the same problem in the devel branch
Version: 1.2.0-dev-687-g45bf398 (devel branch)


Reply to this email directly or view it on GitHub
#2481 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment