<p>Can you check to see if 8333 is being used by bitcoin core?   Do a netstat -ab.   Have you checked for adequate diskspace?</p>

CC BY-SA 4.0
2023-02-05T13:00:02.217Z
Thanks for the suggestion. Disk space is not an issue, the disk that Bitcoin core is writing to has over 120GB of free space left. Upon inspecting the netstat result, bitcoin-qt.exe is connecting to ports 80, 8334, 61472, 61473, 61474, 61475 initially but later it does establish connections to concrete IPs with ports 18333 and 8333
nan
CC BY-SA 4.0
2023-02-01T21:48:36.817Z
2023-02-01T21:48:36.817Z
Coin Fabulator
<p>I suggest publishing debug logs for inspection. Additionaly, there may any of the options fix an issue:</p>
<ul>
<li><code>-reindex</code> (rebuild chain state and block index from the blk*.dat files on disk)</li>
<li><code>-datadir=&lt;dir&gt;</code> (specify another data directory),</li>
<li><code>-loadblock=&lt;file&gt;</code> (Imports blocks from external file on startup).</li>
</ul>
<p>There is the information invoked like this: <code>.\bitcoin-qt.exe --help</code></p>

CC BY-SA 4.0
2023-02-08T12:37:02.047Z
2023-02-08T12:37:02.047Z
Greg Tonoski
<p>An outbound-only node is more than enough to sync a node. No need to fiddle with that.</p>
<p>There are two steps to rebuild your chain. First, you need to sync with other nodes to get the latest header. Then, bitcoin-core reads all your local *.blk blocks and rebuilds its database.</p>
<p>You seem to be stuck at first stage and unable to sync with other nodes. I'd suggest to check on any firewalls or other network configuration that might block this process, as well as reverting to defaults on bitcoin-core, regarding network configuration.</p>
<p><strong>You can have port 8333 closed</strong> (or any other inbound port for that matter) <strong>and won't have any issues while syncing.</strong></p>

CC BY-SA 4.0
2023-02-09T23:09:39.953Z
2023-02-09T23:09:39.953Z
mrn_gomez
<p>I have Bitcoin Core 24.0.1 64bit on Windows 10 which is seemingly stuck on updating with the latest transactions. It seems also that I have port 8333 blocked (checked on <a href="https://canyouseeme.org/" rel="nofollow noreferrer">https://canyouseeme.org/</a>), but not sure if that's even relevant. I am receiving &quot;outbound&quot; traffic in the peers-view window. I tried chaging the port to 8332, 80 and other random ports in the bitcoin.conf file but to no avail. I also tried deleting the peers.dat file but also without any impact. This used to work last year, I would appreciate any info on how I can get this updated so I can transfer by BTC.</p>
<p><a href="https://i.sstatic.net/jEztj.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/jEztj.png" alt="https://i.sstatic.net/jEztj.png" /></a></p>

CC BY-SA 4.0
2023-01-31T17:29:17.287Z
How long has it been like this?
Pieter Wuille
CC BY-SA 4.0
2023-01-31T20:36:33.113Z
Where did you download Bitcoin Core?
Murch
CC BY-SA 4.0
2023-02-05T12:41:16.107Z
@PieterWuille - like this since November, like in the screenshot. I didn't notice until recently. I have the app open on WIndows startup
nan
CC BY-SA 4.0
2023-02-05T12:42:21.977Z
@Murch I just updated to the newest version to see if that would help, I got the updated .exe file from https://bitcoincore.org/
nan
<bitcoin-core>
Bitcoin Core not updating to latest block
nan
# Bitcoin Core not updating to latest block

(Asked by: username_0 on 2023-01-31)

I have Bitcoin Core 24.0.1 64bit on Windows 10 which is seemingly stuck on updating with the latest transactions. It seems also that I have port 8333 blocked (checked on <https://canyouseeme.org/>), but not sure if that's even relevant. I am receiving "outbound" traffic in the peers-view window. I tried chaging the port to 8332, 80 and other random ports in the bitcoin.conf file but to no avail. I also tried deleting the peers.dat file but also without any impact. This used to work last year, I would appreciate any info on how I can get this updated so I can transfer by BTC.

[![https://i.sstatic.net/jEztj.png](https://i.sstatic.net/jEztj.png)](https://i.sstatic.net/jEztj.png)

**Tags:** bitcoin-core

> **Comments:**
> **username_1**: How long has it been like this?  
> **username_2**: Where did you download Bitcoin Core?  
> **username_0**: @username_1 - like this since November, like in the screenshot. I didn't notice until recently. I have the app open on WIndows startup  
> **username_0**: @username_2 I just updated to the newest version to see if that would help, I got the updated .exe file from https://bitcoincore.org/  

---

## 3 answers

### Answer by username_3 on 2023-02-01. Score: 1

Can you check to see if 8333 is being used by bitcoin core? Do a netstat -ab. Have you checked for adequate diskspace?

> **Comments:**
> **username_0**: Thanks for the suggestion. Disk space is not an issue, the disk that Bitcoin core is writing to has over 120GB of free space left. Upon inspecting the netstat result, bitcoin-qt.exe is connecting to ports 80, 8334, 61472, 61473, 61474, 61475 initially but later it does establish connections to concrete IPs with ports 18333 and 8333  

---

### Answer by username_4 on 2023-02-08. Score: 0

I suggest publishing debug logs for inspection. Additionaly, there may any of the options fix an issue:

* `-reindex` (rebuild chain state and block index from the blk\*.dat files on disk)
* `-datadir=<dir>` (specify another data directory),
* `-loadblock=<file>` (Imports blocks from external file on startup).

There is the information invoked like this: `.\bitcoin-qt.exe --help`


---

### Answer by username_5 on 2023-02-09. Score: 0

An outbound-only node is more than enough to sync a node. No need to fiddle with that.

There are two steps to rebuild your chain. First, you need to sync with other nodes to get the latest header. Then, bitcoin-core reads all your local \*.blk blocks and rebuilds its database.

You seem to be stuck at first stage and unable to sync with other nodes. I'd suggest to check on any firewalls or other network configuration that might block this process, as well as reverting to defaults on bitcoin-core, regarding network configuration.

**You can have port 8333 closed** (or any other inbound port for that matter) **and won't have any issues while syncing.**


---

