Anybody have any ideas where i’m going wrong here?
The file should be within your home’s folder, i.e. $HOME/.safe/cli/credentials, it shows you the full path when you self-auth CLI.
Do you use correct version for safe tool?
Well Done Maidsafe. Lets see if I can drive this thing. Dusts off brain…
1 Like
It was, although it was empty. I re-auth’d to see if it would put anything in it. It did not. I removed the file to see if it would regenerate after a re-auth. It did not regenerate it.
Are you getting all these messages:
$ safe auth unlock --self-auth
Passphrase:
Password:
Sending action request to authd to unlock the Safe...
Safe unlocked successfully
Authorising CLI application...
Safe CLI app was successfully authorised
Credentials were stored in ~/.safe/cli/credentials
If not we’ll have to take a look at the logs you get with $ RUST_LOG=debug safe auth unlock --self-auth
Perhaps you are missing the --self-auth flag?
1 Like
Nice @maidsafe! Thanks for your hard work!
Successfully uploaded an image here:
safe://safe.image 
3 Likes
I was missing the flag. That regenerated and populated my credentials file. Since I did the unlock without the flag before, and the
safe auth status
said my Safe was unlocked, I figured everything was OK. So, since I didn’t have the --self-auth flag when I first started, what keypair got tied to my safe nrs create requests? Should it have just failed since I didn’t supply a key and there was nothing in my credentials file? Seemingly there is no way for me to now change my NRS entries and they are forever floating in the ether.
2 Likes
Thanks I started again and must have missed a step first time round
Indeed it is! 
1 Like
I’m 12 hours in front did i miss anything? Oh shit. Well done guys, lots to celebrate this weekend, this is a monumental accomplishment.
7 Likes
ohh!!! I remember now this scenario, so this is the issue, and it’s what you describe, the sn_client will generate a random keypair if the CLI doesn’t provide one, which is what’s happening when there is no credentials file for the CLI to read a key from, so what happened is you’ve created those files and NRS owned by some random key that was generated at that point in time…not good…you don’t own that content since those keys are lost, you don’t have the SK, so this is something to fix/improve. Thanks a lot @wydileie
This will be all solved whenever we remove the simulated-payout feature, as it won’t be possible to upload content with just random key generated. So now that we have farming enabled we should be able to start working on removing the simulated-payouts
4 Likes
I’m here to help by horribly failing 
. Thanks for the responses.
4 Likes
That sounds familiar… 
Is it the same as this? https://forum.safedev.org/t/failed-to-append-to-sequence-networkdataerror/2976
1 Like
I think so, yes.
Just in case testcoins will be realcoins:
New SafeKey created at: “safe://hyryyyyfcuyiixwbi36ww8fuyg6y4657kc584aroggjy9b1mcobigfed7my”
Preloaded with 150000000 testcoins
4 Likes
So, I’m back after a beer, which is not helping be sure
but I wonder I’ve just stopped auth, started and create a new account and forgot that unlock… yet it’s working through nrs create ok.
So, I get
$ safe auth status
Sending request to authd to obtain a status report...
+------------------------------------------+-------+
| Safe Authenticator status | |
+------------------------------------------+-------+
| Authenticator daemon version | 0.5.0 |
+------------------------------------------+-------+
| Is there a Safe currently unlocked? | Yes |
+------------------------------------------+-------+
| Number of pending authorisation requests | 0 |
+------------------------------------------+-------+
| Number of notifications subscribers | 0 |
+------------------------------------------+-------+
$ safe auth unlock --self-auth
Passphrase:
Password:
Sending action request to authd to unlock the Safe...
Error: AuthdError: ClientError: Access denied for PublicKey: PublicKey::Ed25519(80b9a808600c1ab40e1e5fd9dc26f891d321a2c83a606e12db1a9df951cd803f)
? could that be why the credentials file is not there …
1 Like
@happybeing was your script meant to stop once it was successful?
I left, came back and it was still running but i am in!!!
Chunks!!! 
15 Likes
I sent some coins to traktion successfully.
me@testhost:~$ safe keys transfer --from <noonewillknow> --to safe://traktion 20
Success. TX_ID: 0
If anyone wants to test with mine, after all my screw-ups, my NRS is now:
safe://givewydileiemoney
Edit: As a test, I tried to send coins to myself and it properly failed with a ‘Same sender and Recipient’ error. Nice job, guys!
3 Likes
Can anyone say what data should go into --wallet-id parameter of sn_node?
This is what I get when I create wallet:
Wallet created at: "safe://hyryynbx7zw8ansu4fkiah73i3h31nre6ird88h51u5h8io15rkbyd4trqob6o"
New SafeKey created at: "safe://hyryyyyrogampqqeybi3a1p9sm9ucgic5dpx53cmpbjxp5o31bjdazrcmkr"
Preloaded with 0.000000001 coins
Key pair generated:
Public Key = 903616d739000d7389d0a5eddc332[redacted]559b1b5fbcb160a478b918b51
Secret Key = 8274d2552f35f9eb1815c8f7124fa[redacted]cc738831056faedc9ebe7690d
sn_node complaining no matter what I type in that parameter.