[alexg]

In addition to the above, I have just released version 1.0.4 of the adapter where if the IPN message is received by your host and is being rejected, you can view the reason in the admin interface. From the homepage:

Finally, if IPN messages arrive to your host but are being rejected, you can see a copy of the last error message and the time it was generated in the admin screen. The error message is retained for 1 hour and can help you debug problems with IPN messages that go through your firewall but are not accepted for some reason. This was implemented in version 1.0.4 of the adapter.

It’s worth looking at this, it will tell you if the problem is due to some firewall or misconfiguration.

kind regards

 

[alexg]

Hello,

You were correct to look for the IPN information because sometimes there is some error message there. I assume you have already looked at the troubleshooting section at the adapter’s homepage.

Most probably this is due to some firewall. Try disabling Wordfence, disabling your Linux firewall(s) and also contact your hosting provider to see if they are blocking SSL connections with non-standard headers, such as HMAC authentication.

If you do figure out what the problem was, then you can reenable your firewalls and configure them around it.

Please let me know what you find.

kind regards

Alex

[alexg]

Hello,

Have you first installed Bitcoin core? If not, then the file and the directory would not exist and you would get this error.

If you have, and you still get that error, then it should be a matter of permissions.

I would advise against installing Bitcoin core yourself without some basic familiarity with the Linux shell.

kind regards

 

[alexg]

Hello again,

You should also check to see that the incoming connections are not blocked by some other firewall, such as a firewall that your host has placed.

To clarify, CoinPayments should only be able to tell you whether the connection was successful (and the message was rejected) or whether the connection was not successful. In the first case it would be a matter of an incorrect IPN secret, while in the second case it would be an issue with some firewall. I am only mentioning firewalls because a number of other users had the same problems with their hosting providers.

kind regards

 

[alexg]

This has now been addressed in version 3.3.3

 

[alexg]

This has now been addressed in version 3.3.3

 

[alexg]

Hello,

You could use any standard text editor to edit the conf file. Good choices would be vi, emacs or nano for example.

Having said this, if you are not comfortable using the Linux command line you might prefer to install one of the cloud wallets rather than trying to setup a full node. The cloud wallets are the CoinPayments adapter and the block.io adapter. These require minimal effort in installation and maintenance.

kind regards

Alex

[alexg]

Hello,

I have published your previous post. Thank you for providing additional details.

The symptoms you observe are to be expected since the IPN was not sent successfully. The question is why it was not sent.

I can see that the API endpoint at https://xaymacacoin.com/?wallets-cp-ipn=1 is correctly exposed to the internet.

You mentioned that you momentarily disabled your firewall. Can you please tell me which firewall?

The only course of action now would be to make sure that there are no other firewalls preventing the message from getting through.

You could check if any of the following types of software interfere:

1. Security plugins installed on your WordPress site. Access to your site might be limited by geolocation or other factors and this could be preventing the CoinPayments platform from connecting.

2. Firewalls at your server host.

3. Any firewalls that your host is running to secure their network.

Other things I can think of:

4. Could it be that you have entered your credentials a second time incorrectly after first entering them correctly once? Could you try entering the details once more? The IPN secret is used to verify the authenticity of messages coming from CoinPayments, so if this is entered even slightly wrong then messages would not be delivered. It might be worth verifying that everything is entered correctly and with no additional whitespace characters.

5. Since the IPN details did not reveal any useful error message, it might be worth asking CoinPayments support to see why the IPN message with ID aa3b3a4ed5fcfecd96a45222b5f73246 was not delivered. Perhaps they have more information on this.

I plan to add some validation to the input fields for the credentials, so that users can get early warning on such errors.

Please let me know what you find.

kind regards
Alex

[alexg]

Please see the plugin’s readme file and the dashed-slug homepage for all your available options.

The CoinPayments adapter is the only one that has deposit fees.

If you have any further questions please open a new thread as this is unrelated to the original post. This is for the benefit of others reading this forum later.

kind regards

[alexg]

Unfortunately you cannot. If this is important to you, you will have to use another coin adapter.

[alexg]

Hello,

Your issue should have nothing to do with your hosting.

If this is the first time you entered your credentials, make sure that you have entered them 100% correctly, with no extra spaces, etc.

It does look like you have entered one of your codes incorrectly. Otherwise you should not be getting “HMAC signature does not match”.

I would suggest that you enter all the codes again carefully and let me know if the problem persists.

[alexg]

This is very strange.

If you check assets/scripts/wallets-faucet.js you will find that in cases where the remaining time is more than 1 hour, the time is now displayed as human-readable text. Additionally, I have tested this extensively.

My first thought was that the old JavaScript code is still running on your browser, but I have made sure to attach a version number to the wp_enqueue_script() call so this is not very likely. It might be worth clearing your cache anyway just to make sure.

kind regards

[alexg]

OK sounds like you could be doing something wrong.

There are three places where you can enter a blockexplorer url:

1. When you extend the Dashed_Slug_Coin_Adapter class to create your own coin adapter from scratch, you can override the methods explorer_uri_transaction() and explorer_uri_address(). You can use the method get_symbol() to constuct your URI based on the actual symbol of the instance. You could define an abstract subclass that returns something like 'https://chainz.cryptoid.info/' . $this->get_symbol() . '/tx.dws?%s' and then not have to worry about this in any concrete implementations for each coin you instantiate.

2. You can provide a URI by binding to the filter: wallets_explorer_uri_tx_XXX or the filter: wallets_explorer_uri_add_XXX where XXX is a coin symbol. In this case you have no choice – you have to use the XXX symbol in your URI pattern since it is already part of the filter you are binding to.

3. In the MultiAdapter’s coins.csv file. Again, in this file every line is its own coin, so again you have to use the coin symbol as part of the URI.

Hope this is clearer. I do not want to change the URI pattern, because that would break things. I am confused by what you mentioned “My service supports multiple coins but I only have one notification” Block explorer URIs have nothing to do with the notification mechanism. If you insist that none of the above solutions work for you, could you please explain why in more detail?

Thank you very much

kind regards
Alex

[alexg]

Hello,

I am not sure what you are asking exactly.

Do you want to disable deposit fees? Deposit fees only exist for the CoinPayments adapter and are enforced by the platform, not the plugin.

Please post a new thread about this because this is a separate issue.

If possible could you please explain in more detail what it is exactly that you want to delete?

Thank you

kind regards

[alexg]

The documentation is the PDF file in the bundle download of the plugin. http://dashed-slug.net/downloads/

[Author]

Posts