Wallet decryption issue

Basically, I know the password to decrypt it, but there is no such options in the gui aka the qt to do it so I did this
Imgur
Please see the following for my ppcoin.confg
I am using fedora 20 xfce

[code]# ppcoin.conf configuration file. Lines beginning with # are comments.

Network-related settings:

Run on the test network instead of the real bitcoin network.

testnet=0

Connect via a socks4 proxy - default none

#proxy=127.0.0.1:9050

Accepting incoming connections

listen=1

UPnP

upnp=1

##############################################################

Quick Primer on addnode vs connect

Let’s say for instance you use addnode=4.2.2.4

addnode will connect you to and tell you about the

nodes connected to 4.2.2.4. In addition it will tell

the other nodes connected to it that you exist so

they can connect to you.

connect will not do the above when you ‘connect’ to it.

It will only connect you to 4.2.2.4 and no one else.##

So if you’re behind a firewall, or have other problems

finding nodes, add some using ‘addnode’.

If you want to stay private, use ‘connect’ to only

connect to “trusted” nodes.

If you run multiple nodes on a LAN, there’s no need for

all of them to open lots of connections. Instead

‘connect’ them all to one node that is port forwarded

and has lots of connections.

Thanks goes to [Noodle] on Freenode.

##############################################################

Use as many addnode= settings as you like to connect to specific peers

addnode=69.164.218.197
addnode=10.0.0.2:8333

… or use as many connect= settings as you like to connect ONLY

to specific peers:

#connect=69.164.218.197
#connect=10.0.0.1:8333

Maximum number of inbound+outbound connections.

maxconnections=16

JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

server=1 #tells Bitcoin-QT to accept JSON-RPC commands.
#server=0

You must set rpcuser and rpcpassword to secure the JSON-RPC api

rpcuser=notTelling
rpcpassword=notTelling

How many seconds bitcoin will wait for a complete RPC HTTP request.

after the HTTP connection is established.

#rpctimeout=30

By default, only RPC connections from localhost are allowed. Specify

as many rpcallowip= settings as you like to allow connections from

other hosts (and you may use * as a wildcard character):

rpcallowip=127.0.0.1
rpcallowip=192.168.1.*

Listen for RPC connections on this TCP port:

rpcport=9902

You can use ppcoind to send commands to ppcoind

running on another host using this option:

rpcconnect=127.0.0.1

Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate

with ppcoind

#rpcssl=1

OpenSSL settings used when rpcssl=1

#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem

Miscellaneous options

Set gen=1 to attempt to generate ppcoins using built-in CPU mining

#gen=1

Use SSE instructions to try to generate bitcoins faster.

#4way=1

Pre-generate this many public/private key pairs, so wallet backups will be valid for

both prior transactions and several dozen future transactions.

#keypool=100

Pay transaction fee amount per kilo-byte. Default 0.01 (1 cent)

Minimum required 0.01 (1 cent)

#paytxfee=0.01

Allow direct connections for the ‘pay via IP address’ feature.

#allowreceivebyip=1[/code]

And after I restart my computer I got this
[mr-fool@localhost ~]$ cd /home/mr-fool/Downloads/ppcoin-0.3.0-linux/bin/64/
[mr-fool@localhost 64]$ ./ppcoind walletpassphrase secretpasswordthatiamnottelling 9999999 true
error: couldn’t connect to server

or
[mr-fool@localhost 64]$ ./ppcoin-qt walletpassphrase nottelling 9999999 true
still I got
Info: Minting suspended due to a lock wallet

Try this conf and still no goal

[code]#ppcoin.conf

JSON-RPC options (for controlling a running ppcoind process)

listen=1
upnp=1

#Server mode allows Qt to accept JSON-RPC commands
server=1

You must set rpcuser and rpcpassword to secure the JSON-RPC api

rpcuser=???
rpcpassword=???

#The reserve balance field is the minimum amount of coins you want to have available and NOT put up as stake.
#The reason for this is that if you are generating proof of stake you cannot spend those coins for 520 blocks.
#reservebalance=10000

addnode=69.164.218.197
addnode=10.0.0.2:8333
connect=69.164.218.197
connect=10.0.0.1:8333
rpcport=9902
rpcconnect=127.0.0.1
addnode=66.90.146.146
addnode=91.156.102.128
addnode=110.174.124.20
addnode=67.14.164.114
addnode=37.209.40.22
addnode=50.71.216.165
addnode=109.108.236.208
addnode=173.28.37.150
addnode=68.102.86.156
addnode=213.251.187.24
addnodd=188.134.122.31
addnode=72.38.179.122
[/code]

Can’t really help you with the Linux client. In the Windows client it sometimes takes a while before the ‘minting suspended due to a locked wallet’ goes away. There are some command line parameters which would tell you whether the wallet is unlocked or not. Try -getinfo. This provides a set of data. The last one is something about the wallet status related to whether it is unlocked or locked. Have to do this on top of my head as I’m just on my tablet at the moment.

There is also a thread about Fuzzy’s new wallet where I posted the command to lock and unlock in the debug window. They are the same as the command line.

Hope this gets you somewhere

are you positive its not just telling you minting is locked but the actual wallet is unlocked ?

[quote=“horny-sama, post:2, topic:1951”]And after I restart my computer I got this
[mr-fool@localhost ~]$ cd /home/mr-fool/Downloads/ppcoin-0.3.0-linux/bin/64/
[mr-fool@localhost 64]$ ./ppcoind walletpassphrase secretpasswordthatiamnottelling 9999999 true
error: couldn’t connect to server

or
[mr-fool@localhost 64]$ ./ppcoin-qt walletpassphrase nottelling 9999999 true
still I got
Info: Minting suspended due to a lock wallet[/quote]

[quote=“horny-sama, post:2, topic:1951”]And after I restart my computer I got this
[mr-fool@localhost ~]$ cd /home/mr-fool/Downloads/ppcoin-0.3.0-linux/bin/64/
[mr-fool@localhost 64]$ ./ppcoind walletpassphrase secretpasswordthatiamnottelling 9999999 true
error: couldn’t connect to server[/quote]

You need to run the qt wallet then run the ppcoind daemon.

Before you attempted to reboot your computer, did you issue a ./ppcoind stop ?

If not, when you rebooted the computer, it might have been in the middle of writing something to disk and now it has to re-verify the last XXX number of blocks.

Even when you start ppcoind, let it sit for a full 10 minutes before you start sending commands to it. It has to verify that the blockchain is indeed valid before it starts connecting to other peers to accept new blocks.

Finally, even then it has to take time to try and connect to old peers, find new peers, etc.

It is doing a LOT of things when ppcoind starts up after being offline for a bit.

So if a full 10 minutes haven’t passed, and you can’t do a ppcoind getinfo, then don’t bother trying to unlock the wallet and begin minting. You’ll either get a big long pause, or hang, or a “cannot connect to server”

In this day and age of instant gratification asking someone to wait 10 minutes before trying to click or type is often asking a lot, but if you follow that rule of thumb, many times that is all you needed to do. Be patient and wait.

By the way, debug.log is your friend. When wondering what is going on in Linux, simply do:

$ tail -f debug.log

…and watch and read every thing that ppcoind is doing. That is how I learned a huge majority of what I know.