<p>I'm getting repeated</p>

<p>NetworkPlugin cni failed to set up pod \"POD_NAME\" network: unable to allocate IP address: Post <a href="http://127.0.0.1:6784/ip/LONG_HEX_ID" rel="nofollow noreferrer">http://127.0.0.1:6784/ip/LONG_HEX_ID</a>: dial tcp 127.0.0.1:6784: connect: connection refused"</p>

<p>errors in the kubelet log.</p>

<p>Lot's of questions on the internet with this error message, but I haven't found one where anyone actually says what is supposed to be accepting connections on that port. Which is frustrating because if I had that basic piece of info maybe I could figure out what to start/restart to get things working.</p>

<p>Using Kubernetes 1.10 with weave-net.</p>

Brent212
<p>as <a href="https://www.weave.works/docs/net/latest/faq/" rel="nofollow noreferrer">https://www.weave.works/docs/net/latest/faq/</a> states</p>

<blockquote>
  <p>Q: Which ports does Weave Net use (e.g. if I am configuring a
  firewall) ?</p>
  
  <p>You must permit traffic to flow through TCP 6783 and UDP 6783/6784,
  which are Weave’s control and data ports.</p>
  
  <p>The daemon also uses TCP 6781/6782 for metrics, but you would only
  need to open up this port if you wish to collect metrics from another
  host.</p>
  
  <p>The Weave Net daemon listens on localhost (127.0.0.1) TCP port 6784
  for commands from other Weave Net components. This port should not be
  opened to other hosts.</p>
  
  <p>When using encrypted fast datapath, make sure that underlying network
  does not block ESP traffic (IP protocol 50). For instance on Google
  Cloud Platform a firewall rule for allowing ESP traffic has to be
  installed.</p>
</blockquote>

<p>so you need to start with debugging your weave-net daemonset.</p>
