-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
client_addr not included in configuration file #73
Comments
After looking at this with a fresh pair of eyes, the |
I'm not actually sure that's going to help in my case. If I'm reading it correctly your PR would result me in having to redefine client_addr into the extra params? While I could certainly do that it feels unnecessarily redundant. I think the fix is to remove the conditional around adding client_addr:
becomes something more like
|
@dpetzel sorry about that I misunderstood your issue. :P On Thu, Nov 6, 2014 at 3:43 PM, dpetzel [email protected] wrote:
|
This does not match the code. Possibly relevant to sous-chefs#73.
Running into this same issue. I vote for having the conditional for the ui removed from accepting client_addr or being reworked as well. |
I am closing this out because of impeding #126 landing on master. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This is related to #72, but is a slightly different issue so want to treated it as such.
Based on the documentation the
client_addr
configuration element is what controls what IP's the service will bind to. When not set this defaults to 127.0.0.1. manually adding this element to the json configuration and restarting the service shows this to be the case.I think the
client_addr
attribute needs to get added to the copy param in order to have the service listening on all available interfaces. Setting thebind_addr
doesn't result in the service listening on anything except 127.0.0.1The text was updated successfully, but these errors were encountered: