[alexg]

Update: Can you please check to see if the problem is resolved in version 3.0.1? Thank you.

[alexg]

Another thought, in addition to the ones above:

Can you please try again with Wordfence disabled? It could be that the plugin’s rules are blocking the new JSON API.

[alexg]

Note: Others have reported this same issue at https://wordpress.org/support/topic/could-not-contact-server/

[alexg]

Thanks for reporting.

This looks like a misconfiguration on your Apache server’s htaccess. I believe it is a different issue than the original one where you reported problems with the CoinPayments platform. Something is triggering a loop of redirects.

Did you change something in your .htaccess?

When does the error message appear in your logs? Does it occur on all page accesses?

[alexg]

Hello,

Thanks for reporting. Could it be that you have not refreshed your page? Version 2 of the JSON API requires the new JavaScript.

Also, as a test, does the problem persist when you enable “legacy APIs” in your frontend settings?

let me know please

Thanks.

[alexg]

Thank you for reporting.

This is usually an issue with one or more wallets on CoinPayments being temporarily down for maintenance.

When you first reported an issue with Bytecoin I remember distinctly that the wallet was down for maintenance. Probably your transaction went through now that the wallet is back online.

This is an unavoidable drawback of relying on a third-party service.

kind regards

[alexg]

Yes can you please tell me which of the two available CAPTCHA types does not work? reCAPTCHA or SolveMedia?

Are you logged in? Do you see any error message either in the page or at your JavaScript console (F12)?

Thank you

[alexg]

Thank you very much for sharing all of this info. Setting up a service is the best option as you said.

Once I try this out myself I will add to the documentation.

It makes sense that when you set up a tunnel you need to connect to localhost instead of the remote IP.

best regards

[alexg]

No, you do not need SSL.

In fact, in Bitcoin core, SSL in RPC calls is deprecated precisely because the recommended practice is SSH tunneling.

[alexg]

In your adapter settings, near the bottom, close to the “Save Settings” button there should be a checkbox “enable SSL”. Did you check that?

[alexg]

Yes this was implemented in version 1.2.0.

regards!

[alexg]

Yes this is something that I intend to do. It can work not only with CoinPayments but with all wallets.

It requires an addition to the coin adapters interface. So it will have to wait until a later version.

thanks

kind regards

[alexg]

Hi, good to hear you got it working.

I intend to add instructions in the documentation at some point, so thank you for sharing the command.

As for keeping the tunnel alive, it seems the best practice is to use autossh:

https://superuser.com/a/37768/220597

[alexg]

Hello,

I cannot reproduce the issue you are reporting with the default settings for Wordfence. In my installation it does not block the API endpoint for the CoinPayments IPN.

However here’s something you can try:

1. Go to Admin → Wordfence → Firewall → Whitelisted URLs

2. Enter the following:
URL: /
Param Type: query string
Param Name: wallets-cp-ipn

This should whitelist that request.

Alternatively, use the firewall’s “learning mode” while performing a deposit and it should create a rule. Learning mode can be enabled under “Basic Firewall Options” → “Web Application Firewall Status”

If you try this, can you please report here what you found?

Thank you.

[alexg]

Even if you turn off wp-cron, there is a failsafe mechanism that will ensure that the cron jobs for this plugin will eventually run. You will be notified about this in your admin area.

You can of course add a Linux cron job as well to make it extra certain that the job runs at regular intervals. But you shouldn’t have to.

[Author]

Posts