[alexg]

Thank you

I am not sure what you mean by “type of server”, I am trying to determine exactly what you observe, so I can understand what the problem is.

To be clear: When you hit the cron trigger url in your browser, sometimes you get a “success” result and sometimes you get what type of response?

[alexg]

You would only get a JSON parse error like the one you describe if the JSON API does not return JSON but an HTML response, such as a 404 error.

To be clear, to correctly trigger the cron jobs manually, go to Wallets -> Cron job, then click on the link displayed on that admin page. The result should be “success”. Do you get a different result when you do this?

[alexg]

Thank you, I will look at it.

with regards

[alexg]

Hello,

Thank you for reporting. I see the problem too.

Will be fixed in the next patch release.

with regards

[alexg]

Oops! Thank you for reporting this.

It seems that this is an error that can occur in some MySQL configurations only, after the recent changes to the error reporting mechanism.

Could you please try again with 0.5.1-beta? It should be fixed now.

with regards

[alexg]

ERROR IS AS FOLLOWS;

Attachments:

You must be logged in to view attached files.

[alexg]

If the adapters are both responding and unlocked, withdrawals should at least be attempted.

Could it be that your cron job is not running? Did you try to trigger it manually? If withdrawals are attempted after triggering the cron url a few times, then it means that your WordPress internal cron trigger is not running. You can remedy this by setting up a unix system cron. But first test to make sure that this is the problem.

Let me know please.

[alexg]

OK. Be careful not to confuse the RPC password with the wallet passphrase. These are two different things, make sure that you know the difference.

So, is your adapter listed as locked or unlocked?

[alexg]

Hello,

If your coin adapters are in a “responding” state, then it sounds like your wallets are locked. To check if your coin adapters are locked or unlocked, go to Wallets -> Adapters, then check under Withdrawal lock.

If you are using a passphrase to encrypt the wallets, enter the passphrase in the coin adapter settings. You can control how long the passphrase you entered is retained in Wallets -> Cron job -> Time to retain withdrawal secrets. If you change this setting, you should re-enter your wallet passphrase.

Please let me know if this doesn’t work for you.

with regards

[alexg]

No, unfortunately there is no way to connect ERC20 tokens at this time.

[alexg]

There is currently no way to do this but I will work on it. It has been requested before and it is surprisingly tricky with the current API architecture. Hopefully there will be something about this in the next patch.

Thank you for your comment.

with regards

[alexg]

Hello,

The chart and orderbook are now available to all without login to version 0.5.0-beta. Please see the full release notes in the latest blog post: https://www.dashed-slug.net/public-chart-orderbook-exchange/

with regards

[alexg]

Hello,

My apologies, you should add quotes around the url since it contains ampersands. And I forgot to add a slash to /dev/null before. So the command should be:

/usr/bin/curl -sk 'https://mydomain.com/?__wallets_action=do_cron&__wallets_apiversion=3&__wallets_cron_nonce=0227e9c5029dxxxxxxxxxxxxx' > /dev/null 2>&1

Without a shell it is going to be hit-and-miss before you figure out the exact command since every system is different, but I think the above will work.

Let me know if it doesn’t.

[alexg]

Assuming that curl is in /usr/bin on your system, you could add the following command:

/usr/bin/curl -sk https://mydomain.com/?__wallets_action=do_cron&__wallets_apiversion=3&__wallets_cron_nonce=0227e9c5029dxxxxxxxxxxxxx > /dev null 2>&1

The full crontab entry for running this every five minutes would be:

*/5 * * * * /usr/bin/curl -sk https://mydomain.com/?__wallets_action=do_cron&__wallets_apiversion=3&__wallets_cron_nonce=0227e9c5029dxxxxxxxxxxxxx > /dev null 2>&1

[alexg]

Hello,

First of all I have moved your post to a new thread.

Before doing anything we must determine what is causing the problem:

1. Which coin adapter are you using?

2. Which plugins and extensions are you using?

3. Are you able to login and use the site? Under what circumstances do you get error 524?

4. If you can login, try disabling cron jobs (set Run every to never). Does the problem resolve itself? If not, then the issue is not related to cron jobs.

5. Does the problem resolve itself if you disable other plugins?

6. What happens if you deactivate the woocommerce payment gateway? Does the site become responsive?

7. Also, HTTP 524 is the timeout error code. This indicates a firewall problem. Did you reconfigure your webserver in any way, or did you move between hosts?

8. Are you using cloudflare? Could you disable it for a moment to see what happens?

Please let me know about all of the above so I can get a clearer picture.

with regards

[Author]

Posts