[status: offline] SAFE Network Testnet - Vaults from home with IGD

Beginning to see these errors more frequently now …

DEBUG 2020-06-12T00:47:41.971763095+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 178.62.90.125:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:47:42.002476568+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 178.62.90.125:12000
DEBUG 2020-06-12T00:47:42.002547407+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:47:43.972132701+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 157.245.43.62:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:47:44.003082171+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 157.245.43.62:12000
DEBUG 2020-06-12T00:47:44.003169192+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:47:47.973844307+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 134.209.25.197:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:47:48.005379481+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 134.209.25.197:12000
DEBUG 2020-06-12T00:47:48.005470718+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:47:49.976162681+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 167.172.55.70:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:47:50.007202843+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 167.172.55.70:12000
DEBUG 2020-06-12T00:47:50.007291842+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:47:53.977430964+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 178.62.39.12:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:47:54.009645843+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 178.62.39.12:12000
DEBUG 2020-06-12T00:47:54.009737653+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:01.982168365+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 68.183.38.187:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:02.014098968+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 68.183.38.187:12000
DEBUG 2020-06-12T00:48:02.014185584+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:03.982987613+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 178.62.35.242:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:04.015976766+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 178.62.35.242:12000
DEBUG 2020-06-12T00:48:04.016060920+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:11.986735396+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 178.62.90.125:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:12.021494529+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 178.62.90.125:12000
DEBUG 2020-06-12T00:48:12.021582181+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:13.987355271+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 157.245.43.62:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:14.022153785+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 157.245.43.62:12000
DEBUG 2020-06-12T00:48:14.022241888+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:17.989905511+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 134.209.25.197:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:18.024563936+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 134.209.25.197:12000
DEBUG 2020-06-12T00:48:18.024636729+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:19.991151944+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 167.172.55.70:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:20.026277795+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 167.172.55.70:12000
DEBUG 2020-06-12T00:48:20.026365263+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session
DEBUG 2020-06-12T00:48:23.992638371+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:261] Error connecting to peer 178.62.39.12:12000: ConnectionCancelled - Details: Connection cancelled
DEBUG 2020-06-12T00:48:24.028612009+01:00 [/usr/local/cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/connect.rs:31] Connecting to 178.62.39.12:12000
DEBUG 2020-06-12T00:48:24.028695138+01:00 [/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustls-0.17.0/src/client/hs.rs:203] Resuming session

Looks like I am now unable to connect to the network…

willie@gagarin:~/projects/maidsafe/retreived-from-VfH$ safe dog safe://cdn
[2020-06-11T23:49:31Z ERROR safe] safe-cli error: Failed to connect: [Error] ConnectionError - Failed to connect to the SAFE Network: Unexpected("Connection timed out when bootstrapping to the network")

Anybody else seeing similar?

Yes, thanks for reporting it, I just fixed it, now it will install version 0.14.0.

7 Likes

Same dreaded error for me. But a few hours ago vault connexion attempt was working. My router has upnp igd activated. I have the feeling that the contact point is overwhelmed now.

2 Likes

Mine is still playing nicely.

1 Like

I guess you are opening the CLI by double clicking the binary on Windows? if so, that will take you to the interactive mode, where you shouldn’t type $ safe but just the commands names. If you want to run it out of the interactive mode you’ll have to open a console/shell, if it’s in Windows you open a CMD console, and from there you can run safe <command name> ...

Edit: I just read you are on Mac, I guess it’s the same, you are double clicking the CLI binary. I don’t know how to open a console in Mac.

1 Like

I have not seen any fresh chunks for an hour or more now and other connection attempts are all failing
willie@gagarin:~/projects/maidsafe$ safe cat safe://cdn
[2020-06-12T00:21:17Z ERROR safe] safe-cli error: Failed to connect: [Error] ConnectionError - Failed to connect to the SAFE Network: Unexpected(“Connection timed out when bootstrapping to the network”)

Have we broken/DDOSed Digital Ocean?

Im going to restart this vault – 20Mb of chunks is about to go…

Oh, for what its worth i added a port forward for 12000, it vonnected to the seed. Then disconnected then threw the port error.

I got a vault a response in the SAFE CLI that my shared vault was being launched and where the logs are stored but I’m not really sure how to view these logs either in my filesystem or the CLI. I’m not seeing any new info about my vault so far. Any advice? Maybe my being in interactive mode is a hinderance?

Bummer, looks like NETGEAR R7000 doesn’t work with IGD…can anyone confirm?
PS: UPnP is enabled

1 Like

I believe that’s the router I’m on right now, I’ll have to double check but I can’t get any more info past launching vault… not sure how to see the logs at the mo.

1 Like

You can open the log file with any text editor, if you find the way to open a console then you can use the tail -f <log filepath> to see it live.

This seems to show how to open the terminal for Mac @Nigel : How to Open a Terminal Window in Mac: 7 Steps (with Pictures)

1 Like

This is what I am a bit confused about. I’m in terminal and set the safe binary to use the commands in the terminal but it’s saying I’m in interactive mode. I try putting in ~/.safe/vault/local-vault/safe_vault.log and get.

Command ‘~/.safe/vault/local-vault/safe_vault.log’ 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’ve managed to stumble my way this far but I really appreciate the help!

You seem to be in the CLI interactive mode terminal, close it. Then follow the steps described in that link (How to Open a Terminal Window in Mac: 7 Steps (with Pictures)), once you have that terminal try to execute: tail -f ~/.safe/vault/local-vault/safe_vault.log

1 Like

@bochaco You. Are. The. MAN! Thanks again Gabriel, now to read the logs.

2 Likes

Hey @Nigel, otherwise I’m pretty sure you get get to the log through finder… just go to your home folder, .safe, etc; that’s what I did on windows, just opened the the log file in notepad…

Oops too late…

1 Like

Running safe-vault v0.24.0

==========================

INFO 2020-06-11T21:04:36.479061-04:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/igd.rs:117] Fetched IP address from IGD gateway: V4(192.168.1.25)

INFO 2020-06-11T21:04:36.480121-04:00 [/Users/runner/.cargo/git/checkouts/routing-616e72cf40f12bc0/4a092f0/src/node/mod.rs:129] ae3433… Bootstrapping a new node.

INFO 2020-06-11T21:04:36.482626-04:00 [src/vault.rs:128] Initializing new Vault as Adult

INFO 2020-06-11T21:05:06.492295-04:00 [/Users/runner/.cargo/git/checkouts/quic-p2p-9a2715614ed5c99d/c6ae051/src/lib.rs:543] Node 167.172.55.70:12000 is unresponsive, removing it from bootstrap contacts; 0 contacts left

INFO 2020-06-11T21:05:06.492505-04: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(OnlyPermanentLeasesSupported)

ERROR 2020-06-11T21:05:06.492596-04:00 [src/bin/safe_vault.rs:169] Cannot start vault due to error: Routing(Network(IgdNotSupported))

ERROR 2020-06-11T21:05:06.492623-04: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.

Aha. Little bit of a bummer. Same error @stout77?

weird part is it seems to want to connect but the hardcoded contact is unresponsive?

2 Likes

Is the Raspberry pi 3b+ strong enough for running a node?

@lionel.faber
@bochaco

Yeap same error, looks like it’s a Netgear r7000 problem…

1 Like

I know this is just being impatient…but I wonder whether changing these parameters would do anything…

1 Like

Linking this for future reference, might come handy…
https://www.linksysinfo.org/index.php?threads/upnp-port-forwarding-rules-got-dropped.74809/