<p>The message </p>

<pre><code>potential stale tip detected, will retry extra outbound peers
</code></pre>

<p>is associated with at least two situations:</p>

<ul>
<li>A firewall is blocking port 8333 and your node cannot communicate with peers.</li>
<li>Problems with genesis block (delete blocks and chainstate directories and restart).</li>
</ul>

CC BY-SA 4.0
2019-11-16T07:29:05.517Z
Thank you. It was in fact that my ROUTER had a FILTER, set to medium, that was just allowing in some popular known ports. When I set it to Low, My server then started to see peers immiedietely. Just weird how the router chose to implement this firewall this way. It did not honor the fact that I forwarded the port.
Norman Bird
CC BY-SA 4.0
2019-11-15T11:24:50.297Z
2019-11-15T11:24:50.297Z
RedGrittyBrick
<p>So it is not clear to me if my bitcoin server is syncing and all is fine or if the "potential stale tip detected, will retry extra outbound " message means I have to do something. Searching for that string does not actually provide me an answer. I thought Bitcoin full node install would be a bit more intuitive. Any help appreciated</p>

<p><strong>Solution Update:</strong>
My server was not connecting to peers because my ROUTER had a FILTER, set to medium, that was just allowing in some popular known ports. When I set it to Low, My server then started to see peers immediately. Just weird how the router chose to implement this firewall this way. It did not honor the fact that I forwarded the port. </p>

<bitcoin-core><full-node><firewall>
Please take a look at my server print out to see if all looks well or if the repeating errors mean something is wrong
Norman Bird
# Please take a look at my server print out to see if all looks well or if the repeating errors mean something is wrong

(Asked by: username_0 on 2019-11-14)

So it is not clear to me if my bitcoin server is syncing and all is fine or if the "potential stale tip detected, will retry extra outbound " message means I have to do something. Searching for that string does not actually provide me an answer. I thought Bitcoin full node install would be a bit more intuitive. Any help appreciated

**Solution Update:**
My server was not connecting to peers because my ROUTER had a FILTER, set to medium, that was just allowing in some popular known ports. When I set it to Low, My server then started to see peers immediately. Just weird how the router chose to implement this firewall this way. It did not honor the fact that I forwarded the port.

**Tags:** bitcoin-core, full-node, firewall


---

## 1 answers

### Answer by username_1 on 2019-11-15. Score: 1

The message 
potential stale tip detected, will retry extra outbound peers

is associated with at least two situations:

A firewall is blocking port 8333 and your node cannot communicate with peers.
Problems with genesis block (delete blocks and chainstate directories and restart).

> **Comments:**
> **username_0**: Thank you. It was in fact that my ROUTER had a FILTER, set to medium, that was just allowing in some popular known ports. When I set it to Low, My server then started to see peers immiedietely. Just weird how the router chose to implement this firewall this way. It did not honor the fact that I forwarded the port.  

---

