{"action":"created","issue":{"url":"https://api.github.com/repos/weaveworks/discovery/issues/7","labels_url":"https://api.github.com/repos/weaveworks/discovery/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/weaveworks/discovery/issues/7/comments","events_url":"https://api.github.com/repos/weaveworks/discovery/issues/7/events","html_url":"https://github.com/weaveworks/discovery/issues/7","id":118958850,"number":7,"title":"Connection to Weave API refused","user":{"login":"bdentino","id":3820523,"avatar_url":"https://avatars.githubusercontent.com/u/3820523?v=3","gravatar_id":"","url":"https://api.github.com/users/bdentino","html_url":"https://github.com/bdentino","followers_url":"https://api.github.com/users/bdentino/followers","following_url":"https://api.github.com/users/bdentino/following{/other_user}","gists_url":"https://api.github.com/users/bdentino/gists{/gist_id}","starred_url":"https://api.github.com/users/bdentino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bdentino/subscriptions","organizations_url":"https://api.github.com/users/bdentino/orgs","repos_url":"https://api.github.com/users/bdentino/repos","events_url":"https://api.github.com/users/bdentino/events{/privacy}","received_events_url":"https://api.github.com/users/bdentino/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-26T02:20:59Z","updated_at":"2015-11-28T01:53:40Z","closed_at":null,"body":"I have weave discovery running and it seems to be registering it's ip address properly with the discovery backend, but whenever a peer is notified of a change it fails to notify weave via the api, showing a 'connection refused' error:\r\n\r\n```\r\nINFO: 2015/11/26 02:08:22.799458 [main] WeaveDiscovery version git-8d4b4ae68a58\r\nINFO: 2015/11/26 02:08:22.799564 [main] Will announce local address '192.168.44.10:6783'\r\nINFO: 2015/11/26 02:08:22.799682 [client] Starting Weave client: API at http://172.17.0.1:6784\r\nINFO: 2015/11/26 02:08:22.799724 [http] Waiting for HTTP interface eth0 to come up\r\nINFO: 2015/11/26 02:08:22.799839 [http] Interface eth0 is up\r\nINFO: 2015/11/26 02:08:22.803197 [http] HTTP API listening on 172.17.0.2:6789\r\nINFO: 2015/11/26 02:08:23.979432 [manager] Updates from 'token://<REDACTED>': 3 added, 0 removed...\r\nINFO: 2015/11/26 02:08:23.979476 [client] Notifying about '192.168.44.11' (API: 'http://172.17.0.1:6784/connect')\r\nWARN: 2015/11/26 02:08:23.979952 [client] Could not notify about '192.168.44.11': Post http://172.17.0.1:6784/connect: dial tcp 172.17.0.1:6784: connection refused\r\nINFO: 2015/11/26 02:08:23.979980 [client] Notifying about '192.168.44.12' (API: 'http://172.17.0.1:6784/connect')\r\nWARN: 2015/11/26 02:08:23.980139 [client] Could not notify about '192.168.44.12': Post http://172.17.0.1:6784/connect: dial tcp 172.17.0.1:6784: connection refused\r\n```\r\n\r\nThere's probably an obvious place to start debugging but I'm not sure where that is. Anyone have any suggestions?\r\n"},"comment":{"url":"https://api.github.com/repos/weaveworks/discovery/issues/comments/160237415","html_url":"https://github.com/weaveworks/discovery/issues/7#issuecomment-160237415","issue_url":"https://api.github.com/repos/weaveworks/discovery/issues/7","id":160237415,"user":{"login":"bdentino","id":3820523,"avatar_url":"https://avatars.githubusercontent.com/u/3820523?v=3","gravatar_id":"","url":"https://api.github.com/users/bdentino","html_url":"https://github.com/bdentino","followers_url":"https://api.github.com/users/bdentino/followers","following_url":"https://api.github.com/users/bdentino/following{/other_user}","gists_url":"https://api.github.com/users/bdentino/gists{/gist_id}","starred_url":"https://api.github.com/users/bdentino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bdentino/subscriptions","organizations_url":"https://api.github.com/users/bdentino/orgs","repos_url":"https://api.github.com/users/bdentino/repos","events_url":"https://api.github.com/users/bdentino/events{/privacy}","received_events_url":"https://api.github.com/users/bdentino/received_events","type":"User","site_admin":false},"created_at":"2015-11-28T01:53:40Z","updated_at":"2015-11-28T01:53:40Z","body":"I was eventually able to get this to work by explicitly providing an `--http-addr` option when launching weave, eg:\r\n\r\n```\r\nweave launch --init-peer-count 3 --http-addr 0.0.0.0:6784\r\n```\r\n\r\nTBH I don't fully understand the implications of doing this though, so I am still hoping someone more familiar with the weave project could enlighten me. It seems that the default option is to bind the HTTP api to `127.0.0.1:6784` when using fastdp, which i guess make it inaccessible to other containers? Am I doing something I shouldn't be by binding to `0.0.0.0` (e.g. raising security concerns, interfering with fastdp, etc)? Is there a 'more correct' solution to this problem of the `weavediscovery` container not being able to contact the weave router api?"}}