Fleming Testnet v6 Release - *OFFLINE*

hi - not sure if I should post here or the stupid questions channel - I am very new to this but having a go. I have previously set up an earlier node on a windows machine. So on these instructions above I have done the folllowing
rm -rf $HOME/.safe
then
curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
but I am getting an access denied message.

=> Unpacking Safe CLI to ‘/c/Users/render/.safe/cli’…
=> Adding Safe CLI binary path to the PATH in the system for all users
ERROR: Access to the registry path is denied.
=> Close and reopen your terminal to start using Safe CLI

What should I do !?

1 Like

I haven’t used Windows for years but I think the issue is that you need to log in with an administrator account and then run the install.

In the mean time, you might get away with using the full path to the Safe CLI executable, so instead of typing:

safe node join

You would type

/c/Users/render/.safe/CLI/safe node join

Not 100% about this but worth a try.

1 Like

got it - I opened Git Bash as an administrator and it installs for all users now! Thanks!

5 Likes

OK I got this far - I am too green to know what to do here, but I hope this information helps!.

$ safe keys create --test-coins --for-cli

[qp2p::api] ERROR 2021-06-19T19:35:27.777200400 [C:\Users\runneradmin.cargo\registry\src\github.com-1ecc6299db9ec823\qp2p-0.12.3\src\api.rs:266] Failed to bootstrap to the network: Connection lost
Error: Failed to connect: ConnectionError: Failed to connect to the SAFE Network: QuicP2p(BootstrapFailure)

this did’t happen in previous tests :frowning:

“Unfortunately we are unable to establish a connection to your machine either through a public IP address, or via IGD on your router.”

1 Like

I used to be able to run a node, but not with testnet V6. I’m just tethering through my Android phone. I think port forwarding might be possible, but I think I’ll wait.

Come to think of it, I believe I used an older phone with testnet V5, but I’m not sure. Same ISP, though.

This is real progress. Honestly a huge speed bump and a semi stable network with a big feature like AE on its first legs are great and a testament to the SAFE QA. Some of this stuff you’ll never see until it’s in the wild. Great job all.

12 Likes

Here are some log from my attempts :
[sn_node] INFO 2021-06-19T12:51:01.957323721+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/mod.rs:141] db2627… Bootstrapping a new node.
[sn_node] INFO 2021-06-19T12:51:01.961702111+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.12.3/src/endpoint.rs:140] Verifying provided public IP address
[sn_node] INFO 2021-06-19T12:51:02.050247841+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.12.3/src/endpoint.rs:156] Endpoint verification successful! xxx:12000 is reachable.
[sn_node] INFO 2021-06-19T12:51:02.122860840+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/bootstrap/join.rs:292] Sending JoinRequest { section_key: PublicKey(0e51…3b0d), resource_proof_response: None } to [(db2627(11011011)…, 206.189.123.84:54984)]
[tokio-runtime-worker] ERROR 2021-06-19T12:51:02.213496599+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.12.3/src/connections.rs:300] Failed reading from a bi-stream for peer 206.189.123.84:54000 with error: StreamRead(ReadError(ConnectionClosed(ApplicationClosed(ApplicationClose { error_code: 0, reason: b"" }))))
[sn_node] ERROR 2021-06-19T12:51:02.228561988+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/bootstrap/join.rs:353] Invalid JoinResponse::Retry bad prefix: Retry(SectionAuthorityProvider { prefix: (0), section_key: PublicKey(071c…0761), elders: {(02dbf8(00000010)…, 167.99.199.103:35978), (147779(00010100)…, 206.189.16.193:39604), (16652a(00010110)…, 206.189.123.25:49282), (3fb505(00111111)…, 206.189.123.61:46465), (776534(01110111)…, 206.189.31.15:42663), (784925(01111000)…, 188.166.159.43:40669), (7fb589(01111111)…, 159.65.55.40:54000)} })

…and the command line :
/bin/sn_node -vvvv --max-capacity 107374182400 --skip-igd --local-addr 192.168.1.2:12000 --public-addr xxx:12000 --root-dir /var/data --log-dir /var/log --hard-coded-contacts [“206.189.22.30:49067”,“206.189.125.149:12000”,“206.189.22.172:45421”,“46.101.0.202:36333”,“206.189.123.68:44729”,“46.101.22.214:50565”,“46.101.38.43:41024”,“159.65.62.238:35873”,“167.99.203.186:39987”,“167.99.199.5:52619”,“138.68.155.211:43542”,“138.68.162.206:50153”,“188.166.156.250:44267”,“46.101.59.84:56270”,“167.99.199.121:48299”,“206.189.115.253:57937”,“206.189.123.59:43633”,“46.101.38.6:41806”,“206.189.125.156:41487”,“206.189.22.199:57283”,“206.189.31.15:42663”,“188.166.159.43:40669”,“206.189.123.1:38495”,“159.65.53.215:39139”,“165.227.239.76:54439”,“206.189.123.25:49282”,“206.189.16.193:39604”,“167.99.199.168:48777”,“206.189.115.27:46006”,“206.189.30.106:58768”,“206.189.22.44:39409”,“206.189.123.3:36667”,“167.99.199.103:35978”,“206.189.26.250:59523”,“159.65.55.40:54000”,“167.99.199.89:50814”,“138.68.153.41:46626”,“188.166.150.89:49415”,“206.189.115.177:42081”,“167.99.203.17:44080”,“206.189.22.117:59235”,“206.189.123.83:57064”,“206.189.123.84:54984”,“206.189.123.61:46465”,“178.62.26.75:34358”]

Port forwarding is enabled, from both tcp/udp
from anywhere to public ip xxx:12000, redirect to 192.168.1.2:12000 (local ip)

1 Like

Indeed, in battle, those who get to choose the ground they fight on will always be victorious. The advantage continues to grow in our favour. Each test net is a small victory, not because we don’t understand our strength, but because to win we must first confront, accept, and master our weakness, and use it too, in the battle ahead. True strength is about understanding how to use weakness.

7 Likes

As long as you reliably know what your dynamic IP is when you set up the connection, that is what matters. Its lot easier to know tat when you have a static IP.
I am very well aware of te difference between public and private IPs.

As soon as I have this msg :
Encountered a timeout while trying to join the network. Please try again later.
the node shut down
is it ok ?

Deep, man deep – but I like it :slight_smile:

3 Likes

last one and I stop here :slight_smile:

[sn_node] INFO 2021-06-19T13:12:02.203493410+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/mod.rs:141] ed1947… Bootstrapping a new node.
[sn_node] INFO 2021-06-19T13:12:02.207923253+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.12.3/src/endpoint.rs:140] Verifying provided public IP address
[sn_node] INFO 2021-06-19T13:12:02.287372875+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.12.3/src/endpoint.rs:156] Endpoint verification successful! xxx:12000 is reachable.
[sn_node] INFO 2021-06-19T13:12:02.376131973+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/bootstrap/join.rs:292] Sending JoinRequest { section_key: PublicKey(1704…f432), resource_proof_response: None } to [(ed1947(11101101)…, 206.189.22.30:49067)]
[tokio-runtime-worker] ERROR 2021-06-19T13:12:02.458078459+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.12.3/src/connections.rs:300] Failed reading from a bi-stream for peer 206.189.22.30:52150 with error: StreamRead(ReadError(ConnectionClosed(ApplicationClosed(ApplicationClose { error_code: 0, reason: b"" }))))
[sn_node] INFO 2021-06-19T13:12:02.473709404+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/bootstrap/join.rs:194] Newer Join response for our prefix SectionAuthorityProvider { prefix: (1), section_key: PublicKey(0e88…758e), elders: {(9e2968(10011110)…, 46.101.59.84:56270), (b5bdfc(10110101)…, 138.68.153.41:46626), (c7511e(11000111)…, 167.99.199.121:48299), (c796dd(11000111)…, 206.189.22.117:59235), (f3838f(11110011)…, 206.189.125.149:12000), (f3851f(11110011)…, 206.189.123.68:44729), (f7686b(11110111)…, 206.189.123.59:43633)} } from 206.189.22.30:49067
[sn_node] INFO 2021-06-19T13:12:02.477015943+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/bootstrap/join.rs:292] Sending JoinRequest { section_key: PublicKey(0e88…758e), resource_proof_response: None } to [(9e2968(10011110)…, 46.101.59.84:56270), (b5bdfc(10110101)…, 138.68.153.41:46626), (c7511e(11000111)…, 167.99.199.121:48299), (c796dd(11000111)…, 206.189.22.117:59235), (f3838f(11110011)…, 206.189.125.149:12000), (f3851f(11110011)…, 206.189.123.68:44729), (f7686b(11110111)…, 206.189.123.59:43633)]
[sn_node] ERROR 2021-06-19T13:12:02.549070144+00:00 [/home/richard/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_routing-0.77.8/src/routing/bootstrap/join.rs:132] Node cannot join the network since it is not externally reachable: xxx:12000
[sn_node] ERROR 2021-06-19T13:12:02.558945947+00:00 [src/bin/sn_node.rs:138] Unfortunately we are unable to establish a connection to your machine (xxx:12000) either through a public IP address, or via IGD on your router. Please ensure that IGD is enabled on your router - if it is and you are still unable to add your node to the testnet, then skip adding a node for this testnet iteration. You can still use the testnet as a client, uploading and downloading content, etc. https://forum.autonomi.community/

…and the node shut down.

I have tried running this command but it looks like it hangs:
safe keys create --test-coins --for-cli

Any suggestions?

1 Like

The testnet is having trouble currently, and a new update with bugfixes is forthcoming. Stay tuned…

11 Likes

Yes, we debated a T6.1 this morning, but we have got some client feedback we wanted. Many fixes already in and so many more to come.

19 Likes

Anytime before lunch on Monday is fine…

6 Likes

You could be safe there :wink:

8 Likes

No dailly-dallying now, Jock.

5 Likes

Thanks so much to the entire Maidsafe team for all of your hard work!

imgflip.com

5 Likes