Quote from: grue on November 29, 2014, 05:28:19 PM

try my node 104.45.145.179 (hosted on microsoft azure, 100Mb/s connection)

Thanks

Code:

: bitcoind -connect=104.45.145.179 -daemon
: tail -f debug.log

2014-11-29 17:32:05 receive version message: /Satoshi:0.9.3/: version 70002, blocks=332162, us=0.0.0.0:32795, them=104.45.145.179:8333, peer=104.45.145.179:8333
2014-11-29 17:32:05 Added time data, samples 2, offset -1 (+0 minutes)
2014-11-29 17:35:35 ProcessBlock: ORPHAN BLOCK 0, prev=000000000000000005d8f98093bfcd77fe473cc195ca4bc3ece2a77291fdf7ac
2014-11-29 17:36:09 ProcessBlock: ORPHAN BLOCK 1, prev=0000000000000000131bd22a1e2b53594c5589af93d9ebe34d4027777b1131c8

Then nothing.

Second try with bitcoin-qt, because I saw bitcoind did not open any ports (UPnP).

Code:

2014-11-29 17:46:59 receive version message: /Satoshi:0.9.3/: version 70002, blocks=332165, us=0.0.0.0:32805, them=104.45.145.179:8333, peer=104.45.145.179:8333
2014-11-29 17:46:59 Added time data, samples 2, offset -1 (+0 minutes)
2014-11-29 17:47:01 UPnP Port Mapping successful.

And stuck again.

Maybe it's my provider. But I fail to see how we then can handshake and orphaned blocks do get here.

So.. I installed a fresh new VPS with a huge pipe and scp'ed my initial setup and binaries.
I connected again to eldinhadzic.org (1000 Mb/s) which has been really whooshing blocks last night, and still nothing. Not blocking by IP it seems. Maybe it's my BTC address then..

Now my node is sync'ing with the network ok. I just hope this will be done before I reach my retirement age..

This, friends of BTC, is going nowhere fast.

Seems I'm done here. Not much help nor support. I will go now. Any mention of me in forums or press will be bogus. It has been one heck of a ride.. Gained some, lost everything again. But it has been fun by all means.

Hmm.. They even 'jacked my old nick.

Shrike.

PS. My IP here has been obfuscated by the system of an old friend. Don't bother him, hm?