Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[1.3.10rc2] Exception in is_lan_address nukes all requests #2897
What were you doing?
1 set up a reverse proxy (i use reverse proxy with synology server)
What did you expect to happen?
What happened instead?
i get an error 500 :
Did the same happen when running OctoPrint in safe mode?
Version of OctoPrint
Operating System running OctoPrint
Printer model & used firmware incl. version
Link to octoprint.log
Link to contents of terminal tab or serial.log
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 discourse.octoprint.org. 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 2018-11-30 12: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.
Thanks. So this is a bit weird because the referenced line numbers in the stack trace don't match the source code in 1.3.10rc2.
I can see what might be happening here though and fix that.
Could you shoot me the output of
With that you actually just disabled the ip check (it expects a dictionary here, not a single boolean, so you basically gave it invalid config data which it now ignores). You didn't fix the problem, you hid it, and hiding problems isn't the goal here ;)
added a commit
Nov 16, 2018
changed the title from
reverse proxy with domaine name error with 1.3.10RC
[1.3.10rc2] Exception in is_lan_address nukes all requests
Nov 16, 2018
referenced this issue
Nov 16, 2018
mmm i reinstall octoprint with the 1.3.10RC2 with that :
the command : python -c "import netifaces; print(repr([netifaces.ifaddresses(interface) for interface in netifaces.interfaces()]))"
for the other command, i will send you the result to your email.
Weird, that's still a line number that doesn't make sense. The code at that location doesn't contain the cited command. Huh.
Not surprising, you need to run it in OctoPrint's python environment - that's why I added the second one which takes care of this ;)
Thank you, got it. Weirdly though I cannot make that data cause an error. In any case, I've made the whole
no problem, as soon as the RC3 will be available, I will test, and I will make a return on this post.
No, please create it now ;) If there's even the chance of an issue I need to look into that now, I'd rather not have to keep putting out RCs solved issue by solved issue, it's a tremendous amount of work each time, so the goal is to keep the number of RCs as low as possible and that means fixing ALL issues that are observed per RC if possible.