Join the NEW Community Test Network (Running Now): "community1"

nice site @davidpbrown :thumbsup:

I’m also able to run the TodoMVC app by @zatvobor on our community testnet :smiley:

6 Likes

If we want to test this to its limit, I wonder @bluebird could take his offline and see if others that have port forwarding set now adopt the seed… but without the cache perhaps it’s unstable… I’ve opened 5483 to my vault but that is a home network so notionally a dynamic ip.

for those that want to see if they can bootstap off me / bluebird goes down:
207.172.241.242:5483

edit: Seemed to work bootstapping from myself via external IP

3 Likes

@bluebird perhaps update OP to suggest also need to fix safe_launcher.crust.config for the launcher. Thanks again… I shall sleep better now :relieved:

2 Likes

I’ll leave all this running tonight. I’m curious to read some logs and stats tomorrow. Have fun guys! (And add some more vaults so I can trim down some terminals)

1 Like

Wow and all this time I was asleep, I love you guys for experimenting.

:stuck_out_tongue:

3 Likes

Just got the vault running and my launcher is now connected!

2 Likes

Great work @bluebird !! I pinned the topic as long as there’s no main test started from Troon. I have some trouble with the Launcher but will test some more.

It seems we have 17 Vaults online right now. Great work.

2 Likes

Im getting the same ffi error on windows as you are. Running 4 vaults though.

My Vaults says we have 6 client accounts. But I can’t get the Launcher to work on Windows 10/64.

Owh I found it!

Just delete your safe_launcher.crust file!

When you have the Vault running, just delete the safe_launcher.crust file and start the launcher. Within seconds the launcher made it’s own .crust file again. Or I was just lucky with timing, but give this one a try and it might work :yum:.

EDIT: http://polpolrene.safenet is now live and kicking.

3 Likes

Don’t work for me. I have clients but even with a new safe_launcher.crust.config file don’t connect (Windows7/64)

worked for me as well! delete the config file. connected and registered to launcher! :smiley: struggling a bit with the demo app though. Just stands on waiting for response after allowing it.

2 Likes

Just for reference, the distributables are here:

SAFE Vault binaries

SAFE Launcher binaries

SAFE Demonstration Application binaries

I got the launcher to run. The method is as I described last night: Run a quorum of vaults, each listening on a different port, and open those ports, then in the launcher’s config, list each of those.

I’ll post more info once I get some reliable results.

The launcher registered once but the demo app timed out getting approval from the launcher. Since then the launcher times out while trying to register a second time.

Is there a limit on number of registration from the same IP?

I’m now logged in on the first/original registration account.

3 Likes

I think it might be because of few vaults? I had the same problem, after a while the demo app went slightly further to initialising.

demo app seems to be a bit slow indeed. Took me some time to upload my safesite. But it worked after all. Will try to upload some private files to test this further.

1 Like

How big is your routingtable in the Vault?

Demo app sticking at getting authorization from the launcher.

1 Like

just gave it a couple of tries, and third time was the charm, currently uploading. Have registered ID also.

1 Like

Now 21.

Maybe is my router. I’m in my office and this router is unusual and without access. Later I try at home.

2 Likes