Bet you won’t do it again though…
I’m tempted to just fire it up on my laptop as well just to see what (if any) errors come up.
1 Like
$ tail -f ~/.safe/vault/local-vault/safe_vault.log
TRACE 2020-06-12T00:43:29.697433081+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/stage/approved.rs:1757] 86ffb5..() send parsec poke v6 to abaa98.. at 178.62.35.242:12000
TRACE 2020-06-12T00:43:29.697626656+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/transport/mod.rs:69] 86ffb5..() Sending message with token 957 to [V4(178.62.35.242:12000)]
TRACE 2020-06-12T00:43:29.697654746+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/stage/approved.rs:1757] 86ffb5..() send parsec poke v6 to bf197d.. at 178.62.39.12:12000
TRACE 2020-06-12T00:43:29.697843135+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/transport/mod.rs:69] 86ffb5..() Sending message with token 958 to [V4(178.62.39.12:12000)]
TRACE 2020-06-12T00:43:29.697881571+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/stage/approved.rs:1757] 86ffb5..() send parsec poke v6 to e93f2a.. at 167.172.55.70:12000
TRACE 2020-06-12T00:43:29.698092181+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/transport/mod.rs:69] 86ffb5..() Sending message with token 959 to [V4(167.172.55.70:12000)]
TRACE 2020-06-12T00:43:29.698133599+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/stage/approved.rs:1757] 86ffb5..() send parsec poke v6 to f262cb.. at 178.62.90.125:12000
TRACE 2020-06-12T00:43:29.698352891+03:00 [/usr/local/cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/transport/mod.rs:69] 86ffb5..() Sending message with token 960 to [V4(178.62.90.125:12000)]
I guess I’m doing something. 
5 Likes
We had one where a single user had over 3000 nodes 
7 Likes
Everything perfect. The vault requires very few resources and goes totally unnoticed. Software to run and forget.
About half an hour ago
34,5MB and 610 chunks
And now
53,5MB and 941 chunks
15 Likes
every worked perfectly until this:
networks check
Checking current setup network connection information…
Fetching ‘shared-section’ network connection information from ‘/Users/michaelhills/Library/Preferences/net.MaidSafe.safe-cli/networks/shared-section_vault_connection_info.config’ …
‘shared-section’ network matched. Current set network connection information at ‘/Users/michaelhills/Library/Preferences/net.maidsafe.safe_vault/vault_connection_info.config’ matches ‘shared-section’ network as per current config
vault join
error: Found argument ‘join’ which wasn’t expected, or isn’t valid in this context
USAGE:
safe vault [FLAGS] [OPTIONS] [SUBCOMMAND]
Im on a mac so the commands I use exclude safe. So when I try to ‘vault join’ to get the ball rolling I get the error above.
Champagne ! 
I’m in too
Joining a section EldersInfo { prefix: (), elders: {710eba… at 68.183.38.1… etc etc
This is on a fresh buster install, public IP. Everything went flawlessly.
Do I need to say I’ve been hoping for this day for quite some time ? 
Thank you very much for putting this together ! And now, let us see how this behaves
7 Likes
I got that before updating to the latest cli. not sure if it is the reason for your error.
3 Likes
Will there be any intermediary steps for node ageing to give levels/incentive to become the next step up? Like Infant-newborn, Infant-kid, (skip teenagers and let them go rebel against perfection elsewhere), Adult-young, Adult-master, Elder-established, Elder-veteran? Crossed my mind while learning slowly/surely about this test net (though not sure if needed).
Speaking of that, talk about a good time to slowly/surely learn CLI. Must try and finally utilize my ridiculous dormant brain and actually learn something instead of going off somewhere else! I’ve definitely already learned a lot of what this test net has to offer, and have visualized the road ahead much more greatly (can explain to people better already), twisty and slightly unknown as it may be and is.
4 Likes
Very cool, unfortunately failed IGD on my comcast Xfi modem, i went through and made some settings changes but overall advanced security is off, and uPNP is on made no difference.
5 Likes
Just got back to it after having a bite. Can anyone help me get authd installed? Right now I’m putting in $ safe auth install and getting this.
Command ‘$ safe auth install’ is unknown or not supported yet in interactive mode
Type ‘help’ for a list of currently supported top level commands
Pass ‘–help’ flag to any top level command for a complete list of supported subcommands and arguments
1 Like
OK first do safe update
then once that has finished tell us what safe -V says
it should be safe-cli 0.14.0
2 Likes
Safe-cli is puring along, wow guys.
From an Ubuntu thats not seen safe-cli before it was so eash, I just did this…
wget -qO- https://safe-api.s3.amazonaws.com/install.sh | bash
source ~/.bashrc
safe update
safe auth install
safe vault install
safe auth update
safe vault update
safe networks add shared-section https://safe-vault-config.s3.eu-west-2.amazonaws.com/shared-section/vault_connection_info.config
safe networks switch shared-section
safe vault join
Got an error…
ERROR 2020-06-12T01:02:27.104603500+02: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.
… but that’s because I am running ubuntu WSL under win10, so… had to wait for a windows network popup to let me click the permission box.
Also confirmed UPnP is enabled on my router.
Tried
safe vault join
again…
new error,
INFO 2020-06-12T01:04:04.661476500+02:00 [src/bin/safe_vault.rs:114]
Running safe-vault v0.24.0
… Cannot start vault due to error: Routing(Network(IgdNotSupported))
I guess I will have to wait till the next test, but I am seriously impressed.
safe-cli purring away felt great.
my god… time to transfer more cash in to maidsafe.
No going back now… I want more.
Kansas is going bye-bye
Thanks maidsafe.
8 Likes
For whatever reason it is in interactive mode? Maybe that’s an issue? I did a fresh install using the script in the user guide. When I type in any commands besides anything from --help, I get something like
Command ‘safe update’ is unknown or not supported yet in interactive mode
Type ‘help’ for a list of currently supported top level commands
Pass ‘–help’ flag to any top level command for a complete list of supported subcommands and arguments
I just did ‘update’ instead of ‘safe update’ and it’s updating. I’ll see what happens from there andhitback in this post. Yes on Mac. Updated to SAFE CLI 0.14.0
Okay so for me, adding $ safe before any command it says it’s not a known command so just did ‘auth install’ and that is working. We’ll see if I can get that inane authd and then move onto vault to connect. Thanksfor the help and patience so far.
2 Likes
Is this a Mac?
I thought I update CLI, I’ll check that, thanks!
1 Like
Great job everyone! One large step closer to digital freedom!
Unfortunately my vault failed to join using two different routers.
In both cases I got the dreaded message:
“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.”
4 Likes
In my case I had to use “safe update” to update the safe binary that was installed using the script provided by the github install guide. Only then was I able to use “safe vault join”.
2 Likes
Seems that the install script for WINDOWS installs safe v0.12.0 instead of the latest safe v0.14.0.
3 Likes
I’ll give that a try, thanks
1 Like