Forum Replies Created
-
Posts
-
It is also displaying the balance with 4 decimals instead of 8 decimals.
Through the API, it looks like it is slowly scanning the block-chain (as seen in screenshot)
We are connected now. Disabling cache completely did that.
But my balance is way off… there should be about 28,000 ARMS in the wallet. But the screenshot shows… much more
And my admin account shows… -40,700 ARMS
This is hooked up to a copy of the original server wallet renamed to n2aa.org.wallet
I manually added the options to the database, but the same connection errors still occur with the manually added options as seen in the screenshot.
Yea, so the wallet password and the rpc password does not seem to be saving into the database…
You can see in this alphanumerically arranged list that they are not in there…
Also, when I run “wp transient get trtl-ARMS-settings-wallet-passphrase” after saving settings I get:
Warning: Transient with key “trtl-ARMS-settings-wallet-passphrase” is not set.
wallets_secrets_retain_minutes is set to 0 as can be seen in the screenshot
The original 2acoin adapter has been disabled and deleted.
The passwords when saved still are not saved to the database.
Maybe it is a residual from before, since I was already using this currency… so it is not generating anymore options for it and Im stuck with the options I currently have from before.
As you can see from the screenshot I am missing the deamon IP Address and Port & the Wall password options in the database here…
Any reason why these options don’t exist in my database?
Yea, I save the wallet encryption password and it is not saving it into the database when I do a DB wide search…
I just moved this whole server from an apache2 server to an nginx server, but everything else seems to be working fine…
Any idea why the password is not in the database, what is the option name I am looking for?
Ok, so blockchain is downloaded, daemon is running, wallet-api is running, when I save the RPC Password/Wallet Password. The API chirps about “Client requested to modify a wallet, whilst no wallet is open” as can be seen in the screen shot…
Also it looks like I’m getting the same error: Not responding: Cannot open wallet n2aa.org.wallet until the admin provides the passphrase
I’ve taken screenshots of everything that might be relevant.
On a side note, the tip on how to start the daemon and wallet-api seems to have switched the port numbers up so in the tip it is saying to use the daemon port on wallet-api and vice-versa.
With 2acoin-service I usually start it using:
./2acoin-service -w thesitewallet.wallet -p MySuperSecretPassw0rd --rpc-password MySuperSecretPassw0rdIf I try to start the RPC client without a wallet (as specified in the installation instructions):
./2acoin-service –rpc-password MySuperSecretPassw0rd –bind-address 10.136.18.61 –enable-cors “*”
Fatal error: You must specify a wallet file to open!Nope, looks like turtlecoin uses: ./wallet-api to start
https://turtlecoin.github.io/wallet-api-docs/
Is that going to affect me being that I start the RPC daemon with ./2acoin-service?
I’m back an will be working on this today.
I am assuming that the wallet-api is a variable for the turtlecoin variant that is being used. As 2acoin is stated using ./2acoin-service?
Anyways, going to try with a new wallet as you suggested, will get back to you in a bit.
