Why does Bitcoin Core(testnet) unable to connect to bitcoin network?

[Staizita]

I started bitcoin core for sync block yesterday, but it always stays in block 1435525 after several hours.
And Bitcoin Core shows that 0 active connection with Bitcoin network.

Bitcoin Core Version: v0.16.0(x64)

Why does Bitcoin Core(testnet) unable to connect to bitcoin network?
Is it possible that bitcoin core has been updated to 17.0 a few day ago? Or other reasons?

[1714057995]

1714057995

[nc50lc]

Bitcoin Core Version: v0.16.0(x64)

You should read the news just below the site header.

Here's the link to main thread: New info escalates importance: upgrading to 0.16.3 is REQUIRED
Better upgrade to 0.17.
Also, try to delete the latest blk.dat file (or the latest 5) inside the blocks folder, then try to sync again.

[Staizita]

As usual, please post your debug.log, bitcoin.conf/startup parameter and getnetworkinfo result so we can diagnose the problem.

My guess are :
1. Corrupted downloaded block / chainstate
2. Bad configuration on your desktop / router firewall
3. Unstable/very slow connection

my latest debug.log

Code:

2018-10-11 03:47:59 GUI: Platform customization: "windows"
2018-10-11 03:47:59 GUI: PaymentServer::LoadRootCAs: Loaded  37  root certificates
2018-10-11 03:48:10 Loading addresses from DNS seeds (could take a while)
2018-10-11 03:48:10 0 addresses found from DNS seeds
2018-10-11 03:48:10 dnsseed thread exit
2018-10-11 04:19:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2018-10-11 04:30:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2018-10-11 04:40:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2018-10-11 04:51:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2018-10-11 05:01:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2018-10-11 05:12:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2018-10-11 05:22:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2018-10-11 05:33:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2018-10-11 05:43:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2018-10-11 05:54:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2018-10-11 06:04:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 8190 seconds ago)
2018-10-11 06:15:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 8820 seconds ago)
2018-10-11 06:25:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 9450 seconds ago)
2018-10-11 06:36:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 10080 seconds ago)
2018-10-11 06:46:51 Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago)
2018-10-11 06:47:13 GUI:   OpenType support missing for script 12
2018-10-11 06:47:13 GUI:   OpenType support missing for script 12
2018-10-11 06:47:13 GUI:   OpenType support missing for script 12
2018-10-11 06:47:13 GUI:   OpenType support missing for script 12
2018-10-11 06:47:13 GUI:   OpenType support missing for script 11
2018-10-11 06:47:13 GUI:   OpenType support missing for script 11
2018-10-11 06:47:13 GUI:   OpenType support missing for script 11
2018-10-11 06:47:13 GUI:   OpenType support missing for script 32
2018-10-11 06:47:13 GUI:   OpenType support missing for script 32
2018-10-11 06:47:13 GUI:   OpenType support missing for script 32
2018-10-11 06:47:13 GUI:   OpenType support missing for script 32
2018-10-11 06:47:13 GUI:   OpenType support missing for script 19
2018-10-11 06:47:13 GUI:   OpenType support missing for script 19
2018-10-11 06:47:13 GUI:   OpenType support missing for script 19
2018-10-11 06:47:13 GUI:   OpenType support missing for script 19
2018-10-11 06:47:13 GUI:   OpenType support missing for script 20
2018-10-11 06:47:13 GUI:   OpenType support missing for script 20
2018-10-11 06:47:13 GUI:   OpenType support missing for script 20
2018-10-11 06:47:13 GUI:   OpenType support missing for script 20
2018-10-11 06:47:13 GUI:   OpenType support missing for script 16
2018-10-11 06:47:13 GUI:   OpenType support missing for script 16
2018-10-11 06:47:13 GUI:   OpenType support missing for script 16
2018-10-11 06:47:13 GUI:   OpenType support missing for script 17
2018-10-11 06:47:13 GUI:   OpenType support missing for script 17
2018-10-11 06:47:13 GUI:   OpenType support missing for script 17
2018-10-11 06:47:13 GUI:   OpenType support missing for script 17
2018-10-11 06:57:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 11340 seconds ago)

bitcoin.conf(The attribute values of rpcuser and rpcpassword were removed)

Code:

testnet=1
server=1
rpcuser=
rpcpassword=
prune=2000

#Tor Connect
proxy = 127.0.0.1:9050 
listen = 1 
bind = 127.0.0.1

The network is normal

[Staizita]

Here's the link to main thread: New info escalates importance: upgrading to 0.16.3 is REQUIRED
Better upgrade to 0.17.

All right.
Thanks for your suggestion!

[bob123]

This seems like a DNS error.

Currently there is a DNSSEC root key rollover. Today is the day where the old root key is being invalidated.
The new one is already active for months.

Do you run your own DNS server ? If so, you have to do this mannually.
If you are using a DNS server inside of your network, contact the administrator.
And if you are using the DNS server of your provider, they didn't change it yet. In this case, switch to googles: 8.8.8.8 or 4.4.4.4.


This might be not the reason, but would be very plausible. Does anything else work as expected ?
Try to visit a site you never visited before (to make sure DNS works - and IP address it not taken from DNS cache).

[jackg]

If you are using a DNS server inside of your network, contact the administrator.

Emmm.
It seem is a DNS server error.
Beacause another classmate who uses the same DNS server address also can't sync blocks.

THX!

Are you at a university/college, they might have banned nodes under their AUP (I'm unable to run a bitcoin node and have found no way around it yet).... Although, I think my laptop has done something to bypass the system as it now says the last updatetip on my debug.log was 9/10 (9th october).

[bob123]

(I'm unable to run a bitcoin node and have found no way around it yet)..

What are you going to do now?

If the administrator restricts the access to/from special ports/addresses, the easiest way would be to either setup a VPS or route the traffic through another network (e.g. your home network).

Using a VPN to route the traffic to your home network is the most elegant way to circumvent their measurement.
The traffic will be encrypted and is not recognizable as bitcoin-related traffic. Just some 'random' data to/from your home network.