Closed jhmartin closed 10 years ago
I observed this as well, it seems a work around is to set the -o flag to '0.0.0.0' when starting chef-rundeck
@jhmartin the default bind host is localhost
. So this is really happening outside the scope of chef-rundeck. I'd also like to avoid having a default bind to all public interfaces.
Would it be good enough to include docs about this in the README?
Noting it in the README should be fine.
On an AWS EC2-Classic centos 6.4 host that has ipv6 enabled, chef-rundeck binds to just the ipv6 addresses and not ipv4. Disabling ipv6 in the kernel and restarting chef-rundeck resolves the issue.