The good news: just updating the CLI allowed me to vault join.
The bad news: either the testnet is not yet running again, or the IGD won’t let me, which is what it appears to be for me:
Node 127.0.0.1:51835 is unresponsive, removing it from bootstrap contacts; 0 contacts left
INFO 2020-06-12T14:12:18.029814-06:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:335] IGD request failed: Could not use IGD for automatic port forwarding - IgdAddPort(RequestError(ErrorCode(501, “Action Failed”)))
ERROR 2020-06-12T14:12:18.029883-06:00 [src/bin/safe_vault.rs:169] Cannot start vault due to error: Routing(Network(IgdNotSupported))
I have no idea whether this is relevant or not but…
Last night when the network went down, I was thrashing around wondering if it was Just Me or if it was a system-wide problem.
Everything had been working OK, I had uploaded various sites and directories including one with around 3k objects totalling 50Mb. I was able to retreive files at a respectable download speed as well. Then it all stopped…
So I tried again this time on my laptop with a wifi connection. Got everything up to date and issued the safe vault join command. It failed telling me my router did not have the necessary IGD goodness… which was a bit weird cos it had been fine less than an hour before.
So the only change I made router-wise was connecting over wifi instead of by cable.
So when this network comes back up, those got the IGD message on their wifi connected devices, just try sticking a patch lead in. It might make the difference. Im using a Thomson Technicolor TG589. fwiw.
The SAFE CLI is an executable binary, which accepts commands, subcommands, arguments and flags.
If you run this executable by double-clicking it from any GUI file explorer, on any OS, it will run it and enter directly into the SAFE CLI interactive mode. If you are in interactive mode you don’t have to prefix the commands with safe (it’s redundant as you can only execute SAFE CLI commands there), so you type directly the command name, subcommand name, arguments, and flags, e.g. files put <path> --recursive.
If you don’t want to enter the interactive mode, you need to open a Window/Mac/Linux terminal first:
Then, within that terminal, you have to invoke the SAFE CLI executable, which is called safe (or safe.exe on Windows). Again, if you invoke it without passing any command/subcommand/flag it will take you to the interactive mode. Otherwise you can invoke safe / safe.exe passing the command/subcommand/etc. and it will execute it without entering the interactive mode, e.g. safe files put <path> --recursive.
For convenience I do this - once I have a terminal session running
mkdir ~/bin # make a local dir for all your executables
cp which safe ~/bin/ #copy the safe command to you local dir
PATH=$PATH:~/bin #add your local dir to the PATH so your commands are always available
so just typing safe or safe (subcommand) from any directory will work
EDIT: Keep forgetting you can’t use backticks when posting in here - it interprets them as formatted text
Line2 above there is cp backtick which safe backtick ~/bin/
Right, by executing c:\Users\User_1.safe\cli\safe you are calling the SAFE CLI without passing any command to it, therefore it takes you to the interactive mode.
Try with passing any command you want, let’s say:
c:\Users\User_1.safe\cli\safe files put <path-to-a-local-file-or-folder>
Sorry looks like I am out of my depth, I will just stick with interactive mode before my laptop ends up in a thousand pieces. Thanks for trying to help @bochaco much appreciated.
Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Users\User_1>c:\Users\User_1.safe\cli\safe vault join
Storing vaults’ generated data at C:\Users\User_1.safe\vault\local-vault
Starting a vault to join a SAFE network…
Launching with vault executable from: C:\Users\User_1.safe\vault\safe_vault.exe
Node started with hardcoded contact(s): [“127.0.0.1:443”]
Launching vault…
Vault logs are being stored at: C:\Users\User_1.safe\vault\local-vault/safe_vault.log
C:\Users\User_1>
Is that vault now launched but not from interactive mode? If so im still getting the terminated message in the logs. Thanks for the offer @Southside I will be taking you up on that hand holding but not tonight my head is about to explode.
Before the network stopped working last night I uploaded a 50Mb folder and then retrieved it.
It contained a detailed model of a 737-800 for FlightGear. Here is that aircraft model as up and downloaded to the SAFE network in action.
This is me on final approach to EGPK Prestwick airport .
Yes, you are on the right track now. Now you can open vault’s the log file by executing this in the terminal: notepad C:\Users\User_1.safe\vault\local-vault\safe_vault.log
It used to work. Now I just keep getting this. What changed?
ERROR 2020-06-13T23:51:55.851704647+03:00 [src/bin/safe_vault.rs:169] Cannot start vault due to error: Routing(Network(IgdNotSupported))
ERROR 2020-06-13T23:51:55.851765681+03:00 [src/bin/safe_vault.rs:170] Automatic Port forwarding Failed. Check if UPnP is enabled in your router’s settings and try again. Note that not all routers are supported in this testnet. Visit https://forum.autonomi.community for more information.
My IGD gateway fetched my LAN IP instead of my WAN IP. I did nothing to my router, just ran the vault as a n00b would per the instructions. Full log below
INFO 2020-06-12T09:11:01.984731440+10:00 [src/bin/safe_vault.rs:114]
Running safe-vault v0.24.0
==========================
INFO 2020-06-12T09:11:02.102911249+10:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/igd.rs:117] Fetched IP address from IGD gateway: V4(192.168.1.140)
INFO 2020-06-12T09:11:02.103886695+10:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:129] 722621.. Bootstrapping a new node.
INFO 2020-06-12T09:11:02.104200155+10:00 [src/vault.rs:128] Initializing new Vault as Adult
INFO 2020-06-12T09:11:32.110298605+10:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:543] Node 127.0.0.1:4010 is unresponsive, removing it from bootstrap contacts; 1 contacts left
INFO 2020-06-12T09:12:02.110669368+10:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:543] Node 127.0.0.1:4010 is unresponsive, removing it from bootstrap contacts; 1 contacts left
INFO 2020-06-12T09:12:32.111129649+10:00 [src/bin/safe_vault.rs:156] Vault connection info: "192.168.1.140:41307"
INFO 2020-06-12T09:12:32.111238071+10:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:468] 722621..(?) Failed to bootstrap. Terminating.
INFO 2020-06-12T09:12:32.115751294+10:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connection/bootstrap_group.rs:162] Failed informing about bootstrap failure: "SendError(..)"
Some nit-picky things
Hyphen vs underscore
safe-vault repository uses hyphen (consistent with safe-cli etc).
Binary is safe_vault
Log directory is local-vault
Log file is safe_vault.log
Log file contains a lot of meaningless “/usr/local/cargo/git/checkouts/” content, might be good to try to have that log as a relative path rather than absolute.
Running safe auth update when auth is not already installed fails with a cryptic message (sorry don’t have the message handy). It would be good to see it prompt for install instead of failing in an obscure way. Probably same thing happens for safe vault update, not sure. Also when flipped, trying to install when it’s already there it might be useful to prompt the user if they want to update.
Really happy to see vaults from home. I’m sure the results will be very helpful for the next iteration.
