User run network based on test 12b binaries


#281

That is a third AWS instance I have connected now. DUnno what was going wrong earlier but it appears reasonably stable now - as lonng as nobody tries any mega uploads.
Hopefully we can get some more non-AWS nodes connected in the next few hours and normal uploading service can resume and then I will be able to take a couple of these down to save the bill at the end of the month.


#282

Ah that fixed it.

I was using this https://github.com/maidsafe/safe_launcher/releases/tag/0.10.1

I didn’t realized there was a -dev


#283

haha - i didn’t know that either xD glad that it works now!


#284

It’s weird the date is off, “dec 2016” Made me assume it is wrong version.

krishnaIndia released this on Dec 1, 2016


#285

strange - but good to have the correct link in the topic close to the config file now =)


#286

Yep - we really need a page pointing folk to the latest versions of each app to be used with each network if/when they differ


#287

Yeah but the link in the topic was wrong from my perspective because the date is two months off.

Not just that, the there are two different 10.1 versions. Whenever I look at my launcher files… 10.1, I assume there are no changes. They failed on their part. It should be 10.2, 10.3, etc etc…


#288

I’d write in and complain. Don’t forget to demand your money back as well.


#289

yeah we should have a (pinned) thread with infos about the current community network, a correct config file and a link to the compatible launcher - maybe closed so it doesn’t get filled with questions … just up-to-date correct info


#290

I demand my money back in safecoins. lol


#291

as an alternative i would offer you 5 thankscoin for your hassle that you can’t spend (because of not-yet-implemented ownership-transfer)


#292

safe://eeek.southside/


#293

hiya,

am i missing something?

doesn’t seem to be anyone to bootstrap too…

is anybody running?

rup


#294

Yes it’s up. Routing table size is 13. What config file are you using?


#295

lol… obviously the wrong one!!

can you pop me the latest?

also once its up i’ll leave so the ip can be added as a bootstrap vault.

185.16.37.149

rup


#296

No probs. I haven’t tried starting again since yesterday though. Hopefully this still works

{
“hard_coded_contacts”: [
“86.184.57.178:5483”,
“13.80.119.160:5483”,
“85.93.19.51:5483”,
“35.157.162.33:5483”,
“35.156.220.253:5483”
],
“bootstrap_whitelisted_ips”: [],
“tcp_acceptor_port”: null,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}


#297

ah, network name has changed…

now running with 14 peers…

please add my ip to the list as it will be up now til something changes

{
“hard_coded_contacts”: [
“86.184.57.178:5483”,
“13.80.119.160:5483”,
“85.93.19.51:5483”,
“35.157.162.33:5483”,
“185.16…37.149:5483”,
“35.156.220.253:5483”
],
“bootstrap_whitelisted_ips”: [],
“tcp_acceptor_port”: null,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_feb_2017”
}

rup


#298

Welcome aboard 8a5cb9!


#299

thanks!!

anyone seen bluebird? he was my partner running vaults last year…

nice to put something back…

rup


#300

Didn’t know a network was up yesterday so I tried with 10 droplets but couldn’t bootstrap somehow.

I’m now at work and try to join community network this evening.

Any idea what I did wrong?

  • 10 droplets public ip’s:5483 put in hard_coded_contracts
  • open firewall ports 5483 5484
  • boot first vault with option -f
  • same network name in config file for every vault

Now I see above that service_discovery_port is null ??