Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Forwarding IPv6 connection receiving a cookie error #1571
What were you doing?
I bound OctoPrint to IPv6 via HAProxy and received a:
What did you expect to happen?
The OctoPrint page should have loaded
What happened instead?
Internal Error 500 returned by the OctoPrint server.
Branch & Commit or Version of OctoPrint
Version: 1.2.16 (master branch)
Printer model & used firmware incl. version
Solidoodle 2 Pro, Marlin Firmware
Browser and Version of Browser, Operating System running Browser
Firefox 49.0.2 Ubuntu 16.04.1 LTS
Link to octoprint.log
Link to contents of terminal tab or serial.log
serial and terminal logs are empty.
Screenshot(s) showing the problem:
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.
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 2016-11-16 07:10 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!
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.
Can you please provide the haproxy configuration that you used for that? It looks like something is wrongly sent in the forwarding headers, causing part of the address to be interpreted as a port number and causing that issue.
Also, please never leave out parts from the ticket template.
@foosel, I apologize for that, here is the gist of that.