The domain bitcoin.org resolves to that IP address. Could it be some
update check together with a circular redirect? That could at least
explain the large number of connection attempts.
--
Christian Decker
On Sun, Mar 2, 2014 at 9:56 PM, Wladimir wrote:
>
> On Sun, Mar 2, 2014 at 7:34 PM, James
Didn't mean that bitcoind was connecting over port 443. I didn't even get a
chance to compile. I was literally just finished downloading the tar.gz
file when my server was terminated.
Still trying to convince them I wasn't attacking anyone so they can
re-enable the server.
Thanks,
--
James Hartig
On Sun, Mar 2, 2014 at 7:34 PM, James Hartig wrote:
> Heads up... downloaded the linux tar.gz to my OVH box and got my server
> terminated. Screenshot from the email:
> http://cl.ly/image/3q0C2a3Y0T0V
>
> They claimed I was attacking 88.198.199.140 over port 443.
>
Sounds very unlikely that bitc
Heads up... downloaded the linux tar.gz to my OVH box and got my server
terminated. Screenshot from the email:
http://cl.ly/image/3q0C2a3Y0T0V
They claimed I was attacking 88.198.199.140 over port 443.
Thanks,
--
James Hartig
Software Engineer @ Grooveshark.com
http://twitter.com/jameshartig
4 matches
Mail list logo