Can't create coins, can also not debug

[folaht]

Wiped everything. Still receiving bootstrapfailure.

ERROR 2020-12-18T11:10:56.944525625+01:00 [/home/maidsafe/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.9.6/src/api.rs:250] Failed to bootstrap to the network: Connection lost
ERROR 2020-12-18T11:10:56.944679100+01:00 [sn_authd/requests/create.rs:55] Error occurred when trying to create a Safe: [Error] ClientError - QuicP2P error: BootstrapFailure
ERROR 2020-12-18T11:10:56.944765937+01:00 [sn_authd/requests/mod.rs:120] Error when processing incoming 'create' request with id 2956831259: [Error] ClientError - QuicP2P error: BootstrapFailure

@Traktion

to get a local ‘baby’ network running.

What do you mean by local ‘baby’ network running?
8 nodes running on the same computer? Is that local enough or does the client also need to run locally?
What about a LAN cli?
Is that still local baby network?

I thought LAN was fixed in 0.16.

[tfa]

@folaht

I noticed sn_cli-0.16.0-x86_64-unknown-linux-gnu.tar.gz unpacked is still named safe and not sn_cli .

I don’t remember that Maidsafe wants to rename CLI executable from safe to sn_cli. Do you have any link for that?

In CLI documentation all commands still uses safe keyword:

https://github.com/maidsafe/sn_api/tree/master/sn_cli#using-the-cli

[Traktion]

Did you try deleting your .safe home directory before installing the latest from dev thread?

My my-network_node_connection_info.config contains localhost “127.0.0.1:12000”, not a LAN address. I didn’t set this - the scripts did automatically.

Super simple steps here:

Safe Network Dev Update - December 17, 2020

@hamarana and @majumba what guidance is it you guys need? We recommend following the instruction in the OP above, it should be really straight forward to see some activity on your own computer at home. A brief cut down list of steps you can follow on a terminal if the OP is too verbose: curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash safe auth install safe node install safe node run-baby-fleming At that point you should have 8 nodes up & running on your machine - easy! Want to se…

[Traktion]

paul@Vader:~$ rm -rf .safe/
paul@Vader:~$ curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
=> Downloading Safe CLI package from 'https://sn-api.s3.eu-west-2.amazonaws.com/sn_cli-0.16.0-x86_64-unknown-linux-gnu.tar.gz'...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10.5M  100 10.5M    0     0  1780k      0  0:00:06  0:00:06 --:--:-- 1811k
=> Unpacking Safe CLI to '/home/paul/.safe/cli'...
=> Adding statement to '/home/paul/.bashrc' profile to have Safe CLI binary path in the $PATH
=> Profile '/home/paul/.bashrc' already contains a statement to set Safe CLI in the $PATH
paul@Vader:~$ safe auth install
Latest release found: sn_authd v0.0.12
Downloading https://sn-api.s3.eu-west-2.amazonaws.com/sn_authd-0.0.12-x86_64-unknown-linux-gnu.tar.gz...
[00:00:03] [========================================] 7.03MB/7.03MB (0s) Done
Creating '/home/paul/.safe/authd' folder
Installing sn_authd binary at /home/paul/.safe/authd ...
Setting execution permissions to installed binary '/home/paul/.safe/authd/sn_authd'...
Done!
paul@Vader:~$ safe node install
Latest release found: sn_node v0.25.15
Downloading https://sn-node.s3.eu-west-2.amazonaws.com/sn_node-0.25.15-x86_64-unknown-linux-musl.zip...
[00:00:05] [========================================] 9.34MB/9.34MB (0s) Done
Creating '/home/paul/.safe/node' folder
Installing sn_node binary at /home/paul/.safe/node ...
Setting execution permissions to installed binary '/home/paul/.safe/node/sn_node'...
Done!
paul@Vader:~$ safe node run-baby-fleming
Creating '/home/paul/.safe/node/baby-fleming-nodes' folder
Storing nodes' generated data at /home/paul/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/paul/.safe/node/sn_node
Network size: 8 nodes
Launching genesis node (#1)...
Genesis node contact info: ["127.0.0.1:38670"]
Launching node #2...
Launching node #3...
Launching node #4...
Launching node #5...
Launching node #6...
Launching node #7...
Launching node #8...
Done!
paul@Vader:~$
paul@Vader:~$ safe auth start
Creating '/home/paul/.safe/authd/logs' folder
Starting SAFE Authenticator daemon (sn_authd)...
sn_authd started (PID: 1575505)
paul@Vader:~$ safe auth create --test-coins
[2020-12-18T12:06:22Z ERROR safe] sn_cli error: Both the passphrase (SAFE_AUTH_PASSPHRASE) and password (SAFE_AUTH_PASSWORD) environment variables must be set for creating/unlocking a Safe.
paul@Vader:~$ export SAFE_AUTH_PASSPHRASE="test"
paul@Vader:~$ export SAFE_AUTH_PASSWORD="test"
paul@Vader:~$ safe auth create --test-coins
Sending request to authd to create a Safe...
Safe was created successfully!
paul@Vader:~$ safe auth unlock
Sending action request to authd to unlock the Safe...
Safe unlocked successfully
paul@Vader:~$ safe auth status
Sending request to authd to obtain a status report...
+------------------------------------------+--------+
| Safe Authenticator status                |        |
+------------------------------------------+--------+
| Authenticator daemon version             | 0.0.12 |
+------------------------------------------+--------+
| Is there a Safe currently unlocked?      | Yes    |
+------------------------------------------+--------+
| Number of pending authorisation requests | 0      |
+------------------------------------------+--------+
| Number of notifications subscribers      | 0      |
+------------------------------------------+--------+
paul@Vader:~$ safe auth
Authorising CLI application...
Note you can use this CLI from another console to authorise it with 'auth allow' command. Alternativelly, you can also use '--self-auth' flag with 'auth unlock' command to automatically self authorise the CLI app.
Waiting for authorising response from authd...
Safe CLI app was successfully authorised
Credentials were stored in /home/paul/.safe/cli/credentials

While waiting for auth, do this in another console (using request id returned, ofc):

paul@Vader:~$ safe auth reqs
Requesting list of pending authorisation requests from authd...
+--------------------------------+------------------+----------+------------------+-----------------------+
| Pending Authorisation requests |                  |          |                  |                       |
+--------------------------------+------------------+----------+------------------+-----------------------+
| Request Id                     | App Id           | Name     | Vendor           | Permissions requested |
+--------------------------------+------------------+----------+------------------+-----------------------+
| 1122722581                     | net.maidsafe.cli | Safe CLI | MaidSafe.net Ltd |                       |
+--------------------------------+------------------+----------+------------------+-----------------------+
paul@Vader:~$ safe auth allow 1122722581
Sending request to authd to allow an authorisation request...
Authorisation request was allowed

[folaht]

It didn’t run the day before yesterday unless I renamed it to sn_cli.
It’s back to safe again.

[folaht]

That’s local, like I said in post 18, it works.
I’m trying to reach a “shared network”.
I was under the impression that the ‘next version’ would have this working.

I was hoping the node contact adresses only count for node joining, but I suppose this blocks the safe authenticator of reaching nodes as well?

...
$ safe node run-baby-fleming
Creating '/home/folaht/.safe/node/baby-fleming-nodes' folder
Storing nodes' generated data at /home/folaht/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/folaht/.safe/node/sn_node
Network size: 8 nodes
Launching genesis node (#1)...
Genesis node contact info: ["127.0.0.1:57939"]
...
$safe networks add shared
Creating '/home/folaht/.safe/cli/networks' folder for networks connection info cache
Caching current network connection information into: /home/folaht/.safe/cli/networks/shared_node_connection_info.config
Network 'shared' was added to the list. Connection information is located at '/home/folaht/.safe/cli/networks/shared_node_connection_info.config'
$ vim /home/folaht/.safe/cli/networks/shared_node_connection_info.config
$ $ cat shared_node_connection_info.config
"192.168.178.23:57939"
$ safe networks switch shared
...
$ safe auth start
...
$ safe auth create --test-coins
...
2020-12-18T16:06:06Z ERROR safe] sn_cli error: [Error] AuthdError - [Error] ClientError - QuicP2P error: BootstrapFailure

[Traktion]

OK, I’ll have a play here between my two laptops and see if I have any joy.

[Traktion]

Hmm, my old laptop is 32 bit and the build is failing. Maybe I’ll have to try with VMs! Ha!

[folaht]

I’ve got it working, at least the command works.
Still the same computer.
I’m going to test it for two different computers now.

I build the node with

cargo build --release --features=simulated-payouts --

I’m not actually sure what the last -- stands for, but I’m just copying the command from post 14.

---

[edit]

LAN seemingly works for authentication. Gonna try it with a browser.

[Traktion]

Was it just sn_node that you rebuilt with simulated-payouts? I’m getting the same error as you were getting before when trying to connect to my network using a LAN IP address.

[folaht]

No I edited the hardcoded node contact IP address and then rebuilt it.

$ vim src/config_handler.rs +/LOCALHOST 

-- ...LOCALHOST...
++ new(192,x,x,x)

But now I have issues with localhost again after rebuilding again.

[edit]

Alright. I’ve been able to test both localhost and lan again and while authentication works, file upload doesn’t.
Neither client nor server side.

$ safe files put test.txt
[2020-12-19T12:40:17Z ERROR safe] sn_cli error: [Error] NetDataError - Failed to store Public Sequence data: Data error -> Unexpected error: Could not get history for key PublicKey::Ed25519(8684b3..) - ClientError::DataError -> Unexpected("Could not get history for key PublicKey::Ed25519(8684b3..)")

---

[update]

I tried global IP address as well. That does not work at all.