dashed-slug.net

This is a network issue. It would only occur if your server is unable to retrieve the following URI:

https://poloniex.com/public?command=returnTicker

I will make the code a little more robust to cater for that. Does the 500 error persist when you switch to any other provider?

Thanks. Did you try enabling a different provider in the exchange rates settings?

If you are in a production environment you should be able to downgrade to 2.13.7 until this is resolved, if it is indeed a bug in the plugin. There were no DB schema changes so there should be no problem to downgrade.

I would like to know the following:

1. Does the “Legacy APIs” option help?

2. Which coin adapter(s) are you using?

3. Can you use your browser to inspect the XHR requests from the frontend to the server? What are the response payloads? If you cannot do this, can you let me login to a site where the problem occurs so I can have a look?

thanks

Thank you both for reporting.

I am having trouble reproducing this on my end.

Can you please tell me if the problem persists when you:

1. Clear your browser’s cache and reload the page (long shot)

2. Go to Wallets -> Frontend settings -> and enable the Legacy APIs option?

let me know please

thanks

Hello,

I have not tested the plugin with Bitcoin unlimited, but is should work with it.

The issue here is that the plugin has retained deposit addresses from earlier when you might have tested the plugin with testnet. The address you report is not a bitcoin address, but a Bitcoin testnet address. See here for version 111: https://en.bitcoin.it/wiki/List_of_address_prefixes

Unfortunately there is no easy way currently to generate new addresses from within the plugin, although I do have plans to add this in soon. The upcoming version 3.0.0 lays the ground work for this to be possible, because it introduces a more flexible PHP API that will allow this.

In the meantime, you should go to your MySQL database (perhaps via phpmyadmin) and delete all your BTC deposit addresses. This will force the plugin to regenerate them. Assuming the table prefix in your db is wp_, here’s how you’d do it:

DELETE FROM wp_wallets_adds WHERE symbol='BTC';

Let me know if this resolves your issue.

kind regards

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;' http://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

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.

Thanks for reporting.

I am not exactly sure how this or even the previous error you had could occur. I do not think it has anything to do with the balance of any coin.

Address validators are normally used whenever you type in a withdrawal address in the [wallets_withdraw] UI.

Could you please tell me more about what you were doing when this occurred?

1. Do you have the Bitcoin core node enabled in addition to enabling Bitcoin in the CoinPayments platform? (You should only have one adapter per coin enabled.)

2. Does the error appear when your first load your wallets page, or when you attempt a withdrawal?

3. Which browser are you using?