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

Forwarding IPv6 connection receiving a cookie error #1571

Closed
fang64 opened this issue Nov 2, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@fang64
Copy link

commented Nov 2, 2016

What were you doing?

I bound OctoPrint to IPv6 via HAProxy and received a:
CookieError: Illegal key value: session_Pa000:1210:8121::3]

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)
354042b

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

https://gist.github.com/fang64/bef5acb77f99654911b28c87d341c0c7

Link to contents of terminal tab or serial.log

serial and terminal logs are empty.

Link to contents of Javascript console in the browser

http://i.imgur.com/P6i1zPE.png

Screenshot(s) showing the problem:

http://i.imgur.com/KdjOdVB.png

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented Nov 2, 2016

Hi @fang64,

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 - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

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!

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.

@foosel

This comment has been minimized.

Copy link
Owner

commented Nov 2, 2016

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.

@fang64

This comment has been minimized.

Copy link
Author

commented Nov 2, 2016

@foosel, I apologize for that, here is the gist of that.

https://gist.github.com/fang64/cabddca7e8bbe56fc86c26eed44ac3dd

@foosel

This comment has been minimized.

Copy link
Owner

commented Nov 7, 2016

Fixed in maintenance and devel branches. Will NOT make it into 1.2.17 but will be included in 1.2.18 and also the next RC for 1.3.0.

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