yes, thank you 
Thats loads more detail 
could you change -y and -yy to -v and -vv for sake of making it easy to stumble upon / remember?
10 Likes
Rhaaaa my computer is getting overheated again and will shut down soon, dawn my vault wonāt become an adultā¦ 
Did some transactions
But couldnāt do nrs got an error I think (btw Iām trying this again on a SAFE key)
ewa@ewa-System-Product-Name:~$ safe nrs create adulthoodyni --link safe://hbyyyybr8ebm399gjj5psamj5q6f7pne6e8p8urys51h4xu5cq8sugw3em
[2020-06-11T17:00:21Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to PUT Sequenced Append Only Data: Data error ā Access denied - CoreError::DataError ā AccessDenied
2 Likes
This is what I was able to use with NSSM:
"d:\SAFE Vault\safe_vault.exe" -vv --hard-coded-contacts "[\"167.172.55.70:12000\"]" --root-dir "d:\SAFE Vault\local-vault" --log-dir "d:\SAFE Vault\local-vault"
4 Likes
DEBUG 2020-06-11T18:34:03.141090+01:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to x.x.x.x:12000
DEBUG 2020-06-11T18:34:03.141114+01:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer x.x.x.x:12000: Connect(EndpointStopping) - Details: Establishing connection
INFO 2020-06-11T18:34:03.141132+01:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:246] Could not send message to the asked peer 178.62.90.125:12000: Establishing connection
DEBUG 2020-06-11T18:34:05.128495+01:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to x.x.x.x:12000
I was testing if the vault would reconnect. If I interrupt / disconnect the incoming connections (there are several of these), they reconnect just fine. 
If I drop outgoing connection, or turn off my WiFi (and turn it back on). The vault constantly has an error connecting to the peer. 
7 Likes
Half of hour of waiting and here it is.
I even see some metadata:
{"template":"/Users/stephencoyle/Projects/maidsafe.net/src/containers/home","sharedHashesByProp":{},"data":{},"path":"/"}
8 Likes
I have chunks too, also after about an hour. Currently about fifteen! 
9 Likes
#MeToo Some of my chunks are chunky, but most are <3k
6 Likes
trying to get involved but getting this error when trying to update the vault
vault update
Checking target-archā¦ x86_64-pc-windows-msvc
Checking current versionā¦ v0.23.0
Checking latest released versionā¦ v0.24.0
New release found! v0.23.0 ā v0.24.0
New release is NOT compatible
ERROR 2020-06-11T19:04:03.313739600+01:00 [src\bin\safe_vault.rs:103] Updating vault failed: Release(āNo asset found for target:x86_64-pc-windows-msvcā)
3 Likes
Just made a change that I think will fix that @scottefc86, I donāt have a Windows machine to hand to check so do let me know if itās resolved
5 Likes
I think it is possible to update it manually with this link:
https://github.com/maidsafe/safe-vault/releases/download/0.24.0/safe_vault-0.24.0-x86_64-pc-windows-gnu.zip
(edit: file is moved, look at posts below)
1 Like
Still the same error.
What would I do with the link when downloaded @vort?
Ahh, ballsā¦ 
ERROR 2020-06-11T19:19:21.139389539+01: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.
Maybe I can join in next time!
Itās good to see things coming together though!
8 Likes
Unpack safe_vault.exe from .zip file and replace c:\Users\<your_user_name>\.safe\vault\safe_vault.exe with it.
(you can also make backup of yours safe_vault.exe just in case)
4 Likes
Ok made another change which should fix it if the last fix didnāt 
Or as @Vortsays, you can download & unzip manually
4 Likes
Note for anyone clicking on the link in @Vortās message it will no longer work, updated link is now here
Explanation - Scottās issue above is because the safe vault update cmd is expecting a file named ...windows-msvc but the auto uploaded file on both GitHub and S3 was actually named ...windows-gnu due to a bug at our end.
Iāve renamed the files manually on both GH and S3 so the new link is https://github.com/maidsafe/safe-vault/releases/download/0.24.0/safe_vault-0.24.0-x86_64-pc-windows-msvc.zip
1 Like
That may be not too important feedback , but I see strange things in log file:
INFO 2020-06-11T21:31:16.796029+03:00 [src\vault.rs:517] ...
INFO 2020-06-11T21:31:20.705252600+03:00 [src\vault.rs:347] ...
Sometimes time have 6 digits of precision, and sometimes 9.
Why that may happen?
1 Like
I think what you changed @StephenC worked. I managed to update the vault and launch it, but my log says its getting terminated?
INFO 2020-06-11T19:58:36.017597400+01:00 [C:\Users\runneradmin.cargo\git\checkouts\quic-p2p-9a2715614ed5c99d\c6ae051\src\igd.rs:117] Fetched IP address from IGD gateway: V4(192.168.1.20)
INFO 2020-06-11T19:58:36.017597400+01:00 [C:\Users\runneradmin.cargo\git\checkouts\routing-616e72cf40f12bc0\4a092f0\src\node\mod.rs:129] 4e936aā¦ Bootstrapping a new node.
INFO 2020-06-11T19:58:36.017597400+01:00 [src\vault.rs:128] Initializing new Vault as Adult
INFO 2020-06-11T19:59:06.040597700+01:00 [C:\Users\runneradmin.cargo\git\checkouts\quic-p2p-9a2715614ed5c99d\c6ae051\src\lib.rs:543] Node 127.0.0.1:443 is unresponsive, removing it from bootstrap contacts; 0 contacts left
INFO 2020-06-11T19:59:06.040597700+01:00 [src\bin\safe_vault.rs:156] Vault connection info: ā192.168.1.20:63677ā
INFO 2020-06-11T19:59:06.040597700+01:00 [C:\Users\runneradmin.cargo\git\checkouts\routing-616e72cf40f12bc0\4a092f0\src\node\mod.rs:468] 4e936aā¦(?) Failed to bootstrap. Terminating.
2 Likes
Yeah that doesnāt look right.
It doesnāt look like your safe vault join is trying to connect to our bootstrap nodes from what I can see thereā¦
Did you run the safe networks check safe networks add and safe networks switch commands exactly as in the OP? Try those again as it seems your set network is local
2 Likes
The auth install section is a little further down on that page. Glad to hear you got your vault up and running
Iām surprised thereās not more reports of IGD not working, seems Iām one of the very few whoās router doesnāt support it so far. Thatās great news though as if IGD is supported then onboarding those people to the network is a lot simpler 
9 Likes
Just redone it to make sure I joined the shared section and the logs are the same.
Successfully switched to āshared-sectionā network in your system!
If you need write access to the āshared-sectionā network, youāll need to restart authd, login and re-authorise the CLI again
5 Likes