PSA: Add a Full Node for just $19/year!

[cypherdoc]

hey,what does this tell you from one of my vps logs:

Tue, 18 Feb 2014 09:15:23 -0500 Node56.onlinenode.net NODEWATCH: VPS 7426 (107.161.182.117) (518826 pps during 5 second interval). Probably false-positive unless repeats.
Tue, 11 Mar 2014 18:43:56 -0400 Possible DoS VPS 7426 (107.161.182.117): 882609 pps during 180 second interval
Tue, 11 Mar 2014 18:57:41 -0400 Node56.onlinenode.net NODEWATCH: VPS 7426 (107.161.182.117) (468826 pps during 5 second interval). Probably false-positive unless repeats.
Tue, 11 Mar 2014 18:59:47 -0400 Possible DoS VPS 7426 (107.161.182.117): 458826 pps during 900 second interval
Tue, 11 Mar 2014 19:09:08 -0400 Possible DoS VPS 7426 (107.161.182.117): 882614 pps during 60 second interval
Tue, 11 Mar 2014 20:23:04 -0400 Possible DoS VPS 7426 (107.161.182.117): 258826 pps during 60 second interval
Tue, 28 Oct 2014 15:57:47 -0400 VPS 8826 (162.221.191.37) has 65021 conntrack sessions
Tue, 28 Oct 2014 15:58:38 -0400 SUSPENDING VPS 8826 (162.221.191.37); it has 65021 conntrack sessions
Tue, 28 Oct 2014 16:22:55 -0400 VPS 8826 (162.221.191.37) has 64827 conntrack sessions
Tue, 28 Oct 2014 16:23:47 -0400 SUSPENDING VPS 8826 (162.221.191.37); it has 64827 conntrack sessions

am i being ddos'd?  how do i stop it?

bump

[1714164621]

1714164621

[chek2fire]

I have problems today with two of my servers and one node in weloveserver and was down. I dont know what happen but after a ticket support are up and running again.

[allgoodthings1]

bump

I don't know enough to answer your issue/question.  But yesterday morning, this happened to me: I had all three of my WLS nodes go down within about an hour.  The support ticket response came back that I was under DDOS, and they would get them back up as soon as that cleared.  By late afternoon (and a few emails later) they were all back up, and they've been humming along fine since then. (Morblias was a real help to me in this, as before.)

[cypherdoc]

bump

I don't know enough to answer your issue/question.  But yesterday morning, this happened to me: I had all three of my WLS nodes go down within about an hour.  The support ticket response came back that I was under DDOS, and they would get them back up as soon as that cleared.  By late afternoon (and a few emails later) they were all back up, and they've been humming along fine since then. (Morblias was a real help to me in this, as before.)

this one of four nodes with WLS that has this recurring ddos.  maybe 15x repeatedly.  i've almost given up on it and haven't had it running for weeks.  support keeps telling me that i need to implement some security measure to prevent this but i have no idea what to do.

[axel2078]

bump

I don't know enough to answer your issue/question.  But yesterday morning, this happened to me: I had all three of my WLS nodes go down within about an hour.  The support ticket response came back that I was under DDOS, and they would get them back up as soon as that cleared.  By late afternoon (and a few emails later) they were all back up, and they've been humming along fine since then. (Morblias was a real help to me in this, as before.)

this one of four nodes with WLS that has this recurring ddos.  maybe 15x repeatedly.  i've almost given up on it and haven't had it running for weeks.  support keeps telling me that i need to implement some security measure to prevent this but i have no idea what to do.

I have no idea how the host is configured, but is the firewall turned on?

[allgoodthings1]

this one of four nodes with WLS that has this recurring ddos.  maybe 15x repeatedly.  i've almost given up on it and haven't had it running for weeks.  support keeps telling me that i need to implement some security measure to prevent this but i have no idea what to do.

You know, a while back I had persistent problems with one of my nodes -- and I requested WLS move my subscription for that to a different location.  They did, and that solved the problem.

[cypherdoc]

this one of four nodes with WLS that has this recurring ddos.  maybe 15x repeatedly.  i've almost given up on it and haven't had it running for weeks.  support keeps telling me that i need to implement some security measure to prevent this but i have no idea what to do.

You know, a while back I had persistent problems with one of my nodes -- and I requested WLS move my subscription for that to a different location.  They did, and that solved the problem.

fixed!

i didn't have ufw installed for some reason.

[allgoodthings1]

Have you noticed node connections running high the last few days?  I've been pushing close to 100 for a few days now, and occasionally going over 100 -- even with the bitcoind default set at 100.  Morblias just helped me turn up the max setting to 125 on one of my nodes, to test it with a still higher maximum.  We'll see if the recently beefed up subscription specs will handle it without a problem.

[cypherdoc]

Have you noticed node connections running high the last few days?  I've been pushing close to 100 for a few days now, and occasionally going over 100 -- even with the bitcoind default set at 100.  Morblias just helped me turn up the max setting to 125 on one of my nodes, to test it with a still higher maximum.  We'll see if the recently beefed up subscription specs will handle it without a problem.

4 nodes with an avg of about 70 connections.

[John (John K.)]

Following closely - I'm running a full node on my desktop now that never gets turned off, but I'm looking into getting this too.

[allgoodthings1]

Following closely - I'm running a full node on my desktop now that never gets turned off, but I'm looking into getting this too.

Great!  The superb pricing that kicked off this thread no longer works with the expanded size of the blockchain.  But, if you can get a good deal on a VPS somewhere, it's still a pretty efficient way to contribute to the network.  If you need help setting up a VPS for a full node, I think Morblias will still help with that, too.

[chek2fire]

Two days now i cant access my node through ssh. It seems to be offline. I have ask forr support but in this days they say that they look to my problem but nothing happens. Can i add to the node a brute force attack protection like fail2ban to protect the node from ddos attack?

[dserrano5]

Great!  The superb pricing that kicked off this thread no longer works with the expanded size of the blockchain.

The pull request 4701 implements autoprune and is stable enough to give it a try. Easy directions to build it are on reddit. Just add the "prune" parameter to the bitcoin.conf (e.g. "prune=19500" for a 20 Gb box) and you're set.

[chek2fire]

It seems that my last node and the server get bricked. I have ask for a new transfer to europe location and i have to do now a fresh install of the node.

[chek2fire]

I have transfer again the server to Uk location and i have setup once again from the scratch. Now i have a problem to see the web page and i only see the apache server page. I try to change the apache path to  /var/www but it didnt work. The strange think is that i can see the vnstat page without problem. Any idea?

http://185.38.44.64/vnstat/index.php?if=venet0&graph=large&style=light&page=d

[btceic]

Edit, it looks like rpc is not running correctly or the script/caller does not have the correct permissions to access the proxy url

Code:

>>> dir(access._get_response())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 163, in _get_response
    http_response = self.__conn.getresponse()
  File "/usr/lib/python2.7/httplib.py", line 1018, in getresponse
    raise ResponseNotReady()
httplib.ResponseNotReady

Hypothesis is correct:

Code:

root@fullnode:/# curl http://****:****@127.0.0.1:8332
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>Error</TITLE>
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=ISO-8859-1'>
</HEAD>
<BODY><H1>401 Unauthorized.</H1></BODY>
</HTML>

Need some help with this guys.

bitcoind is running fine

Code:

root@fullnode:/# bitcoind getinfo
{
    "version" : 90300,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 336975,
    "timeoffset" : 1,
    "connections" : 20,
    "proxy" : "",
    "difficulty" : 40640955016.57649231,
    "testnet" : false,
    "keypoololdest" : 1403450557,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
root@fullnode:/#

Issue running btc-update.py

Code:

root@fullnode:/# sudo python ./usr/local/bin/btc-update.py
Traceback (most recent call last):
  File "./usr/local/bin/btc-update.py", line 6, in <module>
    info = access.getinfo()
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 124, in __call__
    response = self._get_response()
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 170, in _get_response
    response = json.loads(responsedata, parse_float=decimal.Decimal)
  File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
root@fullnode:/#

Tried running the script manually, no luck

Code:

root@fullnode:/# python
Python 2.7.3 (default, Feb 27 2014, 19:58:35)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from bitcoinrpc.authproxy import AuthServiceProxy
>>> import time
>>> access = AuthServiceProxy("http://*****:****@127.0.0.1:8332")
>>> access.getinfo()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 124, in __call__
    response = self._get_response()
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 170, in _get_response
    response = json.loads(responsedata, parse_float=decimal.Decimal)
  File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
>>>

[cypherdoc]

Great!  The superb pricing that kicked off this thread no longer works with the expanded size of the blockchain.

The pull request 4701 implements autoprune and is stable enough to give it a try. Easy directions to build it are on reddit. Just add the "prune" parameter to the bitcoin.conf (e.g. "prune=19500" for a 20 Gb box) and you're set.

How successful is this?

[Sophokles]

Great!  The superb pricing that kicked off this thread no longer works with the expanded size of the blockchain.

The pull request 4701 implements autoprune and is stable enough to give it a try. Easy directions to build it are on reddit. Just add the "prune" parameter to the bitcoin.conf (e.g. "prune=19500" for a 20 Gb box) and you're set.

How successful is this?

I'd like to know this too. Anyone tried it?

[dserrano5]

[pull request 4701, autoprune]

How successful is this?

I'd like to know this too. Anyone tried it?

Why don't you try it?

[Sophokles]

[pull request 4701, autoprune]

How successful is this?

I'd like to know this too. Anyone tried it?

Why don't you try it?

I may. But I'd like to estimate the chances of success before spending time fiddling with custom builds of the client...