dashed-slug.net

Hello,

Thank you for reporting this. To help me debug, can you please do the following:

1. Test with a standard theme and no plugins and let me know if the problem still occurs.

2. Can you please send me the debug info in the admin dashboard, under “Bitcoin and Altcoin Wallets”?

3. Can you please tell me if you are using the Apache or nginx server?

thank you

Hello,

This does not currently work because the fiat currencies available to the plugin are pulled from the http://www.fixer.io/ service.

To do this I would need to add a freely available exchange rates source that provides the Naira-USD exchange rate.

I will look, but if you are aware of any such good API, please let me know. Most APIs would require signing up to a service, so I will have to review which one is most suitable.

thanks

Hello,

Thanks for the detailed description. I am glad that you got your connectivity issue working, and it’s good to know that the wallet is generating valid addresses.

Configuring the wallet is outside the scope of this plugin, however it sounds like your wallet is working well, so I am not sure why you are trying to control resource usage. You should be able to control the number of CPU cores used with the par option.

I would please ask again that in the future you open a new thread for each additional query. This is for the benefit of us, but also for other people who might read these discussions.

I will leave this thread closed since you say that both of your issues are resolved. If you face another issue with the plugin, please do open a new thread.

I believe that for general configuration guidance about the Bitcoin core wallet, a better place to ask for help is http://bitcoin.stackexchange.com/ or the Bitcoin core section of bitcoin talk, at https://bitcointalk.org/index.php?board=4.0 I am sure that the folk over there are more knowledgeable on this than I.

Thanks

kind regards

@san Yes digital ocean is a great platform and I use it too, although I’m not sure if you’re allowed to use referral links in these forums.

@mc_deimon This is a misconfiguration of your web server, nothing to do with the plugin. You should check your .htaccess file. As I mentioned before, AH00124 is an Apache error that indicates that your rewrite rules are causing an infinite loop of redirects. I would therefore recommend that you debug your .htaccess file. Some information is here: https://codex.ww.wp.xz.cn/htaccess Also check to see if there is another .htaccess file in your assets area or some other directory, as these files can be nested.

The 404 and 500 errors that you report have nothing to do with an actual error, it is simply the browser console looking for “source map” files that are normally used for debugging minified code, and these do not exist. These errors you posted look like they originate from your access.log file, not your error.log.

It is still possible that there might be some PHP error message in your error.log file, or your wordpress debug log if you have enabled it. If there is an error written in your log at the same time that you get the error message on your screen, then please post it here, but only after you debug your server’s configuration.

kind regards

Normally the admin-ajax.php request is done when in the admin area. I am not sure about this, but I believe some plugin that you are using is causing it to be requested from the frontend.

Can you please post here the entire text of the error that you see in your screen? This will be very helpful for me as I try to find the cause of this issue.

Thank you

Hello,

To clarify, what you just reported is a different error than your original error.

Your original error had to do with stale testnet addresses in your addresses table.

Your current error indicates that the plugin does not connect to your RPC port. Since curl cannot connect to your wallet, neither can the plugin. Unless you resolve this, the plugin will not connect. This can be a firewall issue or anything else really.

Additionally, in your curl command you have left a space after http:// which caused the protocol to be interpreted as a hostname, hence the error Could not resolve host: http. The full command would be:

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

Unfortunately unless you can resolve this I cannot help you with the plugin. Do let me know once you resolve this. You should do whatever you had done before, when the plugin was connecting.

kind regards

Great, I’m glad it worked!

Since you and others indicate that this was solved in 3.0.1 I am closing this thread.