It alows down the site and made it unuseable

Hi,

If you need to disable the Bitcoin core node adapter without using the admin UI, you can delete the following WordPress option: wallets-bitcoin-core-node-settings-general-enabled

With wp-cli, you would go to your WordPress directory from the command line and do:

wp option delete wallets-bitcoin-core-node-settings-general-enabled

Having said this, the full node should not normally slow down your system. Instead it should be the fastest option available. If it slows your site down, this is usually an indication that there is a firewall that causes your connections to the wallets to time out.

Base on the issue of fire wall, is there a way I can check the connection to the server where I installed the bitcoin?

Thw bitcoin is installed in another different server other than the one my wordpress is running on.

You say that the coin adapter definitely works, but it is slow.

First, can you confirm that it is the only BTC adapter enabled? i.e. have you disabled Bitcoin in your CoinPayments adapter?

Then to test the connection, if you can connect via ssh to the machine that runs WordPress, then you can use curl to perform a manual getinfo RPC request. Here’s how: https://bitcoin.stackexchange.com/a/19839/8738

That is, do the following:

curl --verbose --data-binary '{"jsonrpc":"1.0","id":"curltext","method":"getinfo","params":[]}' -H 'content-type:text/plain;' https://rpcuser:[email protected]:8332/

replacing “rpcuser”, “rpcpassword” and the ip and port number as appropriate.

With the --verbose flag you should be able to see if there is a slowdown at any part of the transaction.

Hope this helps.

I followed your insteuction on the server I installed the bitcoin and get the following report…

$ curl --verbose --data-binary'{"jsonrpc":"1.0","id":"curltext","method":"getinfo","params":[]}' -H 'content-type:text/plain;' https://rpcuser:[email protected]:8332/
curl: option --data-binary{"jsonrpc":"1.0","id":"curltext","method":"getinfo","params":[]}: is unknown
curl: try 'curl --help' or 'curl --manual' for more information

Then I followed the instruction on the link you shared and get the following report…

~$ curl --data-binary '{"jsonrpc":"1.0","id":"curltext","method":"getinfo","params":[]}' -H 'content-type:text/plain;' https://rpcuser:[email protected]:8332/
curl: (6) Could not resolve host: rpcuser

Replaces the rpcuser and rpcpassword with my own user and password.

I then ran the codes from a different server where my wordpress site is hosted and get the same result.

These test were ran with the server IP address and 127.0.0.1 respectively with the same result.

• This reply was modified 6 years, 8 months ago by UgoDimma.

I moved my site to the same server I installed my bitcoin, configure it and get it up and running.
But why is it not working as expected on a site that is on a different site with botcoin for me?

It’s good to know that it’s working when WordPress and the wallet are on the same machine, but we do not know yet why it is slow when running on two different machines. Your curl command did not succeed in any one of these two attempts.

In the first attempt you should have a space right after “data-binary” and before the JSON data.

In the second case, for some reason curl interpreted rpcuser as your hostname, where it is actually your username. It is possible that you have an old version of curl. You could try to specify the username/password explicitly:

curl --verbose --user rpcuser:rpcpassword --data-binary '{"jsonrpc":"1.0","id":"curltext","method":"getinfo","params":[]}' -H 'content-type:text/plain;' https://127.0.0.1:8332/

This should give you an idea of whether the delay is on the DNS lookup, TCP handshake, server response, etc.

If you wish, try again and let me know if there is any delay when you run this from the command line.

kind regards

Ok.

Here is the reault…

* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* connect to 127.0.0.1 port 8332 failed: Connection timed out
* Failed to connect to 127.0.0.- port 8332: Connection timed out
* Closing connection 0
curl: (7) Failed to connect to 127.0.0.1 port 8332: Connection timed out

I replaced 127.0.0.1 with the IP of the server the bitcoin was installed on while runing the code from another server.

When it printed out Trying 127.0.0.1… which is the IP address of the server running bitcoin, it delays for like 80 seconds before it prints out the remaining information.

• This reply was modified 6 years, 8 months ago by UgoDimma. Reason: To update some spelling error

OK thanks for sharing your findings. This is the root cause of your problem.

“Connection timed out” is almost always caused by firewalls. Check your firewalls on the server where Bitcoin is running, or contact your host about this.