Brief Guide: Setting Up Testnet Wallet, Sending, And Receiving Coins - Os Neutral

Discussion in 'Technical Support' started by anondran, Jan 28, 2016.

  1. 2017/12/15 - Decred v1.1.2 released! → Release Notes  → Downloads
  1. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45
    If you want help with something, state the symptoms of your problem and a log of what may be relevant (in this case, it sounds like the log from dcrwallet may be helpful, but honestly it's impossible to gather even what sort of issue you're having, except that it probably has something to do with Decred. :p
     
  2. here the log dcrwallet

    Code:
    03:34:59 2016-01-31 [INF] WLLT: No recorded transaction history -- needs full rescan
    03:34:59 2016-01-31 [INF] WLLT: No stake manager present, generating
    03:35:00 2016-01-31 [INF] WLLT: Opened wallet
    03:35:00 2016-01-31 [INF] DCRW: Server TLS is disabled
    03:35:00 2016-01-31 [INF] DCRW: RPCS: RPC server listening on 127.0.0.1:19110
    03:35:00 2016-01-31 [INF] DCRW: Client TLS is disabled
    03:36:15 2016-01-31 [WRN] DCRW: Connection to Decred RPC chain server unsuccessful -- available RPC methods will be limited
    03:36:15 2016-01-31 [ERR] WLLT: Unable to request transaction updates for winning tickets. Error: the client was never connected
    03:36:15 2016-01-31 [ERR] WLLT: Unable to request transaction updates for spent and missed tickets. Error: the client was never connected
    03:36:15 2016-01-31 [ERR] WLLT: Unable to request transaction updates for stake difficulty. Error: the client was never connected
    03:36:15 2016-01-31 [INF] DCRW: Client TLS is disabled
    03:36:58 2016-01-31 [INF] DCRW: Received SIGINT (Ctrl+C).  Shutting down...
    03:36:58 2016-01-31 [WRN] DCRW: Server shutting down
    03:36:58 2016-01-31 [ERR] WLLT: Failed to get last used address for address pool external: the client was never connected
    03:36:58 2016-01-31 [INF] DCRW: Shutdown complete
    03:37:04 2016-01-31 [INF] WLLT: Opened wallet
    03:37:04 2016-01-31 [INF] DCRW: Server TLS is disabled
    03:37:04 2016-01-31 [INF] DCRW: RPCS: RPC server listening on 127.0.0.1:19110
    03:37:04 2016-01-31 [INF] DCRW: Client TLS is disabled
    03:37:17 2016-01-31 [INF] DCRW: Received SIGINT (Ctrl+C).  Shutting down...
    03:37:17 2016-01-31 [WRN] DCRW: Server shutting down
    03:37:17 2016-01-31 [INF] DCRW: Shutdown complete
    
    
     
  3. after i [enter] on step 3
     
  4. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45
    Basically, it can't do much of anything because it can't connect to dcrd is what I can gather from that log. Did you start dcrd?
     
  5. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    I too am having a similar issue after I typed in command: dcrwallet -u myusername-P mypassword--noclienttls --noservertls --walletpass mypublicpassphrase--dcrdusername=myusername --dcrdpassword=mypassword :

    Code:
    13:37:49 2016-01-30 [ERR] WLLT: Unable to request transaction updates for stake
    difficulty. Error: the client was never connected
    13:37:49 2016-01-30 [INF] DCRW: Client TLS is disabled
    13:39:04 2016-01-30 [WRN] DCRW: Connection to Decred RPC chain server unsuccessf
    ul -- available RPC methods will be limited
    13:39:04 2016-01-30 [ERR] WLLT: Unable to request transaction updates for winnin
    g tickets. Error: the client was never connected
    13:39:04 2016-01-30 [ERR] WLLT: Unable to request transaction updates for spent
    and missed tickets. Error: the client was never connected
    13:39:04 2016-01-30 [ERR] WLLT: Unable to request transaction updates for stake
    difficulty. Error: the client was never connected
    13:39:04 2016-01-30 [INF] DCRW: Client TLS is disabled
    From the other command line:
    Code:
    13:37:49 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:59516
    13:37:54 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:59526
    13:38:04 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:59547
    13:38:19 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:59596
    13:38:39 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:59624
    13:39:04 2016-01-30 [INF] BMGR: Processed 1 block in the last 6m27.66s (3 transa
    ctions, height 3572, 2016-01-30 13:38:46 -0700 MST)
    13:39:04 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:59654
    This is what the command line looked like just as it began:

    Code:
    13:21:06 2016-01-30 [INF] BMGR: Processed 1 block in the last 31.04s (1 transact
    ion, height 3563, 2016-01-30 13:20:42 -0700 MST)
    13:21:37 2016-01-30 [INF] BMGR: Processed 1 block in the last 31.03s (1 transact
    ion, height 3564, 2016-01-30 13:21:22 -0700 MST)
    13:23:42 2016-01-30 [INF] BMGR: Processed 1 block in the last 2m5s (1 transactio
    n, height 3565, 2016-01-30 13:23:32 -0700 MST)
    13:24:56 2016-01-30 [INF] BMGR: Processed 1 block in the last 1m13.42s (1 transa
    ction, height 3566, 2016-01-30 13:25:31 -0700 MST)
    13:26:04 2016-01-30 [INF] BMGR: Processed 1 block in the last 1m8.52s (1 transac
    tion, height 3567, 2016-01-30 13:25:36 -0700 MST)
    13:26:34 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:57814
    13:26:39 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:57829
    13:26:49 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:57844
    13:27:04 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:57872
    13:27:24 2016-01-30 [WRN] RPCS: RPC authentication failure from [::1]:57913
    Any ideas?
     
  6. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45

    One. The dcrd wasn't run with --testnet as an argument?
     
  7. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    I ran using this command: dcrd --testnet --notls -u user -P pass
     
  8. davecgh

    davecgh Hero Member
    Developer Organizer

    Dec 31, 2015
    642
    788
    Male
    United States
    RPC authentication failure means your username and/or password don't match. Whatever you specified for your username (-u) and password (-P) on dcrd have to match whatever you specify for the dcrwallet --dcrdusername and --dcrdpassword parameters.
     
  9. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    Should I stop it and rerun?
     
  10. davecgh

    davecgh Hero Member
    Developer Organizer

    Dec 31, 2015
    642
    788
    Male
    United States
    Yeah, stop dcrwallet and then start it again with the correct username and password to --dcrdusername and --dcrdpassword.
     
  11. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    Ok. I copied and pasted but maybe I did something wrong. I entered the same user and pass under dcrwallet -u user -P pass
    as I did for --dcrdusername=user --dcrdpassword=pass. This is the inital user and pass I setup not the private password. Are these the correct credentials to enter here?
     
  12. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    Doing it again. I must be putting the incorrect credentials in somewhere.
     
  13. thepotterone

    thepotterone Jr. Member

    Jan 28, 2016
    128
    27
    Male
    enthusiast
    Somewhere above the UK
    Very helpful, thankyou..
     
    anondran likes this.
  14. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    Not having any luck. Would I break anything if I started the guide from the beginning?
     
  15. thepotterone

    thepotterone Jr. Member

    Jan 28, 2016
    128
    27
    Male
    enthusiast
    Somewhere above the UK
    i suggest deleteing the tesnet wallet start afresh, the wallet.dat file is found in appdata\local\dcrwallet\testnet as you will see the air drop isnt in the folder so thats safe
     
  16. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    Ok, I'll give that a try, can't hurt at this point
     
  17. sambiohazard

    sambiohazard Sr. Member

    Jan 21, 2016
    844
    372
    @Argonaut just put a space between mypassword & --noclienttls in your command. I think that will solve your typo :p
     
    anondran likes this.
  18. rohit kumar

    rohit kumar New Member
    Advocate (Reddit)

    Dec 28, 2015
    15
    10
    Male
    software developer
    India
    @anondran I need some help after this command :
    dcrwallet --dcrdusername=YourUserName --dcrdpassword=YourPassword /noclienttls
    in cmd it's starting scanning blocks . how can I proceed further it's taking lot of time
     
    anondran likes this.
  19. thepotterone

    thepotterone Jr. Member

    Jan 28, 2016
    128
    27
    Male
    enthusiast
    Somewhere above the UK
    sounds like its updating, not sure where you are but every time i open my wallet now its been setup has been with this command :-

    dcrwallet -u xxxxx -P xxxxxx --noclienttls --noservertls --walletpass xxxxxxx --dcrdusername=xxxxx --dcrdpassword=xxxxxx
     
    anondran likes this.
  20. Argonaut

    Argonaut New Member

    Jan 12, 2016
    31
    4
    Male
    That might have been the issue. I was able to get it up and running yesterday however I just started the process from the beginning. If my original syntax had no space then maybe my password included --noclienttls. Good catch :)
     
    sambiohazard likes this.

Share This Page