Hello,

The outgoing TC connection to your wallet server fails with a timeout after 10 seconds.

Timeouts are usually due to firewalls.

You should check what firewalls protect the server where the wallet is running. You should allow incoming TCP connections on port 8711.

If you are on a hosting provider, you should contact them and let them know that you want them to add this rule to their firewalls.

If you are managing the server yourself, you should also check any software firewalls on the server (e.g. ufw, iptables, etc).

Hope this helps. Please let me know if you have any more questions.

with regards

Hmm…

I will look at this issue. The plugin should not be crashing like this.

But in the meantime, can you check that you have associated your coin/currency to the wallet?

I will let you know what I find after investigating.

with regards

Hello,

Thank you for providing screenshots regarding the above.

I am assuming you are using version 6.0.0-RC3.

The screenshots you provided are not from the plugin’s own editors. Can you please use the plugin’s built in editors?

Based on the trace you provided, the plugin is trying to load a wallet by its string name, rather than a post ID:

DSWallets\Wallet::load('bitcoin')

I am not sure how that can happen. The argument passed to Wallet::load() must be an integer, and the plugin’s editor does not allow you to associate a currency with anything other than a wallets_wallet post ID. 

I am guessing based on the screenshots you provided, that maybe you used another post meta editor to modify the currency post type? If so, please use the plugin’s own editor.

I am planning to upload a version RC4 with some bug fixes, and this should be the last RC before the final release. But I don’t think that any of the unreleased fixes apply to your particular bug.

(I am taking things slow because I lost a loved one this week and it’s still hard to concentrate on work. Sorry about that. As soon as possible, I plan to continue with the release plan and other planned improvements to the products and website.)

TL;DR The plugin should not ever be calling Wallet::load('bitcoin'). From the stack trace, it looks like you tried to save a currency with a wallet string bitcoin, which is incorrect. I think this is an issue related to you using another post meta editor.

Please let me know if this makes any sense?

with regards

P.S. I use this email for work, not the one at gmail.

Thank you for providing screenshots. Unfortunately I was not able to determine what the issue is.

Just to make sure that we are on the same page, I will summarise the issue so far. Please check that I have understood you correctly.

The plugin is not being notified immediately about incoming deposits.

You have added the following lines to your config file:

walletnotify=curl -s 'https://exchange.napocoin.net/wp-json/dswallets/v1/walletnotify/25335/%s' >/dev/null
blocknotify=curl -s 'https://exchange.napocoin.net/wp-json/dswallets/v1/blocknotify/25335/%s' >/dev/null

Where 25335 is the post_id of your Napocoin Currency entry.

When you logged in to your wallet server, you have attempted the following command:

curl ‘https://exchange.napocoin.net/wp-json/dswallets/v1/walletnotify/25335/ABCD’

and you get as result:

{"message":"The plugin is being notified about this TXID. If a user is associated with one of its output addresses, a deposit will be registered for this user.","status":"success"}

The above is to be expected when the TXID is invalid.

But if you try the same command with a correct TXID that corresponds to your deposit, then you see on the screen the message:

There has been a critical error on this website.

This may be due to a difference between napocoin and bitcoin JSON-RPC APIs. The difference could be something trivial.

The only way to be sure is to see the PHP error that occurs at the time when you run the curl command with the correct TXID.

Can you please find this error message? The error will be in your PHP error log, and also in wp-content/debug.log if logging is enabled.

Let me know if you can find the error.

with regards