May 20, 2020 at 10:13 pm #8408
Im trying out your new Turtlecoin adapter and have run into an issue. I went through step by step setting this adapter up and I dont know if I am missing something or what, but I am getting this error in the wallets -> adapters -> adapter status “❎ Not responding: Cannot open wallet mysitesdomain.wallet until the admin provides the passphrase”.
Thought maybe it was something that I had screwed up on my site, so I tried it on a fairly clean wordpress install and i’m getting the same error.
Thought maybe something was off with the fork I am using, so I compiled the Turtlecoin daemon and wallet-api and ran them and i’m still getting the same error for some reason.May 21, 2020 at 7:23 am #8409
You simply need to enter a secret password in your coin adapter settings, under “Wallet settings” -> “Password”. The plugin will then create a new wallet for your site, and will ask the
wallet-apito encrypt the wallet file with this password.
with regardsMay 21, 2020 at 11:47 am #8410
I have entered a password, for some reason its like its not registering that I am providing a password. Attaching some screenshots of the setup.
Attachments:You must be logged in to view attached files.May 21, 2020 at 5:04 pm #8414
Thank you for testing! Well, the adapter works on my machine 🙂
1. Check your value of the setting: “Cron job” -> “Withdrawal locks” -> “Time to retain withdrawal secrets”. By default this is 0 which means retain passwords indefinitely in the DB.
2. The passwords are stored as transients. Check your WordPress installation and any caching/optimization plugins to see if they are deleting your non-expired transients. If necessary you can disable such plugins and try again.
Please let me know if this made a difference.May 22, 2020 at 3:51 am #8416
So my “Time to retain withdrawal secrets” is set to 0.
Disabled every plugin except the dashed-slug plugins with the same result unfortunately.
I thought maybe something was being thrown off because I was using a pre-packaged wordpress multi-site installation that came with a bunch of bs already installed and loaded so I started with a clean install of ubuntu, went through and installed wordpress and its dependencies from scratch to have as clean of an install as possible. Loaded only the Bitcoin and Altcoin Wallets plugin and the Turtlecoin plugin. Started my daemon and wallet-api. Configured the plugin settings, Im getting the same error message saying cannot open wallet until admin provides the passphrase.
I really appreciate your help. Im not sure where im going wrong on thisMay 22, 2020 at 9:14 am #8417
OK, I have now tested on multisite and I see that the secrets are not saved when the plugin is network-activated.
I will release a fix for this and a few other minor issues over the coming days.
Thank you very much for reporting this issue. I will notify you again here.
with regardsMay 22, 2020 at 11:53 am #8420
No problem at all!
Thank you very much for all of your hard work!!May 22, 2020 at 5:26 pm #8426
I have uploaded a new patch release,
0.1.1-betaof the adapter, where the issue with network-active installations that you discovered is addressed.
Additionally, the adapter is now shown with a withdrawals lock (padlock) while the node is not yet synced. This will prevent any withdrawal failures while the node is syncing.
Thank you for reporting this issue.
with regardsMay 23, 2020 at 11:39 am #8428
Awesome thank you! Wallet is now responding. Found another slight issue. Not to do with the passphrase but on lines 281 and 282 of the coin-adapter-turtlecoin.php the filter_input for the daemon-ip and daemon-port are set to rpc-ip and rpc-port so whatever value I set in the UI for the Wallet RPC ip and port was also applied to the daemon ip and port. I changed the filter_input on lines 281 and 282 from rpc-ip and rpc-port to daemon-ip and daemon-port, and the adapter started working. screenshots attached
Attachments:You must be logged in to view attached files.May 25, 2020 at 6:29 am #8442
Oops, yes I see it now. Thank you! I hurried to release the fix on Friday evening without noticing this bug. I will release a fix today. with regardsMay 25, 2020 at 7:32 am #8446
0.1.2-betauploaded with the fix. Thank you for testing the component!
- You must be logged in to reply to this topic.