dashed-slug.net

Hi, you can ignore the error, and in fact I should make it less prominent.

The cron mechanism can only run when you or a visitor looks at your site, and if your site has low traffic this will happen often. There is nothing to worry about.

Thank you, every time such an incident happens I add to the troubleshooting section of the manual. It’s like a knowledgebase for installation issues.

I guess we’ll never know what went wrong.

If you face further issues please open a new thread.

best regards
Alex

No, sorry if I was not clear. I said that the port looks open from here. I do not know why the port looks closed from your WordPress. The fact that they opened up the firewall was a necessary step.

Running your own apache or nginx server is not incredibly hard as long as you keep them updated, but the plugin should still work with the setup you have now.

Are you running any firewall on your VPS?

You could also check your bitcoin logs at ~/.bitcoin/debug.log or ~/.bitcoin/testnet3/debug.log. There could be clues there as to what’s going on.

EDIT: You could tail -f the logs and observe if anything is written out 1) while starting the wallet and 2) while trying to connect from the plugin. There will be a lot of data in there, but you are only interested in errors that may occur at the time of these two events.

• This reply was modified 8 years, 5 months ago by dashed-slug.net. Reason: added instructions on how to check logs

Hello,

First of all thank you for the thorough explanation of what you did.

The suggested rpcauth value contains the username and password that you provided, salted with random data. So it’s normal that every time it’s different. You could use any one of the suggested values, but using rpcuser and rpcpassword should also work.

The error that you report, *connection refused*, is normally shown if the RPC port is not open. If you try to connect to any random port that is not open, you will see that you will get the same error. So the plugin sees a closed TCP port.

You did not mention if you have specified rpcport=8332 in your conf file. It should be the default, but it doesn’t hurt to specify it.

Other than that, try using telnet or nc (netcat) to see if that TCP port is open on your server.

Lastly, I would not discount the possibility that there is a firewall on your WordPress machine that blocks outgoing connections to non-standard ports. Just because the peer-to-peer communication over 8333 works doesn’t mean that 8332 also works…

In conclusion, set the rpcport setting, and also try to check if the port is actually open. Let me know what you find.

Thanks I would change the tables myself but at the moment I have very little time.

Can you check under Wallets -> Transactions? You should be able to see if the 10 LTCT were deposited into an address? If that address is registered as the deposit address of that user then it would make sense.

Hello,

You have brought up two distinct issues:

1. I know the table is a bit crowded. There are two things you can do: either use some css on it or provide your own knockout views. You can copy the views to a different directory and modify the knockout views. This is described in the documentation, the filter is named wallets_views_dir.

2. The 10 LTCT coins that you got would not show up in the plugin because they were not deposited to a user’s deposit address. They were simply added to your wallet balance by CoinPayments. Users get money into their account when they deposit money to their deposit address via [wallets_deposits] or when they receive money from other users.

The deposit address “from” column is as intended. You are credited from your deposit address. This is a record of your site account. Think of it as money “jumping off” the blockchain and entering your site “from” that address.

I have implemented the explorer links you requested and will be pushing the code along with a few other user requests, right after I test everything again.

My shapeshift extension is 90% done but I am always too busy to get it to 100%.

The issue here is that normally coin adapters should report a URL pattern that can display addresses and transactions in an explorer. While cryptoid has a large number of coins it does not have all of them (can’t find DOGE in their list, that’s a showstopper for me!!!). So there needs to be some work done on the coin adapters interface, and then in the coin adapter implementations. Cryptoid can be the default as long as adapters can override this. Things are never as simple as they seem 🙂