Fleming Testnet v3 Release - * NOW OFFLINE - v4 RELEASED*

We should start the sn_authd process before querying it :slight_smile:
safe auth start should do it.

5 Likes

In under a week, gone through two testnet iterations … Maidsafe is the SpaceX of the new Internet! :wink:

14 Likes

This solved the problem! :+1:

I was just following the instructions in the order they were laid out, and thus tried to restart auth before it was even started. Maybe restart could also just start auth?

6 Likes

Yup, we just had that discussion in the team :slight_smile: Upcoming soon!

7 Likes

Like in 10 seconds maybe? :smile:

I mean I’m really impressed about the pace. But hey, I was quick to report too, wasn’t I? :face_with_hand_over_mouth:

5 Likes

OP updated :+1:

5 Likes

image

12 Likes

Ten hours of Mission Impossible (Network) music to listen to, while searching for bugs. :star_struck: :grin:

8 Likes

:smiley: :smiley: in-house we call these T1 T2 etc. today’s was T3 obviously, reminds me of terminator movies :smiley: I’ll be back :wink:

18 Likes

Look like bug with handling spaces in username:

1 Like

Ha! I was just blogging about test net 1 and 2… then test net 3 comes along! :open_mouth:

Ok, blog on hold… testing this baby out! :sunglasses:

13 Likes

Quick note - the network needs to be added/switched before safe auth can start.

$ safe auth start
Error: Failed to start authd

Caused by:
    AuthdError: Failed when invoking sn_authd executable from '/home/paul/.safe/authd/sn_authd'
11 Likes

Ah of course - OP re-updated!

6 Likes

Chunks… I got them… they are immutable. :sunglasses:

6 Likes

I want your chunks, your boots and your motorcycle. I got them first time. No loops needed here.

9 Likes

Running into errors almost every step of the way…

think@thinkpenguin:~ safe -V sn_cli 0.23.2 think@thinkpenguin:~ safe auth install
Error: Failed to find a release available to install

Caused by:
0: ReqwestError: error sending request for url (https://sn-api.s3.eu-west-2.amazonaws.com/?list-type=2&max-keys=100&prefix=sn_authd): error trying to connect: dns error: failed to lookup address information: Try again
1: error sending request for url (https://sn-api.s3.eu-west-2.amazonaws.com/?list-type=2&max-keys=100&prefix=sn_authd): error trying to connect: dns error: failed to lookup address information: Try again
2: error trying to connect: dns error: failed to lookup address information: Try again
3: dns error: failed to lookup address information: Try again
4: failed to lookup address information: Try again

Can you ping sn-api.s3.eu-west-2.amazonaws.com ?

3 Likes

Node joined for the first time, exciting!

7 Likes

You guys rock :star_struck: :star_struck: :star_struck:

5 Likes

I’ve got a node up and running and that seems to be working.

safe cat was working, but now it’s suddenly not anymore. Getting an error

safe cat safe://hyryyry4aage8oh3dsaw9s5ihio3pmu63qxqduz35g3cpjd46ewuursbecenra
Error: Failed to connect: ConnectionError: Failed to connect to the SAFE Network: QuicP2p(UnresolvedPublicIp)

edit: now I’m getting another error message:
Error: NetDataError: Failed to get current version: NetDataError: Failed to retrieve last entry from Sequence data: ErrorMessage(NoSuchData)