Hi, can you check that the bitcoin port is open and accessible from where you have your WordPress running? Try connecting with bitcoin-cli or even just do a telnet from your WordPress machine to your bitcoin machine on port 8332. Check to see that you have the correct rpcallowip setting. rpcallowip should point to the ip of your wordpress.
Are you running bitcoind on a machine accessible from your WordPress machine? It could also be a firewall issue. Check what firewall you’re using on your webhost and open up the port.
I can’t really help you with your networking issue, this is a matter of setting up TCP connectivity, so you might be better off asking your hosting provider.
Let me know if you have any issues with using the plugin though.
the bitcoind is on a diff server than my wordpress hosting. How would i check if the port is open? and how can i try to connect via bitcoin-cli thats in the bitcoind server?
Hi,
It is not just a matter of checking whether the port is open. You need to check if the port is open from the WordPress server. The bitcoin.conf line
rpcallowip=YOUR_WORDPRESS_IP
means that the bitcoin daemon will only accept connections from that IP. This is essential for security.
My first thought would be to ssh to the WordPress machine and do telnet YOUR_BITCOIN_SERVER_IP 8332. This will probably fail for the same reason that the plugin fails to connect.
My best guess is that you have not opened up 8332 in your firewall. I do not know what firewall you have installed on your VPS, if any. You, or whoever is administering the server, should know this. Find this out first, and then look for how to open up a TCP port on that firewall. http://serverfault.com is your friend. For example, if you find out that you are using Unobtrusive Firewall, then it would be a matter of doing something like:
sudo ufw allow 8333/tcp
Don’t forget to restart your firewall after that.
Another possibility might be that your hosting provider is blocking that port, so check with them, too.
/wp-admin/admin.php?page=wallets-menu-wallets
Adapter Status
Not Responding: Dashed_Slug_Wallets_Coin_Adapter_RPC->get_balance() failed with status=”403″ and error=”HTTP_FORBIDDEN”
from telnet to 8332 everything is ok,
https://bitnodes.21.co/ show that on 8333 works fine.
$ telnet xxx.xxx.xxx.xxx 8332
Trying xxx.xxx.xxx.xxx…
Connected to xxx.xxx.xxx.xxx.
Escape character is ‘^]’.
HTTP/1.1 400 Bad Request
Content-Type: text/html
Connection: close
Date: Mon, 19 Jun 2017 21:51:05 GMT
Content-Length: 94
<HTML><HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD><BODY>
<H1>Bad Request</H1>
</BODY></HTML>
Connection closed by foreign host.
Hello,
OK what you are telling me is that there is no issue with the firewall. I assume you tried running the telnet command from the same machine that runs WordPress?
Before the coin adapter was failing with “Connection refused”.
Now you’re getting “403 – Forbidden”. This is progress, which means you must have done something right in the meantime!
Normally 403 means that you have not setup rpcallowip= correctly to match the IP of your webserver. If you had set the wrong username/password you would be getting “401 – Unauthorized”.
Can you email me your conf file to [email protected]? You can leave out the rpcuser= and rpcpassword= lines.
regards,
Alex
All now is working correctly. Thank you for your support, also by email.
Hey @vedova, I get the same error about connection refused, my wordpress hosting & node is in different server, I also update .conf file accordindly. My node can run `bitcoin-cli’ as well.
How do you fix the error? Hope can get a tips from you, thank you 🙂
@mumiea, did you check your firewall?
