New Release: Vault Phase 1 (real vault)

I reported the lack of Unicode support as a bug a while back:
https://maidsafe.atlassian.net/browse/MAID-2234

But, as @Antifragile pointed out, there might be some problems with supporting more characters, so maybe it’s not a bug at all.

https://forum.autonomi.community/t/protocol-domain-subdomain-path/28815/60

2 Likes

I think the only problem is to have called the flag --daemon. Something like --wait-for-auth-req would be clearer and wouldn’t encourage people to launch it in the background.

2 Likes

If I see option daemon I think it is meant for the process to run, started by the init or systemd process on Linux, or roughly the same as started in the background (& behind). Like for example

rsync … --daemon …

3 Likes

Yes, and it was the intention back then when we started with safe_auth CLI, we wanted to this be a daemon eventually but didn’t invest the effort on that thing, now the moment has arrived :slight_smile: . Note this also will give us some additional cool features apart from what it’s being discussed here, e.g. any Authenticator UI/GUI could be connected to this daemon, so you could interact with it using the CLI, and 5mins later you can do it with SNAPP GUI, while still logged in with same account all the time (you could be allowing auth reqs from the CLI or from SNAPP).

6 Likes

Are any of the shared vault images/songs/videos still available?

I could not access any of it, except for my own.

$ ./safe cat safe://hbyyyynndgnwyik7t6mba3ojxti5ar6r35mbzs9ek6erby8iaqc975b9j4
[2019-09-20T04:41:25Z ERROR safe] safe_cli error: [Error] NetDataError - Failed to GET Published ImmutableData: CoreError(No such data - CoreError::DataError -> NoSuchData)
$ ./safe cat safe://lazydog
[2019-09-20T04:41:54Z ERROR safe] safe_cli error: [Error] ContentNotFound - Content not found at safe://lazydog
$ ./safe cat safe://hbyyyydgtpdfuspaui6s4yozkyfbogrmf9jrt4zo6ea9nuspbdzhdtbfea
[2019-09-20T04:42:08Z ERROR safe] safe_cli error: [Error] NetDataError - Failed to GET Published ImmutableData: CoreError(No such data - CoreError::DataError -> NoSuchData)
$ ./safe cat safe://dweb/index.html
[2019-09-20T04:42:25Z ERROR safe] safe_cli error: [Error] ContentNotFound - Content not found at safe://dweb/index.html
$./safe cat safe://dweb
[2019-09-20T04:47:37Z ERROR safe] safe_cli error: [Error] ContentNotFound - Content not found at safe://dweb
$ ./safe cat safe://hbyyyydumbcdx4yd55q4bg3yxfjkrw15rbepchpy5izded53useofe5fge
[2019-09-20T04:48:05Z ERROR safe] safe_cli error: [Error] NetDataError - Failed to GET Published ImmutableData: CoreError(No such data - CoreError::DataError -> NoSuchData)
$ ./safe cat safe://safekey.bochaco
[2019-09-20T04:49:08Z ERROR safe] safe_cli error: [Error] ContentError - Sub name not found in NRS Map Container
$ ./safe cat safe://cyberpunk
[2019-09-20T04:49:37Z ERROR safe] safe_cli error: [Error] ContentNotFound - Content not found at safe://cyberpunk
$ ./safe cat safe://traktion.wallet
[2019-09-20T04:50:05Z ERROR safe] safe_cli error: [Error] ContentNotFound - Content not found at safe://traktion.wallet
$ ./safe cat safe://test
[2019-09-20T06:45:03Z ERROR safe] safe_cli error: [Error] ContentNotFound - Content not found at safe://test
$ ./safe cat safe://yropeehn
Files of FilesContainer (version 0) at "safe://yropeehn":
+-------------+------+----------------------+----------------------+-------------------------------------------------------------------+
| Name        | Size | Created              | Modified             | Link                                                              |
+-------------+------+----------------------+----------------------+-------------------------------------------------------------------+
| /index.html | 32   | 2019-09-20T04:39:31Z | 2019-09-20T04:39:31Z | safe://hbyyyyncr4gs6mf1w81xsmnhqcw9a3nt5kgn7gb6kka68qutt6mkjsth44 |
+-------------+------+----------------------+----------------------+-------------------------------------------------------------------+

It’s expected some of them must have gone due to an issue from a couple of weeks ago:

So some data has been lost due to that problem in the shared vault

1 Like

All users of the shared vault please note that this vault was restarted today and so the vault_connection_info.config file has been updated in the GitHub releases for the vault.
See the latest vault release here for the new vault_connection_info.config file - if you intend to use the shared vault you should download this to the relevant location for your platform, as per the OP.

Thanks.

9 Likes

I wanted to rebuild safe-cli and safe-authenticator-cli from source. It is OK for the former, but the latter doesn’t compile:

$ git clone https://github.com/maidsafe/safe-authenticator-cli.git
Cloning into 'safe-authenticator-cli'...
remote: Enumerating objects: 44, done.
remote: Counting objects: 100% (44/44), done.
remote: Compressing objects: 100% (32/32), done.
remote: Total 650 (delta 21), reused 22 (delta 12), pack-reused 606
Receiving objects: 100% (650/650), 354.21 KiB | 1.26 MiB/s, done.
Resolving deltas: 100% (374/374), done.
$ cd safe-authenticator-cli/
$ cargo build --features mock-network
thread 'main' panicked at 'assertion failed: prev.is_none()', src/tools/cargo/src/cargo/core/resolver/context.rs:153:25
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Note that I am using latest version of rust:

$ rustc --version
rustc 1.38.0 (625451e37 2019-09-23)

Edit:
Reverting rust version to 1.37.0 makes the compilation works. So, this is a problem brought by latest version of rust.

5 Likes

And now is it supposed to work? I mean new SAFE Browser v0.15.0 with current safe-cli, safe-authenticator-cli and safe_vault built from source. Because I still get the same symptoms.

1 Like

This sounds like a different issue to me, I’m not able to see safe://test with CLI v.0.4.0 either, are you?

EDIT: I’m sorry @tfa, I’m actually able to fetch it with SAFE CLI v0.4.0 (I had the wrong config before), but so I’m with the browser v0.15.0, aren’t you? perhaps making the same mistake as me not having the correct vault config in place and/or having a local vault running?

1 Like

I have a local vault and it is the one I want to use. My config file on the PC with safe browser is certainly correct because I get “Connected” and “Accepted” messages with its ip address in the vault logs.

1 Like

Ah ok, well it also works for me with local vault, uploading a site with CLI v0.4.0 to local vault and loading it with browser v0.15.0 on local vault too. What issue are you experiencing?

1 Like

Same symptoms as here:

Of course the message in Safe Browser is now: Nobody owns this address yet

1 Like

Ok, that’s what I just tried, can you please make sure you are re-authorising your CLI before uploading the site to your local vault? if you authorised it before with a safe_auth running against another vault the CLI may be storing the data in a different vault than the one your browser is connecting to.

1 Like

Normally every thing is properly configured:

On the vault:

  • Existence of safe://test NRS map
$ ./safe cat safe://test
Files of FilesContainer (version 0) at "safe://test":
+-------------------------+------+----------------------+----------------------+-------------------------------------------------------------------+
| Name                    | Size | Created              | Modified             | Link                                                              |
+-------------------------+------+----------------------+----------------------+-------------------------------------------------------------------+
| /img/safe_logo_blue.svg | 5851 | 2019-09-29T19:09:46Z | 2019-09-29T19:09:46Z | safe://hbwynon5ey35si9umca83jkuo6t6qkmkwcp6s9t3g964d9u8fyippaza6z |
+-------------------------+------+----------------------+----------------------+-------------------------------------------------------------------+
| /index.html             | 355  | 2019-09-29T19:09:46Z | 2019-09-29T19:09:46Z | safe://hbhybynoh189jbfes6u1qcu9ojff9rwap9dehr9neop6xikr5atdewactk |
+-------------------------+------+----------------------+----------------------+-------------------------------------------------------------------+
  • Traces of connection from client in vault logs:
$ ./safe_vault --ip pp.pp.pp.pp -p 5483 -vvv > /var/log/safe_vault.log
INFO 2019-09-29T17:39:04Z [src/bin/safe_vault.rs:140] Checking for updates...
INFO 2019-09-29T17:39:05Z [src/bin/safe_vault.rs:169] Current version is 0.19.2
INFO 2019-09-29T17:39:05Z [src/bin/safe_vault.rs:170] No releases are available for updates
INFO 2019-09-29T17:39:05Z [src/bin/safe_vault.rs:119]

Running safe-vault v0.19.2
==========================
INFO 2019-09-29T17:39:05Z [src/client_handler.rs:102] QuicP2p started on pp.pp.pp.pp:5483
with certificate [...]
...
INFO 2019-09-30T19:42:17Z [src/client_handler.rs:153] 3f8f50..: Connected to new client on nn.nn.nn.nn:1024
INFO 2019-09-30T19:42:17Z [src/client_handler.rs:700] 3f8f50..: Accepted App(Bls(85a2ae..), owner: Bls(85a2ae..)) on nn.nn.nn.nn:1024.
INFO 2019-09-30T19:45:21Z [src/client_handler.rs:157] 3f8f50..: Networking error: Connection was actively cancelled
INFO 2019-09-30T19:45:21Z [src/client_handler.rs:159] 3f8f50..: Disconnected from App(Bls(85a2ae..), owner: Bls(85a2ae..)) on nn.nn.nn.nn:1024

(pp.pp.pp.pp is IP address of vault, nn.nn.nn.nn is IP address of client)

  • Config file content (partial):
$ head ~/.config/safe_vault/vault_connection_info.config
{
  "peer_addr": "pp.pp.pp.pp:5483",
  "peer_cert_der": [
    ...
  • Config file checksum:
$ md5sum ~/.config/safe_vault/vault_connection_info.config
c6847c705c782c9971eedfd9cf3ae42c  /root/.config/safe_vault/vault_connection_info.config

On the client:

  • Config file checksum:
certutil -hashfile C:\Users\Thierry\AppData\Roaming\MaidSafe\safe_vault\config\vault_connection_info.config MD5
Hachage MD5 de C:\Users\Thierry\AppData\Roaming\MaidSafe\safe_vault\config\vault_connection_info.config :
c6847c705c782c9971eedfd9cf3ae42c
CertUtil: -hashfile La commande s’est terminée correctement.
  • Navigation attempt to safe://test:

(even though the browser is connected to the vault as shown in vault logs)

There is probably something that I am missing, but what?

Edit:

  • I built both safe-cli and safe-authenticator-cli with cargo build --features mock-network
  • I built safe_vault with cargo build.

Could that be the problem? Should I remove --features mock-network from all build commands?

Exactly, that’s the problem you are facing, you should build both safe_auth and safe_cli for real vault, the local vault is a real vault, and remember to re-authorise the safe CLI with the safe_auth connected to your local vault

2 Likes

Thanks for the info.

But now I get the following error when I try to create an account with safe_auth (on the same machine as the vault):

$ ./safe_auth --test-coins
Secret:
Password:
[2019-10-01T03:29:19Z ERROR safe_auth] safe_auth error: Failed to create an account: AccountContainersCreation("NFS error: NfsError::CoreError -> Request has timed out - CoreError::RequestTimeout")

The corresponding vault log is:

INFO 2019-10-01T03:26:16Z [src/client_handler.rs:153] a8865d..: Connected to new client on pp.pp.pp.pp:443
INFO 2019-10-01T03:26:17Z [src/client_handler.rs:700] a8865d..: Accepted Client(Bls(970930..)) on pp.pp.pp.pp:443.
INFO 2019-10-01T03:26:17Z [src/client_handler.rs:157] a8865d..: Networking error: Connection was actively cancelled
INFO 2019-10-01T03:26:17Z [src/client_handler.rs:159] a8865d..: Disconnected from Client(Bls(970930..)) on pp.pp.pp.pp:443
INFO 2019-10-01T03:26:17Z [src/client_handler.rs:153] a8865d..: Connected to new client on pp.pp.pp.pp:443
INFO 2019-10-01T03:26:18Z [src/client_handler.rs:700] a8865d..: Accepted Client(Bls(970930..)) on pp.pp.pp.pp:443.
INFO 2019-10-01T03:26:18Z [src/client_handler.rs:157] a8865d..: Networking error: Connection was actively cancelled
INFO 2019-10-01T03:26:18Z [src/client_handler.rs:159] a8865d..: Disconnected from Client(Bls(970930..)) on pp.pp.pp.pp:443
INFO 2019-10-01T03:26:18Z [src/client_handler.rs:153] a8865d..: Connected to new client on pp.pp.pp.pp:443
INFO 2019-10-01T03:26:19Z [src/client_handler.rs:700] a8865d..: Accepted Client(Bls(970930..)) on pp.pp.pp.pp:443.
INFO 2019-10-01T03:29:19Z [src/client_handler.rs:157] a8865d..: Networking error: Connection was actively cancelled
INFO 2019-10-01T03:29:19Z [src/client_handler.rs:159] a8865d..: Disconnected from Client(Bls(970930..)) on pp.pp.pp.pp:443

Then I authorized port 443 both udp and tcp, but that didn’t change anything.

I’ve come across that one from time to time (although I didn’t check the vault log). Generally fixed with a reboot.

I’ve just created an account with both secret and password = testing12345. Do you want to see if you can login using those?

3 Likes

Thanks, but I am trying to access my own local vault built from source.

1 Like

Apart from what @JPL suggested, you can run any of the CLIs with RUST_LOG=trace (or ‘debug’) and see if you get more info

1 Like