Bitcoin Sign up or log in to customize your list._ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote 1 down vote favorite Is it normal for the network to work without any ACCEPT rule?Because now my iptables have INPUT DROP, FORWARD DROP and OUTPUT DROP only port like ssh, http(s), 53 it's open.I don't add any rule for port 8333 and 9333 but it works and if I telnet (with this tool http://www.adminkit.net/telnet.aspx) port 8333 or 9333 I have an error message Connection failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond I add here all iptables rules http://notes.io/qZkF I tried to send btc from external source and I received it.In bitcoin.conf I have rpcport=9333 Netstat -tulpn tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 19626/nginx.conf tcp 0 0 127.0.0.1:9333 0.0.0.0:* LISTEN 3537/bitcoind tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2446/sendmail: MTA: tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 19626/nginx.conf tcp 0 0 0.0.0.0:5565 0.0.0.0:* LISTEN 2416/sshd tcp 0 0 0.0.0.0:11111 0.0.0.0:* LISTEN 8575/php tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2936/mysqld tcp 0 0 127.0.0.1:587 0.0.0.0:* LISTEN 2446/sendmail: MTA: tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 2440/memcached tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 3537/bitcoind tcp6 0 0 ::1:9333 :::* LISTEN 3537/bitcoind tcp6 0 0 :::5565 :::* LISTEN 2416/sshd tcp6 0 0 :::8333 :::* LISTEN 3537/bitcoind udp 0 0 127.0.0.1:11211 0.0.0.0:* 2440/memcached Last debug.log 2015-11-22 16:33:33 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=[xxxx:xxxx:x:xxxx::]:8333, peer=304 2015-11-22 16:34:01 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2015-11-22 16:34:01 keypool reserve 47 2015-11-22 16:34:01 keypool return 47 2015-11-22 16:34:11 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=350000, us=[xxxx:xxxx:x:xxxx::]:8333, peer=305 2015-11-22 16:34:11 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2015-11-22 16:34:12 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2015-11-22 16:34:31 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2015-11-22 16:34:38 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2015-11-22 16:34:44 ERROR: AcceptToMemoryPool: nonstandard transaction: dust 2015-11-22 16:34:53 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=350000, us=[xxxx:xxxx:x:xxxx::]:8333, peer=306 With PHP I use this $server = new jsonRPCClient("http://$user:$passwd@127.0.0.1:9333/"); Update: I think it's because I have these rules iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT Is it a good idea to close port 8333 and 9333?

bitcoind server php firewall up vote 1 down vote Telnet says 'Connection failed' which means others will not be able to connect to you.Your iptables is working as it should.You may be mistaken thinking that bitcoin is working without ACCEPT rule because you are seeing outgoing connections.g2play bitcoinYour netstat shows bitcoin is LISTENing but if iptables doesn't ACCEPT then it will never see any incoming connections.bitcoin mining htc oneTry netstat -na | grep 8333 and you will see only outgoing connections (source address: you).bitcoin handelenTo make your bitcoin node reachable to the outside world simply add a rule to accept 8333.bitcoin ipn

Note do NOT open 9333 !It's meant for local use only and you might lose your bitcoins if people get access to it (in fact you're better off disabling it if you're not using it).Your Answer Sign up or log in Sign up using Google Sign up using Email and Password Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service.bitcoin ireland taxNot the answer you're looking for?bitcoin coinbase inputBrowse other questions tagged bitcoind server php firewall or ask your own question.Last updated 4:30am 2016-02-11 GMT.Running a full node can help the Bitcoin network significantly.There's lots of benefits to running your own node and most people can run one at home.For those who can't, or for those that want to run an extra one, the options are usually limited to virtual private servers (VPS) or dedicated servers (expensive).

Enter seedboxes - usually inexpensive, but provide plenty of disk space and resources to run a full node.This gist provides a list of seedbox providers that you can run a full node on, confirmed and unconfirmed.It also provides instructions for setting up a full node as a regular user on these services.The instructions work on Feral Hosting, but should work just fine on a different seedbox provider or a VPS, dedicated server or AWS instance.Security on seedboxes, as with most shared Linux boxes, is usually adequate for most users, but please note that I recommend against using a seedbox with wallets you care about.You can, and most of the time you won't run into issues, but in general you should never put your wallet on a server that other people have access to.Use at your own risk!Also note that if someone else is running a Bitcoin daemon on the same box as you, you won't be able to run your full node on the default port (8333).You can get around this by setting a custom port.

However, having two nodes running on the same box is not particularly useful, as running your node on a non-standard port will greatly limit how many other clients will connect to you.These providers have been confirmed to work with the instructions below.Please contact me if you can add to the list or confirm whether a provider works with this gist.These providers should work, but have not been tested yet.It should simply say "Bitcoin server starting" and then fork off to the background.If you're having issues, here are some common problems and solutions.You can check for other users running Bitcoin daemons on your box by running this command If that command returns some results, you should ask to be moved to a different box.If your node is showing as "Unreachable" on the Bitnodes check node tool, you may not have port 8333 open.To open it, use iptables or equivalent.If you downloaded Bitcoin Classic beta 2 during the testing period, or even Bitcoin Core, you might want to upgrade to the first official release.